If you follow the world of Web Development, you might have been recently hearing a lot about Deno - a new JavaScript runtime that might as well be considered a spiritual successor to Node.js. But what does it even mean, do we need “the next Node.js” and what’s all the buzz about?

What’s Deno?

To understand what’s going on, we first need to take a look at what Deno even is. Like I’ve said, it’s a new JavaScript runtime aka an environment where your JS code is meant to be executed. It was originally created by Ryan Dahl - the same nice guy, who previously brought us Node.js - hence all the comparisons.

Ryan announced Deno at his JSConf EU 2018 talk titled “10 Things I Regret About Node.js”. From that piece of information alone, you can see where this is going. Deno is created from the ground-up to be a better implementation of what Node.js currently is.

But what’s so bad about Node.js and how does Deno stack up against it’s more matured cousin?

#deno #node #javascript #typescript #web-development