Deno is Node Corrected

Node's author focused on async programming and left most everything else to fall into place on its own. Now with Deno he goes back to visit subsequent decisions that haven't worked out as well as they could have. site

YOUTUBE M3BM9TB-8yA Published Jun 6, 2018.

I tried to note the regrets as he spoke and seem to have missed one of the ten.

- no promises - no security - weak build (gyp) - no ffi - weak libuv autotools - weak package.json (require) - weak node_modules (vendored by default) - no extension (.js) on require - weak index.js

Deno reaches 1.0 release candidate 1.

YOUTUBE F0G9lZ7gecE Published May 5, 2020.

.

Is there anything you wish you had done differently with node? post (2011)

Yes - many things. For example, I wish I had not used the CommonJS module system. It's far too complex and wildly different from how the browser works. I wish I had not used the WAF build system, it works - it's okay, but it introduces more WTFs than necessary. I can perhaps dig out from under WAF at some point but it would be a monumental undertaking.

See also Trancending POSIX. login