Ryan Dahl: Node JS

Channel:JSConf · Length:48:32 · Published:2012-10-09 · Views:35332

Watch on YouTube

Summary

Ryan Dahl's JSConf EU talk introducing Node.js to the world. He explains the motivation for event-driven, non-blocking I/O, with JavaScript chosen mainly for its asynchronous nature.

Why HN recommends it

Cited as the primary source for why Node exists and why JavaScript was chosen, in debates about async models and language choice.

it's kind of refreshing to see the original node.js presentation, where using javascript is sort of a side-note — HN, 2024

Web development · Tech pioneers & interviews

Subtitles (excerpt)

[Music] foreign I'm going to talk about node uh so briefly uh so node is is a server-side JS platform it's built on Google's V8 um it does it i o in a very special way which I will describe in great detail it uses the common JS module system and uh it's written in C which has confused a lot of people so it's a rather large C project actually so the thesis is that I O has to be done differently um we're doing it wrong everything the way that we're thinking about doing IO really uh makes things difficult so writing servers and writing any sort of application is difficult because of how we're doing IO so uh a lot of web applications have such line of code like you query a database and then you return a result and then you use the result and so uh the question is what is your web framework doing well that while this line of code is running so in many cases you're not doing anything at all you're just sitting there while the database is waiting to respond and that might be uh that uh the uh database is in San Francisco or uh it might be thank you there's a lot of reasons uh okay well the point is is that you can't just wait for it to respond uh there's a big difference between what happens inside your CPU inside your memory and what happens

On Hacker News

And it keeps being polished and improved to the point it's almost not a turd, and now has types sort of, and much better engines, and now there are ARM machines that are literally designed to run it faster, and now most of your actual PC applications are written in it. But honestly it's kind of refreshing to see the original node.js presentation, where using javascript is sort of a side-note. He … — karel-3d, 2024-10
> Async/await was a terrible idea for fixing JavaScript's lack of proper blocked threading that is currently being bolted onto every language. As fun as it is to hate on JavaScript, it's really interesting to go back and watch Ryan Dahl's talk introducing Node.js to the world ( [VIDEO] ). He's pretty ambivalent about it being JavaScript. His main goal was to find an abstraction around the epoll()… — mrkline, 2023-09
> One of those environments is a GUI which is naturally a good application for async. The other is not. Backend web development is still largely input -> process -> output. Node is just shoehorning JS in, and pretending that JavaScript's weaknesses are strengths. Until you need to perform two or more IO operations at the same time (e.g. more than one of: database query, Redis query, HTTP request,… — throwitaway1123, 2024-08

Related videos