I (sadly) agree. Interested in the Ionic approach (see comments). Would like to hear @slightlylate's thoughts.https://twitter.com/tomdale/status/1153309794226147330 …
-
-
Replying to @peterbowyer
Platform improvements don't swallow existing practice whole, or suddenly invalidate everything you do in user-space; instead, they enrich the toolbox, making *some* things that used to be expensive much cheaper. Components? Cheaper. Coordination? Not yet cheaper.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @peterbowyer
...which means that if your perspective is that "components and coordination must come in a fused-together package", the new world is disorienting. But nothing about it prevents taking advantage of cheap components and moving to (much) smaller coordination-only frameworks.
1 reply 0 retweets 3 likes -
Replying to @slightlylate @peterbowyer
Our explicit goal, the whole time, was to raise the level of abstraction. That is happening to the extent that folks adopt tools that don't try to actively dissuade use of the now-cheaper substrates. You may recognize this effect from the effect of Promises on Node's EFC dogma.
1 reply 0 retweets 1 like -
Replying to @slightlylate @peterbowyer
Anyhow, there's always more to do. We should expose better scheduling to allow user-space to collaborate better with the complex ordering of the event queue. Thankfully,
@shubhie is on it!https://github.com/WICG/main-thread-scheduling …2 replies 0 retweets 2 likes -
One way to reframe is that much of the JS-industrial-complex is stuck in a frame of reference that encourages totalizing framework choice. To get a coordinator you must switch _everything_. This benefits framework authors in multiple ways; sucks for businesses, tho.
1 reply 0 retweets 2 likes
However, we can imagine coordinator-only tools. Schedulers that build on top of the standard WC lifecycle contract and present much smaller integration surfaces. I expect more of this.
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.