IMHO Deno's has been approaching it "wrong", so it'd never take over Node.js. Deno has 3-4 big differences over Node: url-imports/no npm, explicit permissions,

IMHO Deno's has been approaching it "wrong", so it'd never take over Node.js. Deno has 3-4 big differences over Node: url-imports/no npm, explicit permissions, web compat, typescript. As both a dev and as a package publisher, those are either not an advantage, or a straight disadvantage. npm, for all the downsides it has (and it does have them), IMHO has been a huge net positive for the JS/web community. Explicit permissions on the land of 100-dependencies is just a non-starter. Web compat is def the biggest advantage as a dev myself, but Node.js has finally woken up and catching up. I don't use TS so won't comment. IMHO the main advantage of Deno, like IO.js back then actually, has been to make Node.js stop being sluggish and actually accept PRs/new challenging features.