On the contrary. Ryan Dahl, the person who created node, came up with deno, specifically to address a number of problems (or regrets) he had with node: see https://youtu.be/M3BM9TB-8yA.
On the contrary. Ryan Dahl, the person who created node, came up with deno, specifically to address a number of problems (or regrets) he had with node: see https://youtu.be/M3BM9TB-8yA.
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.
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...
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.