@fogti@chaos.social The near-total incompatibility in practice combined with the lack of actual convincing benefits besides "looks shiny" and the widespread misinformation about what the benefits supposedly are.
It's created basically two split ecosystems that take hours upon hours to try and integrate back together for maintainers, and all tooling now needs *two* implementations forever
Follow
@fogti@chaos.social Like, part of the problem is that CommonJS was already so widespread that it will never go away fully due to old code hanging around, and so now to have a tool that works in the real world, you must implement both CJS and ESM and this is likely to remain true in perpetuity
