To be fair I don't see radical changes from RxJS. Maybe I use it wrong or I miss something, but in reality I haven't need anything more than debounce from reactive/stream libraries on the client-side. On the other side streams on the server-side is a real deal - you can use streams for things like Gulp, stream response from the server, for queues etc.
There is also interesting story about ability to cancel request with RxJS+Redux, which I haven't tried.
Yes on the server side it brings an amazing set of functionality. Treating stuff as stream has performance advantages on certain applications. Regarding the story of cancelling promises it's not just promises any even can be cancelled. That was one of the powerful functionalities. I felt it to be extremely useful as I had some unorthodox usecases at work to implement streams in existing javascript app.
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.
Very good post. Kudos, but you missed a few innovations that made a real radical change as well like RxJS and innovations in JavaScript runtimes.
To be fair I don't see radical changes from RxJS. Maybe I use it wrong or I miss something, but in reality I haven't need anything more than
debouncefrom reactive/stream libraries on the client-side. On the other side streams on the server-side is a real deal - you can use streams for things like Gulp, stream response from the server, for queues etc.There is also interesting story about ability to cancel request with RxJS+Redux, which I haven't tried.
What do I miss here?
Yes on the server side it brings an amazing set of functionality. Treating stuff as stream has performance advantages on certain applications. Regarding the story of cancelling promises it's not just promises any even can be cancelled. That was one of the powerful functionalities. I felt it to be extremely useful as I had some unorthodox usecases at work to implement streams in existing javascript app.