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

Channel:JSConf · Length:26:42 · Published:2018-06-06 · Views:662231

Watch on YouTube

Summary

Node.js creator Ryan Dahl discusses ten design mistakes he made in Node, including package.json, npm, and module resolution. The talk sets out the motivations behind his later project, Deno.

Why HN recommends it

HN treats it as the classic talk on why Deno exists and on lessons from design mistakes in a widely used platform.

Ryan Dahl's great talk on design mistakes he made with node.js is something I think about all the time — HN, 2023

Web development · Software architecture & design

Subtitles (excerpt)

Hello. Hey, so, yeah, I kind of wanted to give a different talk about some other stuff, but I wasn't ready, so this is a make-up talk. It's been some years since Node came out, and it's kind of stabilised, and it's a thing, and it's kind of going into its direction. I thought I would look back on it and tell you what I think about Node. So, sorry, I'm a little nervous. Excuse my wavering voice. Right, some background. I created Node and managed it through its initial development for a couple of years, and, my goal, as you may know was really around IO, and doing event-driven IO in JavaScript. I think that focus was really important in 2009 for getting server-side JavaScript off the frowned, because, as we know now, JavaScript is sing-threaded, and like - I'm sorry. And - sorry, lost my train of thought. JavaScript is single-threaded, blah, blah, blah, that allowed Node to succeed. I felt that Node was doing well in the IO department. Like we had protocol supports, like HTTP, and HTTPS, and we ported Node to windows using a nice systems calls IOCP, and we were running on Linux, Mac, and it had a relatively small core. I mean, it kind of got out of hand a little bit, but it was okay. It has a stable API, MPM was out, and there were people adding modules.

On Hacker News

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 chang… — bin_bash, 2023-01
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] ) — onetom, 2021-02
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 li… — bartlomieju, 2020-12
Deno [1] is a new JS runtime by one of the creators of NodeJS, Ryan Dahl. He had a great talk [2] about the lessons he learned when creating/maintaining NodeJS. Many of these lessons are being applied to Deno. [1] [LINK] [2] [VIDEO] — azemetre, 2020-06
I just hope in 5 years we're not seeing a talk saying that in retrospective, dropping static types was a huge error... and DoNe is a new project to fix issues like that! (I'm just referring to this nice talk about the regretful mistakes done in Node: [VIDEO] ) — j1elo, 2020-06

Related videos