Skip to content
Hallway
0:00 / 0:00

#node.js#ryandahl#eventloop

Ryan Dahl: Original Node.js presentation

stri8ted

14K subscribers • 1 video on Hallway

YouTube
  • Recommended by 5 people: 3 on Hacker News, 1 in engineering communities and 1 curated list.
  • A classic. People kept recommending it from 2015 to 2022.
  • Presented by Ryan Dahl, creator of Node.js
  • May be out of date. Uploaded 14 years ago, in an area where tools change fast.

Intermediate. Assumes working knowledge.

234K views14 years ago5 recommendations

Web developmentHistory and cultureNode.js, Deno and BunWeb performanceConcurrency and parallelism

Ryan Dahl introduces Node.js at JSConf 2009, pitching event-driven, non-blocking I/O in JavaScript as a better way to handle concurrency.

The first presentation on Node.js from Ryan Dahl at JSConf 2009

Why it's here

5 people recommend this

What people say. Highly recommended as a historic and energetic tech talk that introduced Node.js and changed server-side web development.

u/jucrouzetin r/node • Recommends

Ryan Dahl's original Node.js presentation.
24View on Reddit

samblron Hacker News • Recommends

On “Ask HN: What's your favorite tech talk?”

There is a sort of palpable energy in (Ryan Dahl) node.js original presentation. link to this video edit: +Ryan Dahl
View on Hacker News

programming-talkscurated list on GitHubRecommends

Under “JavaScript”

The first ever presentation on Node.js 00:48:31 by **Ryan Dahl** (2012)
View the list

knbknbon Hacker News • Recommends

On “Ask HN: What are some of the best technical talks you've heard?”

I like the talk by Ryan Dahl, node.js inventor Original Node JS Presentation, 2009, link to this video In 2018 he gave a follow-up presentation "10 things I regret about node", but that presentation is more for experts.
View on Hacker News

swyxon Hacker News • Recommends

On “Ask HN: Best dev tool pitches of all time?”

i also asked this on twitter so just putting some replies here: - Doug Engelbart link - Twilio link - Stripe - "7 lines of code" - Netlify - link - Heroku - link and git push heroku master - Cloudflare - link - Node ( link to this video ) and Deno ( link ) - Firebase (reportedly) - link smaller companies/less impactful pitches that i still like - Redux link - Stackblitz link - Comm link - Mongodb link - Let's Encrypt link - Figwheel-Clojurescript link - Svelte link
View on Hacker News

alexc05on Hacker News • Mentions

On “A love letter to jQuery”

…ink it's really useful to think of that as asynchronous code. It appears I'm using async as a term interchangeably with non-blocking... which may not be correct. So it may be the case that my nomenclature is off, but I'm sure I got that from somewhere. Perhaps a lot of people were referring to node as async in the early days, I'm re-watching this: link to this video now, but it doesn't look like Ryan Dahl uses the term async. Anyways, looks like I'll have to train myself to use the right word for it. Thanks for pointing that out without making me feel dumb or being all insulting and internet-y. :) I really appreciate that. EDIT: Hmmm... additionally, to be fair: it appears that some agree that it is OK…
View on Hacker News

e12eon Hacker News • Mentions

On “Deno 1.4”

See also - post on original nodejs presentation: link (was a surprisingly large number of dead links on hn regarding this one). I believe this is a copy of the video: link to this video
View on Hacker News

jorisdon Hacker News • Mentions

On “Deno 1.9”

The third slide of Ryan Dahl's 2009 JSConf.eu presentation ( link to this video ) covers most of the reasons for why it was made: "I/O needs to be done differently". Evented I/O via event loops wasn't really that much of a thing back then, and many server-side web frameworks were simply sitting idle whilst waiting on I/O. Node changed this, and thereby enabled a kind of concurrency that was easy to achieve and there by default, often without the programmer really realizing it, because they didn't have to do anything too special to get it done other than write JavaScript with callbacks. I don't think JavaScript was really the point of it. (EDIT: but JavaScript having functions as a first-class citizen,…
View on Hacker News

danShumwayon Hacker News • Mentions

On “JavaScript Is Weird”

Edit: here's the actual presentation, not just the slides: link to this video What's interesting about this talk is that Ryan doesn't even mention Javascript at all (other than briefly to say that NodeJS is built on it) until nearly 13 minutes into the presentation. And it's clear that he's using Javascript as a means to an end -- he's going with Javascript largely just because Javascript by default has a single threaded event loop that every JS programmer had to learn to work with it. So he brings up going with JS because JS programmers are used to callbacks already -- and then roughly 2 minutes later he immediately moves back to talking about I/O and request handling again. Very little of his present…
View on Hacker News

u/Normal-Programmer-51in r/node • Mentions

why is node high level? A few weeks ago I saw the initial node.js presentation on JSConf 2009 (link: link to this video and multiple times during this event he mentions why Node is low level, and that's what made it so incredible and bla bla bla now, 15 years later, we're here, with one of the most high level ecosystem of all. to the point we don't even write \`n % 2 ===\` and prefer to \`npm i is-odd\` instead. any takes on why is that and what brought us here? I'd guess its related to Node also being used for front-end ecosystem (and all complexity of it in terms of bundling, building, and so on).
0View on Reddit