That path decouples progress from TC39 (a perenially winning move, in my experience) but leaves a path for eventual convergence. Why wait? Why bet on JS-first here when it has failed so massively to date?
-
-
Replying to @slightlylate @MylesBorins
Out of interest, what necessary components need working on to make "let's bet the farm on modules" story plausible?
1 reply 0 retweets 0 likes -
Replying to @lukejacksonn @MylesBorins
Right now, we need a syntax for fetch options in module requests (particularly destination type, but also CORS, etc.). Had hoped to avoid, but looks necessary.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @lukejacksonn
Seems like good use cases for modules attribute proposal
1 reply 0 retweets 0 likes -
Replying to @MylesBorins @lukejacksonn
Yep. What's the prognosis? Does committee grok it already burned through runway and is late to deliver?
1 reply 0 retweets 0 likes -
But let's say it works out...what's the case that we will not just continue to pile more transpilation on? What evidence shows meanings reductions in it vs. now fast-moving 90% browser-reach baseline?
1 reply 0 retweets 0 likes -
I want to believe. I have spent a decade mining this vein...but community doesn't want to hear we can't afford profligate ways, and node/server/cli tools are only insulating devs from costs today (not minimizing and/or providing visibility). What drives change in that behaviour?
1 reply 0 retweets 0 likes -
Replying to @slightlylate @lukejacksonn
This feels like the begining of "a new hope"



2 replies 0 retweets 2 likes -
Replying to @MylesBorins @lukejacksonn
I'm working on prods to change client dynamics (https://github.com/slightlyoff/never_slow_mode/blob/master/README.md …), but continuing to pitch "it'll be the same on the server and client" has been a massive loser. How do we enforce this sort of discipline server-side?
1 reply 0 retweets 1 like -
If the answer is "we'll move most of our heavy workload to the server and treat client as a scarce resource, but with more shared platform underpinnings", I'd buy it. But "universal" is a comforting lie so long as resource costs diverge wildly for client and server.
1 reply 0 retweets 0 likes
More to the point: if we're doing futurism that doesn't mention (nevermind solve) the existential perf crisis that a decade of JS-first has wrought, we're talking about a future that is smaller, serves fewer people, and retreats into gated communities of network and CPU wealth.
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.