If you think this is a reason to jump on the ES Modules bandwagon you haven't looked at the loader spec. https://nolanlawson.com/2016/08/15/the-cost-of-small-modules/ …
-
-
Replying to @mikeal
Promise overhead right now is much costlier than function overhead. The load spec calls for each module resolution to use a promise.
3 replies 0 retweets 3 likes -
Replying to @mikeal
Which means that, if the current spec holds, *native* browser resolution of ES Modules will be slower than the worst browserify benchmark.
2 replies 2 retweets 2 likes -
Replying to @mikeal
While web developers are saying ES Modules are great for performance, the spec wonks are literally saying perf doesn't matter for native.
3 replies 0 retweets 3 likes -
Replying to @mikeal
Clarification: the "spec" is not agreed upon https://whatwg.github.io/loader/ so if you care about this you should contribute https://github.com/whatwg/loader
1 reply 1 retweet 1 like -
Replying to @mikeal
nah, I feel unwelcome there - people far smarter and patient than me have tried and been ignored, don't have the energy to try
2 replies 0 retweets 2 likes -
Replying to @yoshuawuyts @mikeal
seeing the state of the language I've given up on the notion that it can be "changed from within" - unsure about alternatives tho
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
you have to build a coalition to get things done. also, the loudest voices publicly don't always win "in the room."
1 reply 0 retweets 1 like
yeah I know; witnessed that with Node core Promises. But that stuff is gory, and don't feel there's a voice of reason for browsers
-
-
Replying to @yoshuawuyts @mikeal
Browsers + JS are off doing their own thing, feels like every now and then they just pop up and slam down a mandate. Makes me sad
0 replies 0 retweets 2 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.