The blog post didn't make it sound like this was implemented just for the sake of backwards compatibility, it sounds more like an admission that Deno's take on package management isn't a superior solution to how Node did it before.
It states many times it was added for backwards compatibility.
Even at the bottom of TFA they annotate the ideal solution (which will be implemented soon) is to use import maps instead of package.json, the same format the browser uses, which is in line with Deno's main goals.
Fast forward a few years, and they are now adding these two things natively to deno, just as the web ecosystem did. Turns out, Node was right to have modules and an import file all along, and at worst there were some minor implementation quibbles to argue about.
I'm glad I can use direct url imports in simple Deno scripts.
I also see the need for import maps for larger projects.
I do think node_modules is an abomination and glad I don't have to deal with them anymore.
I prefer writing everything that works in Deno and the browser, not Node specific APIs.
I like the tech, I don't really care about the drama, and I doubt the Ryan does either lol.
I disagree with how you summed it up, but I don't really care to continue.
It's getting too dramatic and not really about the tech at this point.