There's a cottage industry of "thought leaders" trying to sell you one weird trick to fix what you broke with JS ("SSR!", "scheduler!", "compilers!", "preset-env!") but it's all failing. The only thing that works is *less script*. How? Structure + budgets.https://twitter.com/slightlylate/status/1018329021522706435 …
-
-
This is why tools that do things like auto-per-browser-builds and default route-based-code-splitting are different IN KIND. They represent that full, supported stack that you need to succeed.
-
That is, they are a key part of a culture that understands limits and budgets and has the tooling to support those things as an organisational priority. Cultural change is usually a discussion with managers and TLs. Not all teams get it. Related: lots of progress is darwinian.
End of conversation
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.