It's interesting to me that by-and-large the folks who made the "frameworks will drive performance improvements" arguments in '15/'16 aren't working on the ones that actually have 2-3 years later.
-
-
Replying to @slightlylate
We don't have frameworks, that's the problem. We have a lot of libraries that are built individually and independently, then a bunch of them bundled together by another library without any specific process, constraints or limitations that a "framework" I assume should provide.
1 reply 0 retweets 2 likes -
-
Replying to @_zouhir
We *can* have frameworks. Preact CLI and Polymer PWA Starter Kit provide app structure. Others can too (but decline to do so for infuriating reasons).
2 replies 0 retweets 2 likes -
Replying to @slightlylate
App structure is cool, Preact CLI is also beyond the app structure and does awesome optimisations out of the box. but I'm thinking that a framework would be far more opinionated, strict & get you to question multiple practices you have in your code beyond bundle size.
1 reply 0 retweets 0 likes -
Replying to @_zouhir
Polymer PWA Stater Kit and Next.js also do a lot of great optimisations out of the box. Not enough people are adopting these tools, and the messes I'm seeing are the result.
2 replies 0 retweets 1 like -
JS bundles the size of a small moon, main threads locked up like a supermax.
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.