• A shame, really. I like the idea of Deno. It was supposed to be faster, more secure by default, easier to maintain with good defaults, web API compatibility, the works. I think the main issue is that it failed to deliver useful value over node. At first it was doing its own thing with deno.json, URL imports, import maps.

    It quickly became apparent that people are mostly unwilling to change their ways from the node way of doing things. So, Deno started pushing node compatibility. It left it kind of in an awkward spot: Not as node compatible as node is (duh), but also not that much on top that would make people want to use it over node.

    I think the most important thing that Deno did was force Node to get better: TypeScript support, built in SQLite, a permission system. I doubt those things would get merged into Node if Deno and Bun hadn’t been around.

    I will always I will always respect Ryan Dahl. I wish him the best in his future endeavors.


    score 1 · canonical