Won't make you guess how they died: Vocal framework authors shouted them down because they weren't perfect in their specific estimation.
O.o was decoupled from MDV in response to feedback that MDV was "too big" (which, sure, OK). The goal in all of this was to create a world where data updates could flow w/ the component hierarchy. It's not disingenuous that O.o tried to find a bigger audience when extracted.
-
-
Despite your 'sigh' that I'm 'confused', it was very explicitly positioned as something that could be used to implement change detection for the sake of driving views, i.e. within FWs (e.g. https://www.html5rocks.com/en/tutorials/es7/observe …). It made sense, briefly, at the time! But we shouldn't mourn it
-
...but frameworks like react *do change detection* on state object updates. It's behind the scenes, but we would have better tools to help them if the language was optimising for this.
- 18 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.