: hrm, I'm not hard on the WebPack folks, am I? In fact, I'm excited about a lot of what they've done recently.
-
-
Replying to @slightlylate
: ...but what I want to see are toolchains that are set up for success by default.
2 replies 0 retweets 0 likes -
Replying to @slightlylate
Ya what I mean. Always assumed devs knew to code split - I'd expect my tools to give me standard split promitives & that's it
1 reply 0 retweets 1 like -
Replying to @AdamRackis @slightlylate
Which WP does—supports AMD CJS & import split primitives. Literally not sure what else they can do (maybe yell @ big bundles)
1 reply 0 retweets 1 like -
Replying to @AdamRackis
: they're doing that now too! Like I said, tho, I think we need to (collectively) favor tools that set devs up for success.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: that might be WebPack-as-part-of-a-thing-that-configures-it-for-code-splitting-by-default. So far, that's not React ecosystem
5 replies 0 retweets 1 like -
Replying to @slightlylate
: to get there you need action or route awareness. A higher-level thing than just a component framework.
2 replies 0 retweets 0 likes -
-
Replying to @AdamRackis
: yep. I hope someone succeeds in hooking that up to build config by default in a popular boilerplate
1 reply 0 retweets 0 likes -
Replying to @slightlylate
idk - boilerplates becoming more unpopular I sense. Too hard to predict what the dev using it will need / want.
1 reply 0 retweets 0 likes
: well, whatever works. Splitting-by-default needs to be de rigueur!
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.