I like a lot of the points being made here. Some random thoughts: - Maybe Deno intends to be "just a runtime", compared to Node world, where the Node tool and

I like a lot of the points being made here. Some random thoughts: - Maybe Deno intends to be "just a runtime", compared to Node world, where the Node tool and NPM blur together. It also seems to be attempting to dial back Node projects' exponentially large dependency trees by putting a lot of its effort into its built-ins and standard library. - Deno is as free a bird compared to Node with its apt/dnf packages, multi-version/LTS support, and its lack of 10 years worth of old-JS cruft. It seems to not be too antsy to get out of its alpha stage. - I could see Deno start to overtake Node if: * It develops some mature, popular frontend (Vite for Deno becomes stable) and backend libraries. (And/or they pull off their Node compatibility features.) * It starts to sell people on a comparatively safer software supply chain than NPM. Some other perceived benefits would be: * Performance (not the case now) / the interesting stuff it's doing with its runtime. * New 'n fun.