I never thought that, and I know very little about the space. In attempting to learn about the available options as fast as possible (along with TS and JS), I learned that the same guy launched a total re-do to address the shortcomings he realized through years of experience with his original product. I didn't imagine he could do that without breaking compatibility.

But the point of Deno was to try to avoid pitfalls that became apparent in NodeJS, so some over-correction was bound to happen.