2 ms·

> Will Bun JavaScript Take Node's Crown It's far too early to be asking this question. Deno has been around for longer, and it hasn't decrowned Node yet.

• franciscop 4y ago
  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.
  • nickserv 4y ago
    I had completely given up on Node and JavaScript in general until I had a chance encounter with Typescript recently. Seriously looking at deno specifically for the built in TS support. Will never touch basic JS again.
  • crabmusket 4y ago
    From Deno's early days, it seemed their goal was to make something fairly different to Node. Holding up "had it replaced Node yet" as a yardstick seems misguided.
    • andrew_ 4y ago
      Agreed. The guy just wanted to make something he felt was better. I've never seen a mission statement that said the goals were to replace Node. It's a separate beast.