63 Comments

  • Martin Jurča

    @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.

  • lennyhome

    @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.

  • lennyhome

    @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.

  • Martin Jurča

    @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 😉

  • Martin Jurča

    @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.

  • Martin Jurča

    @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.

  • bloody_albatross

    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.)

  • Jinsong Huang

    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.

  • supercobra thatbytes

    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.

  • Loren Norman

    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!

  • Olle Kullberg

    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);

  • Henrique B

    Amazing guy, brilliant technology, unfortunately his presentations are very hard to watch. It isn't because I can't understand it, but because he doesn't have a fluid speech and I found it very hard to follow . I will stick with the documentation and html tutorials for now. But great technology nevertheless

  • InformBureau

    Let's be clear – this is an awesome technology and Ryan deserves highest credit for developing it.

    The other aspect is the presentation itself – it is quite hard to follow, maybe just not polished enough yet, maybe he needs more practice speaking in public speaking – not as fluid and engaging as it could be.

    I don't think that being a technical person is a legitimate excuse for the lack of presentation skills, there are heaps of technical specialists with exceptional public speaking skills.

  • ckaye9

    It's hard to understand these criticism's of Ryan's presentation skills. I found his presentation not just clear, but remarkably thorough. Not only does he lay out the impetus and defining elements of the node.js architecture, he also contextualizes it with a healthy dose of general background covering server architectures and network communications. Sure, his style of speaking might be a bit jerky, but if smoothness is your litmus test for a "good" presentation, it's really your loss.

  • Michael Ernest

    Ryan's halting speech was off-putting at first, but I got accustomed to it quickly. In the brief review I have done so far on node.js, this resource ranks tops for me. The concepts are few, clearly stated, and (I think) easy to identify in the examples given.

    I'm surprised that none of the blog entries or other articles I saw before this presentation got me further along or as motivated to do more. I'm excited to dig in now.

  • superoldboy

    I think the achilles heel of node.js right now is the lack of multi-core support. Load balancing to multiple node.js processes should be a standard part of the deployment, I guess. At least for now.

  • devryan

    His speech does seem halting in this one, but I think he seems nervous for some reason here. In another video I watched it was much different from this, and easier to follow. The NodeJS project is amazing, still trying to master the concepts.

  • OnePieceWonPeace

    Of course, his communication skills lacked (at least till the end), but man… great presentation.

    The guy knows his sh**

  • JamesRCoston

    We own a lot of credit to the DNS. Although, it is now probably coming to an age where technology is changing, it is most definitely not 'fucked'.

  • bourgeoisbrats

    He's not presenting…he's mentoring to "his peers", who probably have a similar delivery style. That being the case, I don't think it's terrible to have all the "umm" and "uhhh" words.

  • Joey Garcia

    Watch the video for it's content, this is not a Toastmasters video, so just skip over any of his "uums", he has something worth sharing, so be grateful that he is sharing his thoughts. Thanks Ryan!

  • carsten

    If every important function is supposed to be non-blocking and have a lambda argument, they could just invent a new language where the compiler decides itself when to turn a couple of statements into a lambda or something. the whole thing feels clumsy in JS as it is

  • TheFerdi265

    @Siddharth Shama Node.js doesn't actively depend on it, but it uses it for builds when downloading packages: NPM (node package manager) downloads and rebuilds packages (e.g. packages that aren't pure js and contain a bit of c) and uses something called node-gyp which calls python 2.7.x.

  • Abdelhakim Lahrach

    LIMITED TIME OFFER
    https://www.udemy.com/nodejs-tutorial-from-scratch-by-examples/?couponCode=NewOffer

    1.Lifetime access to 24 lectures
    2.Over 120 mins of high quality content!
    2.Join to a community of over 2687 students learning together.
    4.Course information and regular updates
    5.Learn node.js and mongoDB from scratch by examples.
    6.Course information and regular updates.
    7.Discussion forum, which we encourage you to make use of — both to pose questions about the material to the course instructor and to exchange ideas with your classmates.
    8.High quality course support.

  • Antha Chetta

    I found these videos which are exceptionally good for beginners: https://www.youtube.com/watch?v=epH81xhS6mk&list=PLvZkOAgBYrsQVc9PFn8mQ-xXef9zmy3kC

  • Saúl Martínez Vidals

    If you are too worried about the "ummhh … ahhh" then go directly to StackOverflow and ask how to get your job done.

    This talk if for the ones interested in how does nodejs works internally and have enough knowledge about IO, networking and other stuff to appreciate how awesome this guys is.

Leave a Reply

Your email address will not be published. Required fields are marked *