choice is sometimes not a good thing. This is just fragmentation for fragmentations' sake, imo. The bun team could have contributed to node. The deno team could have too (once they did a 180 and decided deno would be node compatible). Instead we have a de-facto standard with a bunch of subtly incompatible implementations.
Re:Deno Is Joining Cloudflare
by galaxyLogic on Wednesday October 14, 2026 @08:11PM
(#50097442)
I'm also happy using Common-JS syntax on the Node.js. In the odd case that both the client (browser) and the server (Node.js) should run the same code, it can easily be accomplished with minimal amount of code-duplication. And such code-duplication can actually be good reducing the number of dependencies that could break in some future version of the software.
Just saying don't throw out the Common-JS sub-system with the bathwater.
The problem with ES6 modules (imo) is it does not support sync loading of dynamic imports, so you have to figure out how to handle the Promise.
But that points to an important aspect of the platforms-game: The interface between the runtime and everything else should be standardized, to support true pick-and-choose.