Node.js: JavaScript on the Server

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.
Video Rating: 4 / 5

You can leave a response, or trackback from your own site.

Top incoming search terms for this post

25 Responses to “Node.js: JavaScript on the Server”

  1. a1mint says:

    aahhhh, uhmmm, unwatchable, ummm, uhmmm….
    trivial content too.
    NEXT !

  2. mmichelli says:

    Ryan is a clear and convincing speaker. Really impressed.

  3. thatmartolguy says:

    He’s very nervous to start with but after 10-15 minutes it begins to flow more freely and seems more coherent. Great library, definitely gonna try it.

  4. noagbodjivictor says:

    hope you all have memorized “ten thousand users” by now ;)

  5. yesudeep says:

    The “uhm”, “uhhh..” “um” “uhhhm…” is too distracting to pay attention to what he is talking about. Once you start hearing those uhms, understanding the content becomes hard.

  6. ollekullberg says:

    There is a typo on the “server.js” example, it should be:

    net = require(“net”);

    s = net.createServer();

    s.on(‘connection’, function (c) {
    c.end(‘hello’);
    });

    s.listen(8000);

  7. lorennorman says:

    The first few questioners get so hung up on the synchronous module loading, as if Ryan is contradicting himself or something, so obnoxious!

    We don’t care about synchronous calls during the ‘boot’ phase of a program like this: it should only happen once, and it’s downright tedious to register a series of nested ‘loaded’ callbacks just to load up (potentially dozens of) modules before we can begin to do the real work.

    Great talk!

  8. DevelX666 says:

    @lennyhome You think it’s not possible?

  9. lennyhome says:

    @DevelX666 “javascript”, “usability” and “accessibility” used in the same sentence. That’s interesting.

  10. supermegacobra says:

    Awesome presentation about an awesome piece of software. Ryan is real presenter, true to himself who cares about the content of the message, not the medium. He brings deep knowledge of Javascript, Unix and networks. His presentation can be summarized as ‘no fluff, just stuff’ about super efficiency a server-side scripting language. Keep it up Ryan.

  11. blenderpanzi says:

    @blenderpanzi Ah, it was the last question. Ok. It’s like I thought.

  12. grokus says:

    Ryan, sorry to say this, but please get help for learn to do a better presentation, it’s just so difficult sitting through your presentation.

  13. blenderpanzi says:

    Hm, all these .write() calls. They *look* blocking. Am I right that they queue the data in the background and do not actually block? So you never get an IO error with these function calls? (The error would be delivered to a – obviously optional – callback.)

  14. blenderpanzi says:

    Sounds all much like Python’s Twisted.

  15. DevelX666 says:

    @lennyhome I have never said that everything is always perfect or appreciated by everyone. All I’m saying is that there is also upper side of using javascript as it may be used to increase usability or accessibility – or annoy the user.

  16. lennyhome says:

    @DevelX666 What you just said makes no sense.

  17. DevelX666 says:

    @cosmos2k3 I think there are more reasons, like the better performance in all browsers, new API, more powerful CSS 3 and HTML5, larger applications using javascript etc. IE is just trying to catch up, but IE9 looks very good so far and I’m looking forward to it.

  18. DevelX666 says:

    @lennyhome 1) you don’t need javascript to do that
    2) any programming language may be used to do harm in some form. so using your standard, all programming languages are bad, genius ;)

  19. lennyhome says:

    @DevelX666 Also, thank you for proving me right. You said: “All modern browsers block popups automatically”. They do that exactly because otherwise javascript would open a metric ton of them per minute. Genius.

  20. cosmos2k3 says:

    @DevelX666
    I think javascript is getting more popular now. IE9 has put a lot of effort into making javascript run faster.
    jQuery is probably the main reason why javascript is growing, but javascript has been getting a poor reputation over the years.

  21. lennyhome says:

    @DevelX666 Youtube’s usability has, in fact, taken a a big nosedive since they did they javascript infected “channel redesign”. It brought several security issues, generated complaints, general slowness, annoyances, and absolutely no new useful feature.

  22. DevelX666 says:

    @lennyhome I respectfully disagree. Take for example gmail, basecamp, youtube, facebook, myspace, … they all use javascript and they use them for other things that opening porn popups.
    By the way… what kind of browser are you using? All modern browsers block popups automatically.

  23. linuxlist2000 says:

    hahaha love how he air quotes about erlan “processes”

  24. patrick132435 says:

    i like node.js and how it makes everyone speaking about javascript (i like javascript)

    ry ftw

    @lennyhome good point!

  25. lennyhome says:

    @DevelX666 Because javascript’s only purpose is to open porn popups.

Leave a Reply

You must be logged in to post a comment.

Powered by WordPress | Shop Free Phones at Bestincellphones.com. | Find the best CD Rates, Checking and Fat Burning Furnace Review

Powered by Yahoo! Answers