2 ms·
Loom should solve all that.
by apta 6y ago
Loom should solve all that.
- unscaled 6y agoI think Loom is thrown around too haphazardly here. Loom will present an ergonomic alternative for concurrency that is strictly superior to futures, but it will not replace or significantly simplify RxJava[1]. Project Loom is also orthogonal to actors - it really doesn't dictate any specific concurrency model, it just provides fiber support in the JVM. We will definitely see actor libraries once project loom is released, but these are already available now, and they are not widely used. The only thing Loom can help them with (I hope) is better performance, but I don't think that's the reason the actor model lost ground in the Java world. [1] Project Loom can be the basis for some minor simplifications, as JetBrains did in kotlinx.coroutines.flow.
- mping 6y agoI have never used Rx libraries. What are the cases where you have low friction coroutines such as loom (no "coloured" functions afaik) where you want to use RxJava? Handling backpressure? Modelling complex flows? Honest question