3 ms·
Node JS and by extension Deno is built on a house of cards. Deno is simply not ready for production. You can import NPM modules, but they aren't guaranteed to
by 999900000999 2y ago
Node JS and by extension Deno is built on a house of cards.
Deno is simply not ready for production. You can import NPM modules, but they aren't guaranteed to work.
https://docs.deno.com/runtime/manual/node/ https://docs.deno.com/runtime/manual/node/
- elnatro 2y agoSo when is this going to change? I mean, I suppose deno will become mature at some point, right? How did other languages become mature?
- 999900000999 2y agoIt might never be ready for production. Who picked Deno at your company? It's a odd choice given it's limited support. Even if it's fine for some use cases, it sounds like a poor fit for your needs.
- elnatro 2y agoWell the idea was to use a typescript-capable environment, and we thought that deno could be a good fit. The main problem is that we spent more time doing trial-and-error than actually developing software. Maybe it was a bad choice, yes.
- 999900000999 2y agoI think if I was in your shoes I would have evaluate what your ultimate goal is. Do you need a back in language with types ? Maybe C# would be a better fit?
- elnatro 2y agoThanks I’m thinking about golang, I don’t know we will see. Thanks for your advice!
- 999900000999 2y agoGolang is more mature, but it's still a relatively new language. C#, Java, and to a lesser extent NodeJS and Python are enterprise level backend languages with support for whatever you can imagine.
- WuxiFingerHold 2y agoIf you don't need NPM modules, Deno is pretty nice. There's a Deno specific ecosystem (e.g. DB drivers) that is working fine, but of course you're limited compared to the huge NPM ecosystem.