2 ms·
One of my projects for work is RxJava and I’ll never touch anything Rx again. I don’t see any benefit it brings outside of making your project and control flow
by vips7L 5y ago
One of my projects for work is RxJava and I’ll never touch anything Rx again. I don’t see any benefit it brings outside of making your project and control flow convoluted.
- halfmatthalfcat 5y agoThat's unfortunate because reactive programming shines when you have continuous data flows and want to run pipelines against them; whether that's clicks, websocket events, queue items, etc.
- Offpics 5y agoI work with rxjs and its a breeze to work with. My data flow got only complicated after introducing redux-observable.
- Jenk 5y agodocument.addEventListener("something", event => { /* blah */ }); is no different. Nor are Java streams or .NET linq.
- vips7L 5y agoJava streams don’t infest your project. They also don’t throw away the error system of the language. They are also leagues more maintainable than a reactive project. Ignoring the maintenance issues, reactive applications do not yield better performance on realistic I/O-bound workloads: https://julien.ponge.org/blog/publication-performance-and-costs-of-reactive-programming-libraries-in-java/ https://julien.ponge.org/blog/publication-performance-and-co... So all you end up with is less maintainable code and more developer headache.