> hoping that Deno would be a reboot That's exactly what they tried, by settting up a Deno-only registry. But there is just way too much work and momentum hap

> hoping that Deno would be a reboot That's exactly what they tried, by settting up a Deno-only registry. But there is just way too much work and momentum happening in the NPM ecosystem. Many library maintainers wouldn't want to bother maintaining separate packages for a barely-used ecosystem, and users will be less likely to switch because they can't use the existing (huge!) ecosystem. It's the same language after all, "just" a different standard library (which is very impactful for lot's of server-side code) and packaging/distribution mechanisms. This move was probably inevitable.