u/vl4kn0in r/node • Recommends
Node.js: JavaScript on the Server, Google Tech Talk,
presented by Ryan Dahl
0:00 / 0:00
Node.js: JavaScript on the Server
Google TechTalks
349K subscribers • 65 videos on Hallway
- Recommended by 2 people: 2 in engineering communities.
- A classic. People kept recommending it from 2012 to 2017.
- Presented by Ryan Dahl, creator of Node.js
Intermediate. Assumes working knowledge.
135K views16 years ago2 recommendations
Systems programmingProgramming languagesNode.js, Deno and BunJavaScriptConcurrency and parallelism
Ryan Dahl explains the design of Node.js, combining the V8 JavaScript engine with an event loop for high-performance server-side software.
Google Tech Talk July 28, 2010 ABSTRACT Presented by Ryan Dahl, the creator of the node.JS open source project. It is well known that event loops rather than threads are required for high-performance servers. Javascript is a language unencumbered of threads and designed specifically to be used with synchronous evented I/O, making it an attractive means of programming server software. Node.js ties together the V8 Javascript compiler with an event loop, a thread pool for making blocking system calls, and a carefully designed HTTP parser to provide a browser-like interface to creating fast server-side software. This talk will explain Node's design and how to get started with it.Why it's here
2 people recommend this, 1 disputes itWhat people say. Recommended as a great way to understand the design decisions and history behind the creation of Node.js.
Moments people linked to
u/The_frozen_onein r/node • Recommends
On “What node.js CANNOT do?”
> Someone wanted to take JS out of browser and use it for server/general purpose programming.
Just to expand on what you're saying, here is a presentation of Ryan Dahl's (creator of node.js) from 7 years ago where he walks through the decisions that led to node's creation. That video is a really great way to understand how and why node.js was created, and I would highly recommend watching it to anyone who wants to learn more about node.
Essentially, he liked writing asynchronous (callback driven) code in C, and had the realization that virtually everything in JS executed as a callback. It seemed like a natural fit for writing high performance network services. There are other reasons too…
u/marcfaselin r/node • Disputes
On “Ryan Dahl video - History of Node.js”
This presentation is actually not that bad. If you want to see a bad presentation by Ryan watch his GoogleTechTalk link to this video
u/The_frozen_onein r/node • Mentions
On “Multithreading in Node.js”
> Still boggles my mind to see at the height of multi-core cpus, one of the most popular languages is inherently single threaded and requires you fork a new process to emulate threads.
That's the thing, you don't have to fork to emulate threads, this is a misunderstanding. You just use normal non `-Sync` functions and it "emulates" threads right out of the gate. Each node process can do the work of many threads without the overhead each thread brings with it. That's kinda the point, actually. An http stream in node costs just 36 bytes. Spawning a new thread or process for each connection is a nice way to spend a lot of your CPU time context switching, which is something node avoids.
Try…
u/The_frozen_onein r/programming • Mentions
On “Electron is flash for the Desktop”
> CSS is simply properties on objects (HTML tags and element identifiers (id/class)), so there's nothing novel with that idea, except you aren't able to dynamically change them, or perform any computation without JS. I do believe this is the correct approach, although I've honestly never given it much thought previously. I'm unsure if there are any decent alternatives.
Sounds like somebody hasn't looked into CSS in a while :)
`calc` lets you do math directly in CSS, even stuff like subtracting `px` from `%`. It's safe to use, and there are even some games written using just CSS.
There is a little more to CSS than just a list of properties (like element specificity and a comprehensive sele…