10 Things I Regret About Node.js - Ryan Dahl - JSConf EU

What people said

bin_bash · 2023-01 · Strong recommendation

Ryan Dahl's great talk on design mistakes he made with node.js is something I think about all the time: [VIDEO] Even though he considers things like `require('./something')` defaulting to either `./something.js` or `./something/index.js` a mistake, he also admits these are not possible to change at this point. I think Python made a mistake trying to correct design problems in 2. The cost of change simply wasn't worth the price of migration. Is `print("text")` really that much of an improvement over `print "text"`?

Read the original HN comment ↗

onetom · 2021-02 · Recommendation

Recommended "literature": 1. 10 Things I Regret About Node.js - Ryan Dahl - JSConf EU ( [VIDEO] ) 2. Brendan Eich: JavaScript, Firefox, Mozilla, and Brave | Lex Fridman Podcast #160 ( [LINK] )

Read the original HN comment ↗

bartlomieju · 2020-12 · Recommendation

Deno is a JavaScript runtime much like Node. For the reasons on why creating Deno I recommend "10 Things I Regret About Node" by Deno's author [1] Deno is different than Node in several aspects; most notably: - Deno supports only ES modules, there's no built-in support for CommonJS modules - Deno's APIs are all promised based - Deno does not use NPM, instead it can pull code from any URL, much like browsers do - Deno has built-in permission system that by default runs your code in full sandbox allowing to opt-in into breaking out of sandbox (eg. to read a file from disk) - As you've mention Deno can run .ts files without explicit build step - Deno comes with a full toolchain in a single binary (formatter, linter, test runner, bundler, doc generator) [1] [VIDEO]

Read the original HN comment ↗