Because selection bias. Of course sites using Svelte are brilliant: they’re engineered by the elite .1%, like @Rich_Harris. He could do almost as well w/ React if he were so inclined.
But yes, obviously the long tail of badly engineered sites are made with popular frameworks.
-
-
Didn’t mean to misrepresent you. App frameworks like Sapper are great. React has similar, ie Next. Sadly the people who need them most probably aren’t following you on Twitter, to get this msg. I don’t know what the solution is, but railing against web frameworks prolly isn’t it
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
What do you mean by “optimal code structure”?
-
Think he means things like code splitting being built in, and automatic. Thing is, app wrappers like Sapper and Preact-cli exist for React, too, ie Next.js. But nobody can force these devs to use it.
End of conversation
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.