Many interesting and fair points in the article. Given perfect hindsight, perhaps the ES Module specification would look quite different today. It might more cl

Many interesting and fair points in the article. Given perfect hindsight, perhaps the ES Module specification would look quite different today. It might more closely resemble CommonJS and prioritized compatibility with it. But that ship seems to have sailed. The ES module specification has been build into every JS runtime of note. Which of the issues raised in the article are actually actionable at this point? Due to the priorities of the web ecosystem, no breaking changes to ES modules are possible. Can any of the issues raised in the post be addressed in non-breaking fashion?