80K views · Oct 5, 2011 · 1:03:41 · 3 HN recommenders · 4 mentions · discussed 2011–2013
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.
Why Hacker News points people here: HN recommends it as the creator's own account of why Node was built and how he thinks about humility.
“He didn't want to use an ecosystem that had existing blocking code.”HN comment, 2012
“Love what Ryan Dahl has to say about being humble.”
Ryan Dahl on being humble
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.
“He didn't want to use an ecosystem that had existing blocking code.”
Why Node was built for non-blocking IO on a clean slate
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.
“This video gives some good insight into what led to his decision to start fresh”
Insight into why Dahl started fresh rather than extend Ruby
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.
“History of Node.js”
Why Node was created for event-loop servers
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
