It bugs me that people criticize TC39 for not basing Modules on Node/CJS. Why should they settle for a local maximum just bc it was first?
-
-
Avoiding sync IO & avoiding blocking syntax is good. But... having humans in charge of picking static vs dynamic import() isn't always best.
-
Jest startup went twice as fast by converting static imports to JIT dynamic imports via transpilation. https://github.com/zertosh/babel-plugin-transform-inline-imports-commonjs/issues …
-
You can't do that kind of "make-it-lazy" build-time optimisation with a native ES module loader. So we need to find new ways to be lazy.
-
Classic best practice: "Don't conflate module management with configuration management".
-
Experience with early implementations not predictive of long term possibilities. Statically analyzable no help if not exploited by impls
End of conversation
New conversation -
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.