4 ms·

> Deno seems to be a solution looking for a problem On the contrary. Ryan Dahl, the person who created node, came up with deno, specifically to address a numbe

• auggierose 4y ago
  Yes, I know that. But Dahl's regrets are not my problems, really. Remember that Dahl is NOT the author of npm, and without npm, where would Node be now? Probably nowhere. For example, what is the problem with calling the TypeScript compiler? I have a build setup anyway, so why does it need to be integrated? That's an example of a solution where I don't see the problem.
  • mark_and_sweep 4y ago
    > without npm, where would Node be now? Probably nowhere. I disagree. There were and still are good competing package managers and registries. Perhaps, in an alternate universe, yarn might have won. Or in yet another universe, node would have package management built-in, as deno does now. In any case, node would be fine. > what is the problem with calling the TypeScript compiler? I have a build setup anyway Just because your project has a build setup, doesn't mean all other projects must have one, too...
    • auggierose 4y ago
      No, projects can do what they want, but if having a build setup is your biggest problem you need to solve, you are pretty lucky. Anyway, my real problem is to be able to easily create modules that I can use everywhere, on the backend, and in the browser. I don't think Deno makes that easier than Node, because for the web, I still need to add a build step using esbuild. So for me, Deno is pretty pointless. But that's just my opinion.