What happened to one tool that does one thing well? If deno wanted to have HMR and all the good stuff the author mentioned, then Deno, with however much the maintainer count is, MUST prioritize and make compromise. But with every tool being a separate project, it is easier to make changes and to gather maintainer because of how broad range the tool application is compared to a single monolithic tool.

However, we do see a difference in Bun approach. It brings ALL the good stuff Deno does AND compatibility with Node from the get go. So the developer of course would flock there. Because the tooling works. Ironing out kinks of the tool is much easier than entirely severing compatibility in the name of progress.