YUI Theater — Douglas Crockford: “Crockford on JavaScript — Scene 6: Loopage” (52 min.)

By YUI TeamAugust 30th, 2010

Douglas Crockford speaking at Yahoo! on August 27, 2010, as part of his Crockford on JavaScript lecture series.

Douglas Crockford’s latest installment in the “Crockford on JavaScript” series, a talk in which he covers the role of event loops and the importance of server-side JavaScript, is now available on video. Flash video is embedded below, or you can download the HD video (480p ~370MB). Video from the first five lectures is available on the Crockford on JavaScript page.

Other Recent YUI Theater Videos:

Subscribing to YUI Theater:


  1. For those curious about the Elko system mentioned at the end of the talk, a clickable link:


  2. His excitement at the end is truly palpable, and infectious.

    What I think is also important to consider is that we now must be super vigilant that what happened to client side JavaScript in its early days doesn’t happen to SSJS. We need the platforms and libraries that will be enabling the future to be stable, clean, efficient, and flexible. So in a word, professional.

    We have a tremendous opportunity to make the web grow quickly in the right direction. The lessons of OSS development and community collaboration will serve us well.

    Watch the video. Watch other videos about Node.js and get involved. Participate in the CommonJS discussion. Be belligerent gatekeepers of quality. And more than anything, share!

  3. This man is amazing, and I love his perspective and passion. What I wouldn’t give to sit under his tutelage sometime.

  4. Thank you so much Doug. You have taught me so much over the years!

    Loved this video!

  5. Jeffrey Gilbert said:
    September 1, 2010 at 8:36 am

    Having a 1-1 server to client relationship for your session handling means having a single point of failure for your site. It eliminates the possibility redundancy which means you could have blankets of user outages all at once. I guess the clever people at google and the session server authors will come up with a way to handle unresponsive servers to redirect the user to one that works, but where does the session state go if the lone server it was hosted on dies? or what happens when the session manager server dies? either of those are bad things. session redundancy distributed over many machines is a necessary evil.

  6. Doug,
    You are the coolest guy i’ve ever seen. You are my hero.

  7. Great series of vids. This guy is a legend!

    His commentary about the resistance of the software community to learning things which they don’t think they need is so accurate.

    From compilers, to structured code, to asynchronicity, we’ve always had to wait for a generation to retire and the next generation to take up the better techniques.

    Education is the key!

  8. non-blocking require() enhancement request for node.js: http://github.com/ry/node/issues/issue/282

    Feedback on proposed syntax highly welcome!