Crockford on JavaScript - Scene 6: Loopage
Why Stack Overflow recommends it
Stack Overflow users link it when explaining the event loop and non-blocking style in JavaScript and Node.js.
Recommended by 3 people across 3 different months, 2011 to 2017.
What it is
Douglas Crockford's 2011 YUI Theater talk, the sixth in his series on JavaScript, argues that early languages made design mistakes around blocking and recursion that JavaScript's event loop can fix. He ties this to the rise of Node.js and server-side JavaScript. It is a 52-minute single-speaker lecture.
What people said
Recommends luvieere · 2011-08 · Stack Overflow · on “Eteration - explanation and example ”
Initially, I thought it was just a typo of iteration , as searching online for eteration yields no significant results. But, then, I came across references [LINK] that state that the term is coined by Crockford himself, in one of his talks. Online, the only place where I could find an explanation is on his page, in The Factorial Tutorial [LINK] , an article where, in Act 2 , as a comment to a code sample, he states: Act 2a: message iteration (eteration) This seems to be part of a related pair of terms, as his next code sample, that performs recursion without using a stack, contains the other member of the pair: Act 2b: message recursion (ecursion) So, it seems that eteration and ecursion are
Recommends Thomas Nadin · 2012-04 · Stack Overflow · on “None Blocking setTimeout(fn, 0)”
I have been using JavaScript as a tool for many years now, but only recently have I begun programming applications with it. After watching Crockford on JavaScript - Level 6: Loopage [this video] I have begun to appreciate the Event Loop and the style of not blocking. To better get to grips with this I have gone back to an app where I am believe I have a badly designed area of code. The application downloads an ~45KB JSON file (minified, uncompressed) containing ~20 elements, so on average each element has about 2.25KB of data. The download takes place every minute, as well as being manually triggered, at which point the new array replaces the old array. Every 15 seconds the DOM is cleared out and
Recommends Marco Scabbiolo · 2017-04 · Stack Overflow · on “How node.js single thread model process concurrent request?”
@TimWong Node runs an event loop, it is a different type of system, the implementation doesn't affect how the event loop works, and you don't need to worry about threads, you just have to understand the event loop. Of course a block in the event loop will block, thats how it works! View [this video] if you want to learn more.
Cites LXG · 2013-09 · Stack Overflow · on “Is it possible in .NET, using C#, to achieve event based asynchronous pattern without multithreading?”
Event loop is non-blocking and operate in one thread. Look here [this video] the above implementation is correct node.js is not the only way to implement event loop