in keeping with the spirit of extracting sense and meaning where it may be implied rather than enumerated, I grokked:
1) noise is bad.
2) web fashions come and go
3) the trendy is not always right.
i happen to agree with these points in many regards, so perhaps I'm a poor reader and merely projecting...
but yeah, I'm pretty over the militant "a react in every stack" approach... ditto every other myopic temporary obsession... you realize this after a couple hegelian cycles of thesis, antithesis, synthesis... i mean, when yesterdays baby becomes todays bathwater and it's time to throw it all out, or perhaps consider renaming "common sense" that rare balanced mix of functional object-oriented reactive structured aspect oriented programming as a service platform...in the cloud
I don't think it's as much "a React in every stack" as "observables solve a lot of problems that couldn't previously be solved with promises."
Handling async events can be difficult and error probe. Observables finally provide a useful pattern to that can be used to effectively manage async operations on data.
React os the poster child because it came first but Angular2 also uses Rxjs (ie Reactive Extensions for JS).
The poster goes to the opposite extreme, "if we're doing functional programming in JS, everything should be functional. Here's what I use, everybody who doesn't also use it is dumb."
i happen to agree with these points in many regards, so perhaps I'm a poor reader and merely projecting...
but yeah, I'm pretty over the militant "a react in every stack" approach... ditto every other myopic temporary obsession... you realize this after a couple hegelian cycles of thesis, antithesis, synthesis... i mean, when yesterdays baby becomes todays bathwater and it's time to throw it all out, or perhaps consider renaming "common sense" that rare balanced mix of functional object-oriented reactive structured aspect oriented programming as a service platform...in the cloud