Rollup does not code split. Even Rollup's author has said it's for different use cases than webpack. /@Rich_Harris
-
-
Replying to @AdamRackis @seldo and
I've been in the OSS rough and tumble for long enough to understand "it's for different use cases". Politeness is a virtue.
2 replies 0 retweets 1 like -
Replying to @wycats @AdamRackis and
Honestly, "even the author said" is a good way to take a polite response and use it against somebody ;)
1 reply 0 retweets 0 likes -
Replying to @wycats @AdamRackis and
Rollup's use cases massively overlap with webpack and it should have code splitting.
1 reply 0 retweets 1 like -
I mean, webpack produces UMD builds (Rollup use case) - so I guess nothing would stop Rich from adding lazy script loading to Rollup :)
1 reply 0 retweets 1 like -
Replying to @AdamRackis @wycats and
Of course then he'd need to add something to let users manually manage async chunks' contents, and, and, and ......... --------- === webpack
1 reply 0 retweets 0 likes -
-
Replying to @wycats @AdamRackis and
They do indeed overlap. I build apps with Rollup all the time. I'm just not the kind of person to bother convincing everyone else to
1 reply 1 retweet 6 likes -
Replying to @Rich_Harris @wycats and
Aren't you effectively betting that the app will never grow to the point where you need to code split?
1 reply 0 retweets 0 likes -
Replying to @AdamRackis @Rich_Harris and
@Rich_Harris said what I expected him to mean. ;)1 reply 0 retweets 1 like
I think code splitting is important but overrotated upon
-
-
Replying to @wycats @AdamRackis and
Totally. It (and webpack itself) comes at a cost. If your app reaches a point where the benefits outweigh that cost, do it, otherwise don't
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.