DEV Community

loading...

Discussion on: Question: Will Deno replace NodeJS?

Collapse
eriklz profile image
Erik Lundevall Zara

I think it has to be a bit more contextual than that.
Deno addresses a number of shortcomings with Node.js and also sacrifices some compatibility in the process. For those that the secure runtime is more important than to have all packages available for the node ecosystem, then Deno may be better - if it is still important to use Typescript or JavaScript in that context.
Others may stick with node if package ecosystem is more important, or go for something else entirely.

I would not be surprised if Deno would be used more in a FaaS context, like AWS Lambda.

Collapse
aadityasiva profile image
Aadityasiva Author

Umm I actually wrote this to ask the community not to tell about my view

Collapse
eriklz profile image
Erik Lundevall Zara

But you did state a view :-)

And I agree, Deno will not replace Node.js. New technologies/solutions seldom do that, except in certain scenarios or if they enable new scenarios which were not available before.

Personally, I think Typescript is pretty ok given its heritage and for the things I tend to use Typescript for, I would prefer something like Deno for an ecosystem rather than the current Typescript/JavaScript ecosystem. Currently this is mainly around infrastructure as code and cloud services.