3 ms·
Wow, I'm actually a pretty big fan of the original Observable, so on the one hand I'm pretty happy about that (assuming it will get standardised, rather than be
by Vinnl 3y ago
Wow, I'm actually a pretty big fan of the original Observable, so on the one hand I'm pretty happy about that (assuming it will get standardised, rather than being a Chrome-only API).
But on the other hand, indeed, like signals, I don't really think it meets that bar - especially since Observables have been widely available and actively worked on for a long time, without seeing wide adoption.
- azangru 3y ago> especially since Observables have been widely available and actively worked on for a long time, without seeing wide adoption Take a look at the "Userland libraries" section [0] of the proposal (almost certainly written by Ben). He argues that observables get reinvented in the userland in various libraries over and over again. It is a primitive, like Promise, only better, and with very sound theoretical underpinnings. [0] - https://github.com/WICG/observable?tab=readme-ov-file#userland-libraries https://github.com/WICG/observable?tab=readme-ov-file#userla...
- troupo 3y agoI think people have been burned by RxJS where observables are "cold" by default and the source of many problems, over subscriptions, false starts etc. The modern swing back to signals (which in a way stem from Knockout's observables) seems to be simpler and easier to reason about.