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 …
I *also* see failure in stable, evolving products, for reasons we'd agree on. In both cases budgets and structure are helpful. In new projects, that defines tool choice. In stable products, that defines the space of improvement projects (often down to changed assumptions)
-
-
What I'm trying to say is that performance is about culture supported by tools. Browsers did a decent job supporting an HTML+CSS world; pulling out all the stops to get users to interactive content quickly. JS defeats all of this, puts burden back on teams...
-
...and the tools they're picking up today, frequently, do not include equivalent support for getting interactive quickly by default. So we need to reset: when you pick JS as your starting point, you now own the full problem. The browser can only do so much to help.
- 4 more replies
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.