A lot of people in the industry are saying “oh well, there isn’t any competition between Deno and Node, there is a lot both can learn from each other”.
To some extent, I agree, there’s a lot Node and Deno can learn from each other. But there’s no competition? I completely disagree with that.
Let’s look at common features of Deno and Node:
- They’re both runtime environments for JavaScript
- They both run on any computer where you can run V8
- They both have ECMAScript standard support
- They’re both actively maintained
If you become a “Deno” fan 2 years down the road, you are never going to choose Node for your next project. It’s just not possible.
Similarly, if you’ve never worked with TypeScript before, and you think you want to try Deno, but maybe you want to have some NPM modules, you wouldn’t choose Deno.
That’s right: there is a division of developers across Deno and Node - I would say that’s a very good example of a competitive space.
Note: This is going to be a controversial article, and I would really appreciate if you could control your emotions and read the full article till the end, and maybe then decide what you think. I have my social media links at the bottom of the article and would love to have a healthy discussion on this topic.
#node-js #deno #web-development #javascript
