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 …
-
-
Replying to @slightlylate
Do you have any multi-year case studies of a real world, revenue generating application that successfully shows this? In my experience, software is never done, features are always added, never removed, which typically means "more script". This is a game of cost mitigation.
3 replies 0 retweets 13 likes -
Replying to @chadhietala @slightlylate
Correct. Which is why loaded script needs to be O(features used) instead of O(features built). Route based code splitting is still the latter. Manual code splitting doesn't work in practice. Mainstream frameworks still aren't there.
2 replies 1 retweet 9 likes -
Replying to @cramforce @chadhietala
This is why structure matters so much. Tools like Ember, React (and CRA), and Angular are, today, razors without safeties: fine if you bring your own, worse than useless if you don't. Teams need budgets to constrain decision space and help hitting them; not blank canvasses.
1 reply 3 retweets 3 likes -
Replying to @slightlylate @chadhietala
Structure is important. I've never seen budgets work in practice. Either your stuff works by design or you're broken. Budgets then just make you feel sad, but don't fix things. They are
% the same as the USA debt ceiling.2 replies 0 retweets 8 likes -
Replying to @cramforce @chadhietala
We have dashboards and "can't regress" metrics for Chrome startup. Same challenge, different language. Team culture and willingness to Code Yellow for perf are critical.
1 reply 0 retweets 6 likes -
Can't stress enough how important bought-in leadership is. The willingness to put feature work on hold to keep the overall user experience good defines thoughtful management of technology products.
2 replies 6 retweets 19 likes -
We have the same for Android however it's unrealistic to expect teams of ~10 to have the resources to dedicate to optimizing JS payload size after the fact.
1 reply 0 retweets 0 likes -
Replying to @samccone @slightlylate and
While I agree frameworks are not there yet, they are making non-trivial universal improvements to the web as a whole.
2 replies 0 retweets 0 likes
...and adding universal costs that are not borne proportionately by the wealthy or the teams building these experiences. It's a trade off, and we're managing it badly at scale.
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.