Given that CJS supports limited circular deps & that browserify/webpack have proven effective, what is the "killer app" of ES6 modules?
-
-
Replying to @isntitvacant
@isntitvacant My sense is that there may not be a "killer app", but that removing a build step and sourcemap is a win for FE dev2 replies 0 retweets 4 likes -
Replying to @izs
@isntitvacant In that sense, the "killer app" is "using npm for FE, without having to know about webpack/browserify" Not so "killer" maybe?3 replies 0 retweets 5 likes -
Replying to @izs
@izs@isntitvacant not if removing that built step will amplify page load latency. built step is easy, people concat js anyway!1 reply 0 retweets 2 likes -
Replying to @dominictarr
@dominictarr http/2 is concurrent and binary, would theoretically make this is a non issue - don't see build steps ever going away tho2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts you gotta look at the top index.js and parse it to know what to request next. round trips cost more than bandwidth.3 replies 0 retweets 4 likes -
Replying to @dominictarr
@dominictarr oh yeah, that's completely true - welp, there you have it; ES modules is next level bike shedding1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts we don't need this NIH, we need low level enablers: like how adding querySelector and querySelectorAll made jquery trivial1 reply 1 retweet 4 likes
@dominictarr this thinking got acknowledgement in the extensible web manifesto only to be ignored by modern spec WGs https://www.w3.org/community/nextweb/2013/06/11/the-extensible-web-manifesto …
-
-
Replying to @yoshuawuyts
@yoshuawuyts@dominictarr FE is not about JS only (images, css) focusing on js forgot about 1/2 the FE job, build step is there to stay0 replies 0 retweets 0 likesThanks. 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.