Skip to content
Hallway
0:00 / 0:00

#node.js#deno#package.json

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

JSConf

286K subscribers • 28 videos on Hallway

YouTube
  • Recommended by 9 people: 6 on Hacker News, 1 on Lobsters and 2 in engineering communities.
  • A classic. People kept recommending it from 2018 to 2023.
  • Presented by Ryan Dahl, creator of Node.js
  • Linked in the descriptionry/deno
  • May be out of date. Uploaded 8 years ago, in an area where tools change fast.
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

661K views8 years ago9 recommendations

Web developmentSoftware designNode.js, Deno and BunSoftware architectureAPI design

Ryan Dahl discusses ten design mistakes he made in Node.js, including package.json, npm, and module resolution, which motivated him to build Deno.

See also github.com/ry/deno JSConf EU is coming back in 2019 2019.jsconf.eu/

Why it's here

9 people recommend this, 1 disputes it

What people say. Widely cited by developers as a classic talk on software design trade-offs, API design mistakes, and the origins of Deno.

Moments people linked to

u/pier25in r/node • Recommends

10 Things I Regret About Node.js - Ryan Dahl
260View on Reddit

u/io33in r/node • Recommends

10 Things I Regret About Node.js - Ryan Dahl - JSConf EU 2018
132View on Reddit

yumaikason Lobsters • Recommends

10 Things I Regret About Node.js
48View on Lobsters

bin_bashon Hacker News • Recommends

On “Breaking the Snake: How Python went from 2 to 3”

Ryan Dahl's great talk on design mistakes he made with node.js is something I think about all the time: link to this 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"`?
View on Hacker News

azemetreon Hacker News • Recommends

On “Design Doc: Use JavaScript instead of TypeScript for internal Deno Code”

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 link to this video
View on Hacker News

j1eloon Hacker News • Recommends

On “Deno will stop using TypeScript”

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: link to this video )
View on Hacker News

kybernetikoson Hacker News • Recommends

On “Deno will stop using TypeScript”

Well, in all the initial presentations Ryan Dahl gave about Deno, he phrased it as solving the things he'd come to realise he hated about Node. So that's what I take as the raison d'être of Deno - taking the lessons he'd learned from some years mainly coding Go and thinking about what he'd learnt from Node, and fixing what he could. Here's the classic video on the topic: link to this video
View on Hacker News

bartlomiejuon Hacker News • Recommends

On “Deno 1.6 supports compiling TypeScript to a single executable”

…- 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 link to this video…
View on Hacker News

onetomon Hacker News • Recommends

On “Choose Boring Technology (2015)”

Recommended "literature": 1. 10 Things I Regret About Node.js - Ryan Dahl - JSConf EU ( link to this video ) 2. Brendan Eich: JavaScript, Firefox, Mozilla, and Brave | Lex Fridman Podcast #160 ( link )
View on Hacker News

echopomon Hacker News • Disputes

On “Deno 1.10 Release Notes”

…o the language since it's origin.;. Deno doesn't seems to address those at all... Again it's just seems to be "npm is bad , and i want to use typescript natively with web apis"... I just know very well that Ryan is redoing exactly the same mistakes as Node with the same obsession he had on "EPOLL"0 back then that will end up in a new fiasco. 0 link to this video Can't find the specific part where he mentioned "EPOLL"…
View on Hacker News

u/JumboTruckerin r/node • Mentions

Why is `index.js` a mistake in node.js? Ryan Dahl mentions in JSConf I recently watched a video by JSConf on YouTube [video He says that adding \`index.js\` was a mistake. I don't understand why. I am supposing he is taking about the index.js we have in a folder which lets us export content from other files within the folder using a single \`index.js\` file. I think this is a good feature. I see many libraries use it. I see that \`bulletproof-react\` which suggests good ways to write React code suggests to use \`index.ts\` as well Can somebody please explain why was this a mistake? Should I avoid it? Thank you!
95View on Reddit

u/DuckDeskin r/typescript • Mentions

On “Deno, a typescript runtime, has been rewritten in rust and released v0.1”

The guy who created this project is the same person who created the nodejs project. For information about this project you can see his talk from JSConf.
6View on Reddit

whatever_dudeon Hacker News • Mentions

On “Design Mistakes in Node [pdf]”

These are the slides to Ryan Dahl's presentation at JSConf EU 2018. A video of the presentation is here: link to this video
View on Hacker News

steamer25on Hacker News • Mentions

On “ESLint compromised, may have stolen your credentials”

In a recent video, Ryan Dahl mentioned that he regrets incorporating package.json and NPM into Node: link to this video He has a very early attempt at breaking from compatibility with Node called "Deno". Here's the part in the video about his current thoughts on importing external modules under Deno: link to this video He has some other security proposals as well.
View on Hacker News

apoon Hacker News • Mentions

On “ECMAScript modules in Node.js: the new plan”

Meanwhile, Deno (alternative server-side JS built from scratch by the creator of Node) keeps chugging along: link It will be interesting to see which happens first: developers migrate to Deno or Node finalizes its ES module implementation. I think both groups are doing excellent work, but the Node team seems to be at a disadvantage having to continue support for some decisions made early on in Node: link to this video
View on Hacker News

lioeterson Hacker News • Mentions

On “A new decade, a new tool”

> ..The node_modules package resolution algorithm is how JS does namespaces.. I wonder whether they got that right through sheer genius, or by accident. I recall hearing Ryan Dahl's regrets about design decisions in Node.js, a few of which had to do with the module/package resolution algorithm. 10 Things I Regret about Node.js - link to this video There are some good aspects of it though. I like how modules/packages are just imported objects (the path resolution is a bit weird and seemingly inefficient, i.e., checking every parent folder's node_modules folder). It goes together well, that modules are also self-contained function scopes by default (I suppose a kind of anonymous namespace), that exports…
View on Hacker News