It’s disingenuous bordering on mendacious to keep blaming React for 400K JS loads when React’s 1/12 that size. I’m sure a lot of people would be curious where all that junk is in fact coming from, but so far you haven’t told us. Are multiple copies of lodash sneaking in? D3?
I say that *all the time*. I've said as much to everyone here on multiple occasions. This isn't a new position. I will, however, clarify in the post.
-
-
Sorry - maybe I missed you on those days. All I’ve ever seen from you is ragging on React for encouraging bad practices. I’ve not seen you push things like Next as safety guardrails that help React be more of a pit of success. But that’s a great message! Agree

-
Look at the post, look at the links to the frameworks I cite. They're links to Sapper (not Svelte). Polymer PWA Starter Kit (not Polymer). Ioinic PWA Starter Kit (not Stencil or Ionic), Preact CLI (not Preact). Etc. etc.
- 9 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.
. I’m lucky to have come from the requireJS side - never touched Browserify, so code splitting’s always been second nature to me.