3 ms·
Totally agree with you. I'll add to that a lack of native reactivity. The observable proposal has existed for years. It's still in stage 1 and was last present
by pier25 6y ago
Totally agree with you. I'll add to that a lack of native reactivity.
The observable proposal has existed for years. It's still in stage 1 and was last presented in to the TC39 in 2017 [1].
There seems to be an almost total disconnect between the needs of web developers and what the TC39 is working on. Data binding and reactivity are two important points, but also the need of optional static types which should be obvious by looking at the meteoric success of TypeScript. This is nothing new, it has been discussed since ES4 times 10+ years ago.
[1] https://github.com/tc39/proposals/blob/master/stage-1-proposals.md https://github.com/tc39/proposals/blob/master/stage-1-propos...
- SahAssar 6y agoIsn't observable superseded by Proxy? Most (all?) of what is enabled by observable should be possible with Proxy, right?
- pier25 6y agoGood point although Proxy is pretty low level (for the JS world) and you still need to implement a lot of stuff yourself. I would have expected something more akin to RXJS, MobX, or even the Svelte reactivity system.
- renke1 6y agoI guess Observable as in RxJS Observable (or the likes). Similar to Promise which is now part of the standard.