Hey @richytong I like the design of your API, I do find it more intuitive, but I also like RxJS's design as well. You keep mentioning the "Why" and I suspect it's probably due to a very famous TED talk. If you absolutely need the why, just have in mind that RxJS is an implementation of reactivex in JS:
You can find the "why" of reactivex in the website above. For the why of RxJS, just add "in Javascript" at the very end.
On the topic of map, concatMap, exhaustMap, mergeMap and switchMap all have their place and are useful in their own way. I'm not sure about how I would use them in the backend but I constantly use them on the frontend in different scenarios. Especially switchMap.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey @richytong I like the design of your API, I do find it more intuitive, but I also like RxJS's design as well. You keep mentioning the "Why" and I suspect it's probably due to a very famous TED talk. If you absolutely need the why, just have in mind that RxJS is an implementation of reactivex in JS:
reactivex.io/intro.html
You can find the "why" of reactivex in the website above. For the why of RxJS, just add "in Javascript" at the very end.
On the topic of
map,concatMap,exhaustMap,mergeMapandswitchMapall have their place and are useful in their own way. I'm not sure about how I would use them in the backend but I constantly use them on the frontend in different scenarios. EspeciallyswitchMap.