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 @gregwhitworth @ken_wheeler
Sorry, just saw this thread. The structure thing comes from app-level constructs that give you some ability to automate loading only what you need when you need it. Tools like CRA leave this as an exercise to the reader. Polymer PWA Starter Kit and Preact CLI bake it in.
1 reply 0 retweets 2 likes -
...and big companies (Google, FB) have proprietary analogues for their internal use that optimize modules sent -- sometimes on a per-user, per-feature basis.
1 reply 0 retweets 1 like
Those systems are tightly tied to app and framework structure. What's largely missing in OSS land is a similar set of tools. This is why I never recommend "naked" frameworks; I recommend systems that set you up for success by building in that structure.
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.