Deno is here to replace NodeJS. Or, at least, it has the goal to do so and to fix NodeJS‘ biggest flaws. it comes with some pretty interesting built-in features like TypeScript support and more.
However there is no exact answer to this, For starters, Deno is the creation of Ryan Dahl, also known for the creation of a little thing called Node.js, sounds familiar? Does that mean Deno is automatically a de facto replacement for Node and we should all start planning our refactoring sprints? Heck no! But if you want to know more, keep reading!
In 2018, Ryan gave a talk where he covered the top 10 things he thought were wrong with Node.js, and at the end of that presentation, he unveiled Deno, back then it was just a small project where he was building what you’d call Node.js v2, improved and more secure.
Here is a rundown of some of the features which were added to the Deno runtime:
- Security is integrated
- A more complete standard library
- Integrated Typescript
- No more NPM or node_modules folder
There are other features included by Deno, such as bigger tooling out of the box with things such as a test runner, debugger, file watcher, and others. But then again, some of these are just APIs provided by the language, and you need to code your own tools in order to use them.
However, “It hasn’t been tried and tested in production systems yet. It hasn’t been reviewed and put into weird and unintended use cases to see how it deals with those border situations.”, https://blog.bitsrc.io/ reported
“And until it does, it’ll just be a toy for early adopters to play with. Maybe in a year, we’ll start hearing from companies sharing their experiences with it, how they’ve solved the newly found shortcomings, and eventually, the community behind it will adapt it to a point where it is useful. Will it replace Node then? Who knows! We’ll have to wait and see.” https://blog.bitsrc.io/ added.