#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…
#scifi#rxjava
I've been thinking about why 🖖 Star Trek Discovery was interesting and odd at the same time. Michael's hyperactive inference made it unstable-to-mundane to my eyes.
However, when she was contrasted with a great captain such as Lorca, Pike and Rayner, the duo shined.
Add in a McCoy-esque unity of Booker, Tilly, Stamets, Saru, et all, and now we have a stable 3-body system.
Season 5 was good, but not perfect. I think the issue was that Rayner became number-1. He should have been the captain of the situation, making Michael his number-1 instead.
The show needed a seasoned leader who can filter through Michael's and the others' ideas through his experienced lense and make the decision. Not Michael. Rayner not knowing or being capable of all the inference was not a bug. It was a feature.
🤔
Which brings us to RxJava. I have many ideas and resolves to make it great again. But I'm too technical, driven, loopy.
The best years were when Ben Christensen was at the helm. He is an industry veteran who could filter through the ideas and resolves in a reliable, safe and measured way.
Our McCoy was probably the engaged community members who also provided contrast and feedback to the library.
I miss those days.
So what does this mean with regards to RxJava 4?
Technically doable, all doable. But we'd end up with a huge library if we do the full reactive triad / tetrahedron.
We need a filter. I need a co-operator, maybe even two.
To be clear, I'm not stepping down or release my admin powers. I invite qualified and established people like Ben & others to show up and get involved.
We can go slow, no need to do everything within 10 days. I can, but won't. But I could 😉
🙏 for listening.
Si programas en #Java, seguro que #RxJava ha pasado por tu cabeza. Te contamos cómo pasar del modelo secuencial al reactivo de forma natural, con ejemplos paso a paso para que todo cobre sentido 👇
Is #RxJava and the reactive paradigm overwhelming you? It's not as scary as it looks! Get our practical guide on moving from sequential code to data streams and functional composition. Read the full post here! 👇
Moving from for loops to reactive programming isn't easy. We'll guide your transition to #RxJava, from basics to advanced techniques, making everything click. Don't miss the post! 👇
If you’ve moved from using `for` loops to the reactive world, you know the transition isn’t easy. We’ll guide you through the switch to #RxJava — from the basics to more advanced techniques — so everything starts to make sense. 👇