Reactive eXtensions for composing async and event-driven programs using observable sequences for the Java VM.
https://t.co/CSzgIgWUhs
via @akarnokdgithub.com/ReactiveX/RxJa… GitHub / InternationalJoined January 2013
We are now in a time where there is a serious chance yours truly will be banned or heavily restricted on GitHub, the private platform that can do anything they want without checks and balances, no transparency.
I'll be arranging backups, but mainly I prepare to move the RxJava project into my institute's own GitLab repository:
git.sztaki.hu/karnok/RxJava
(please wait for the permissions to go live).
🫡 @akarnokd
Who. Cares.
Please add compiler conveniences such as extension methods, async-await, generator syntax for iterable/async-streams, auto Varhandles, in Java 27+.
Please. Stop fooling around and consider the community's needs. Any of our needs.
AI assist will help you resolve issues and corner cases.
Please 🥺
Disclaimer
The new profile picture is generated via @Grok based on the Elf-comics of @merrivius as if the Elf would talk to our ReactiveX eel in a snarky way.
🫡 @akarnokd
@akarnokd HI David, did you take a look at github.com/franz1981/Nett… and speakerdeck.com/franz1981/reac… ?
TLDR it enables running blocking operations AND any reactive pipeline on the same carriers - including ones which run Netty I/O without using the FJ pool.
I'm working on ... (1/2)
Wow. Interesting thesis.
umu.diva-portal.org/smash/get/diva…
If you can, please redo it with #RxJava 4's Schedulers.virtual() instead of wasting 1,000+ cached threads on blocking IO at once.
Also it is not explicitly mentioned by the document, but Structured Concurrency won't save you much.
Coordination is one of the hardest part of async programming and you'll sweat blood getting it to work for non-trivial and/or multi-valued use cases.
I know, because I did sweat.
Worry not. We'll fix that with Streamable / Streamer just fine.
😏Stay tuned!
#java#idea#rxjava
Here is my list of Java language enhancements that would make our RxJava life much much easier:
- Extension methods.
- Generators á la C#, yield return X and yield return async X.
- Syntactic sugar async/await on top of Virtual Threads
- Syntactic sugar atomics, atomic_read(x), atomic_cmpxchg(x), etc.
- Obtaining names via nameof(method|param|variable) at compile time.
These all seem to be doable, and anomalies worked around just fine. Please do it. Please.
🥺🙏
#rxjava#proposal
I've just posted a new hybrid reactive-virtual type Streamable and its provider Streamer.
It is a multi-valued sequence that complements the executor.submit() type one-shot calls with Virtual Threads.
It is going to be modelled after C#'s IAsyncEnumerable type.
Virtual threads make it very convenient to block on join() calls.
However, I'd rather have syntactic sugar support in Java: await someCompletionStage;. Any state machine builder for yield return and yield return async would be also welcome.
github.com/ReactiveX/RxJa…
Hi @merrivius !
I'm @akarnokd, the maintainer of @RxJava, github.com/ReactiveX/RxJa…, the project lead.
Would you be willing to create for us an Elf-comic style RxJava-eel, snarky, you know, image to become the @RxJava X/Discord header/banner?
Of course, please name the price.
We are a free OSS project, so I'll have to pay from my own pocket. Anywhere between $100 - $300 sounds good? Via bank transfer.
2K Followers 8K FollowingSoftware Engineer.
Cyclist. Swimmer. Pragmatist.
Farmer at heart. Digital Nomad by habit.
Forensic Scientist.
Politics affects us all.
RT ≠ endorsement.
25 Followers 423 FollowingI am a Microservices Developer with hands-on experience designing, developing, and deploying scalable Spring Boot microservices. With a strong background in Jav