3 ms·

Your response describes exactly how I felt using RxJS for the first time.

dmitriid 4y ago
It took the author of RxJava months to understand the concept. Screenshot from the book: https://twitter.com/dmitriid/status/811561007504093184 https://twitter.com/dmitriid/status/811561007504093184 (Jafar is the author of Rx .Net, and even he couldn't explain it to the future author of RxJava :) )
dtech 4y ago
I've been working with Rx for 10 years or so and I think it's a terrible model. If you need processing of streams of asynchronous dynamic ("hot") data it's the least-bad model I know, otherwise there are much better ways, especially now that many languages have async-await keywords or at least a Future/Promise type.
- halpmeh 4y ago
  Async await is way worse for serious async processing, mainly because handling cancellation sucks.
antihero 4y ago
I found using rxjs with redux to be a way of decoupling control flow. Instead of having a function with a bunch of thunks, you did something and then other bits of code to could effectively subscribe to the side effects of that and you built your control flow up that way. It had pros and cons, was quite powerful but you ended up with a lot of indirection and not exactly knowing what was going to happen.
Cthulhu_ 4y ago
I've only been using RxJs for a short while now (we're moving to react soon), I don't really get it. I mean I get it, just not why we're using it just to consume some REST APIs. 80-90% of that is boilerplate code to please RxJs, and only alll the way down through two layers of stores / states and a library another team maintains is there a single call to `fetch()` that does the actual work. I'm pushing to use react-query with the new app, I think people will get confused when it turns out hooking up the whole API will take hours.
azangru 4y ago
I just wanted to say, among all the negativity in the comments, that I love RxJS, and fell in love with it after Jafar's workshop. As Ben Lesh often says, there are sadly a lot of misconceptions around Rxjs and the Observable type. The Observable type is a primitive so useful that it keeps getting reinvented over and over (React's useEffect is a weird React-only observable; a redux store is an observable); whereas Rx is a set of convenience functions to help with the use of the Observable type. If people are happy to use lodash, I can't understand what makes them so unhappy about Rx, which is like lodash, but for async collections.

It took the author of RxJava months to understand the concept. Screenshot from the book: https://twitter.com/dmitriid/status/811561007504093184 https://twitter.com/dmitriid/status/811561007504093184 (Jafar is the author of Rx .Net, and even he couldn't explain it to the future author of RxJava :) )

dtech 4y ago

I've been working with Rx for 10 years or so and I think it's a terrible model. If you need processing of streams of asynchronous dynamic ("hot") data it's the least-bad model I know, otherwise there are much better ways, especially now that many languages have async-await keywords or at least a Future/Promise type.

halpmeh 4y ago
Async await is way worse for serious async processing, mainly because handling cancellation sucks.

antihero 4y ago

I found using rxjs with redux to be a way of decoupling control flow. Instead of having a function with a bunch of thunks, you did something and then other bits of code to could effectively subscribe to the side effects of that and you built your control flow up that way. It had pros and cons, was quite powerful but you ended up with a lot of indirection and not exactly knowing what was going to happen.

Cthulhu_ 4y ago

I've only been using RxJs for a short while now (we're moving to react soon), I don't really get it. I mean I get it, just not why we're using it just to consume some REST APIs. 80-90% of that is boilerplate code to please RxJs, and only alll the way down through two layers of stores / states and a library another team maintains is there a single call to `fetch()` that does the actual work. I'm pushing to use react-query with the new app, I think people will get confused when it turns out hooking up the whole API will take hours.

azangru 4y ago

I just wanted to say, among all the negativity in the comments, that I love RxJS, and fell in love with it after Jafar's workshop. As Ben Lesh often says, there are sadly a lot of misconceptions around Rxjs and the Observable type. The Observable type is a primitive so useful that it keeps getting reinvented over and over (React's useEffect is a weird React-only observable; a redux store is an observable); whereas Rx is a set of convenience functions to help with the use of the Observable type. If people are happy to use lodash, I can't understand what makes them so unhappy about Rx, which is like lodash, but for async collections.