If your framework of choice™ is not code splitting by default, they are choosing to ignore a requirement to shipping a performant experience
-
-
Replying to @samccone
Here's the question: are they "choosing to ignore" or "actively working on it but thinking through compatibility"?
3 replies 0 retweets 5 likes -
I don't know anyone who is hostile to these ideas or isn't actively thinking about it.
1 reply 0 retweets 0 likes -
The shaming angle is maybe effective for convincing people. But people are convinced! They're working on it!
2 replies 1 retweet 7 likes -
Replying to @tomdale
+1 -- this msg is more to users -- bc they assume because something is advertised as "performant" that they do not have to worry
1 reply 0 retweets 1 like -
but when codesplitting techniques are missing and the primary cost is in js parse + compile it leaves them in a perf hole.
1 reply 0 retweets 3 likes -
When evaluating what tools to build your app w/ codesplitting needs to be at the top of the list imho.
2 replies 0 retweets 1 like
ding ding ding. Let's make code splitting an expectation of the tools you use.
-
-
Replying to @wycats @fivetanley and
also, I'd be interested in which tools are on the path to near-term splitting.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.