HackerTubewatch
Surprise me
Frame from Ryan Dahl - History of Node.js Plays via YouTube's privacy-enhanced embed

Ryan Dahl - History of Node.js

phxtagsoup
Talks
YouTube
3 HN users recommended this talk3 months2011–2013 score 3
Years with an HN recommendation, 2007–2026

HN recommends it as the creator's own account of why Node was built and how he thinks about humility.

Ryan Dahl tells the history of Node.js and why he created it at a Phoenix meetup. He explains the push for non-blocking IO on a clean slate rather than extending an existing ecosystem.

“He didn't want to use an ecosystem that had existing blocking code.” (HN, 2012)

3 recommendations · 1 citations · Talks · intermediate

4 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@nodesocket Dec 2011 Recommends
on HN thread Trolls (2008)
Love what Ryan Dahl has to say about being humble. [this video] Honestly, happens almost daily, especially in SF. We meet awesome developers, but they are frankly arrogant assholes. This sort of entitlement results in those people trolling and flaming. Be humble, there are many smart people in the world; you're not that awesome.
Ryan Dahl on being humble
@SjuulJanssen May 2012 Recommends
on HN thread The love and hate of Node.js
This might answer your question: [this video] TLDR: He didn't want to use an ecosystem that had existing blocking code. He wanted node to be pure in te sence that nothing was blocking. Starting on a clean slate enabled him to get everything pure non-blocking from the ground up. He admits that Js isn't the best language. But his rationale for not using an existing ecosystem (when it comes to IO) is not bad.
Why Node was built for non-blocking IO on a clean slate
@sturadnidge Oct 2013 Recommends
on HN thread Rubinius 2.0 released
Read more
The creator of Node was something of a Rubyist, i believe the main reason was around the stdlib / ecosystem not being event oriented, making it difficult to build non-blocking applications. EventMachine may well have strategies to defeat this, I just don't know. This video gives some good insight into what led to his decision to start fresh rather than try and change things in Ruby [this video] So that's probably the biggest thing about Node - everything in the core is built with event orientation in mind, so you know you're not going to hit something that will block and kill you, and that minset is pervasive in userland too.
Insight into why Dahl started fresh rather than extend Ruby

Citations, criticism and jokes

@dsego Aug 2013 Cites it
on HN thread An Absolute Beginner's Guide to Node.js
Node was created to make scripting fast servers easy. Nothing more, nothing less. Because JS (as implemented in the browser and known by many programmers) didn't carry the baggage of blocking IO calls, Ryan thought it would be a good language for an event-loop based server. History of Node.js: [this video]
Why Node was created for event-loop servers

Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.

Keyboard shortcuts

/
Search
j k
Next / previous video
r
Surprise me
l
Like (video page)
w
Watch later (video page)
?
This help
Esc
Close