It seems more responsible to both users, the community, and to the teams involved to re-build Imports on top of Web Packages and let JS catch up whenever the committee realizes the world changed around it.
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.
-
-
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.
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.
