Sometimes I wish we'd had reactivity, data binding, or even a vdom in the browser so that we could save tons of bandwidth and CPU cycles. Then I remember how useless WCs are.
-
-
Alex, don't be disingenuous. The primary motivation for O.o, at least in terms of how it was communicated, was to facilitate easier data-binding as implemented by contemporary frameworks. Once we realised that data-binding was a local maximum, that motivation disappeared
-
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.
- 22 more replies
New conversation -
-
-
Right, in many ways, O.o could've been leveraged as just a first class way to get event listeners period the end
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.