The goal of Node.js was supposed to be that you can use the same language in both the client and the server. So you can share code and reduce context switching, making development easier.

But now the two are so different, it's like they are two different languages. The original purpose is no longer served.

Now it requires a bunch of polyfills, shims, and build tools to make them interoperate. Half the time is spent pulling your hair out instead.

Node.js is living in an alternate reality clown world, while Deno is behaving like an actual modern web browser. Things "just work" between Deno and the web, once again fulfilling the original mission of why Node.js even exists. 

 @Alex Gleason what if it happens again and 2 years from now you're using build tools to dump roly poly beetles into your deno and talking about switching to cumjar.js
i miss when applications were written in C, errors in ./configure would tell you pretty much exactly what library you needed to install, and you didn't have to learn how to deal with the quirks of node and python and docker and php modules

https://media.wolfgirl.bar/50b56806a7cf8ce25d95f6b809b3c635b79f399ee44f8bb80100d48a590f84fc.jpg 

 Legit concern. Here is proof they're trying to avoid that.

Also, when Node.js was created, it wasn't even possible to create a JavaScript program with multiple files. Now that the basics are covered I don't think it will need to change as much.

https://media.gleasonator.com/8cfae89a9091ce77e6be302613e1268fdb99118bd1d796b6dba472b7975cedbe.png