4 ms·

It was made by the creator of NodeJS and fixes many issues he considers to be mistakes. Do you like NodeJS? This is NodeJS 2.0.

hn_throwaway_99 5y ago
I've seen the original Dahl post about his mistakes with NodeJS, and why he wanted to do Deno, and to be frank, I'm not convinced. It's not that I disagree with Dahl on most of his recognized mistakes (though some I do, most especially that a standardized, embedded packaging system was a mistake, despite the legions of warts of NPM), it's that most of these mistakes feel like little nits or one-time costs that just don't bother me at all in the Node world. I mean, it feels like the best thing going for Deno is out-of-the-box TypeScript support, but with Node it's trivial to have a template project that integrates all this for you, then it's 1-and-done. Perhaps the other thing I like about Deno is it separates the standard library into its own package instead of being part of the Deno-runtime version, but again, this difference is definitely not enough to make me switch.
- andrewmcwatters 5y ago
  Deno feels like past the peak technology to me. You've got years and years of labor put into the Node.js ecosystem, and then the guy comes out with something that totally drops all of that for some gimmick features. Could you not just build a URL loader and cache for importing in Node.js? Could sandboxing not just be a flag in Node.js? Do you really need TypeScript built in? I'm not going to throw years of my and other's work away for some gimmicks. It's just a bad investment.
  - ecares 5y ago
    > Could you not just build a URL loader and cache for importing in Node.js? Could sandboxing not just be a flag in Node.js? Do you really need TypeScript built in? There are open PRs on node for the first two parts ^^ It's 100% doable.
    - andrewmcwatters 5y ago
      Seems like Deno will have some great competition then. I'd rather slowly implement such functionality than dump everything.

hn_throwaway_99 5y ago

I've seen the original Dahl post about his mistakes with NodeJS, and why he wanted to do Deno, and to be frank, I'm not convinced. It's not that I disagree with Dahl on most of his recognized mistakes (though some I do, most especially that a standardized, embedded packaging system was a mistake, despite the legions of warts of NPM), it's that most of these mistakes feel like little nits or one-time costs that just don't bother me at all in the Node world. I mean, it feels like the best thing going for Deno is out-of-the-box TypeScript support, but with Node it's trivial to have a template project that integrates all this for you, then it's 1-and-done. Perhaps the other thing I like about Deno is it separates the standard library into its own package instead of being part of the Deno-runtime version, but again, this difference is definitely not enough to make me switch.

andrewmcwatters 5y ago
Deno feels like past the peak technology to me. You've got years and years of labor put into the Node.js ecosystem, and then the guy comes out with something that totally drops all of that for some gimmick features. Could you not just build a URL loader and cache for importing in Node.js? Could sandboxing not just be a flag in Node.js? Do you really need TypeScript built in? I'm not going to throw years of my and other's work away for some gimmicks. It's just a bad investment.
- ecares 5y ago
  > Could you not just build a URL loader and cache for importing in Node.js? Could sandboxing not just be a flag in Node.js? Do you really need TypeScript built in? There are open PRs on node for the first two parts ^^ It's 100% doable.
  - andrewmcwatters 5y ago
    Seems like Deno will have some great competition then. I'd rather slowly implement such functionality than dump everything.