Added: 1 year ago
From: GoogleTechTalks
Views: 60,592
Sort by time | Sort by thread (beta)

Link to this comment:

Share to:

All Comments (69)

Sign In or Sign Up now to post a comment!
  • 1:41 - if you can dodge a wrench...

  • Sometimes, we, developers find it very hard to deliver material to a general audience.

    Bear with him and just try to figure out ;)

  • This is the future.

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

  • genius!

  • Awful start to a presentation... "uhhh.... ummm... uhhh..."

  • 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'.

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

    The guy knows his sh**

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

  • "DNS is so fucked."

    So true. DNS has to be the most unnecessarily convoluted system ever conceived.

    node === win

  • "There's great thing in unix called 'processes'"

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

  • @cybersalad 20:59 "Don't fear"

  • Does MVC exist in js?

  • @Fiil128 function view(model) { alert(model.msg); } function controller() { var model = {msg:"hello"}; view(model); }

  • @ironmagma  :D

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

  • Given the kinds of things this guy is talking about... non blocking I/O, thread safety, controlling side effects... I think he'd love Happstack or maybe the Snap framework. Hell he knows about Erlang but chose Javascript instead?! I guess he does wants simplicity and that's fine too.

  • DNS is FUCKED.  /Agree.

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

  • great talk.

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

  • I agree that is kinda hard to fallow the whole presentation, but if you have the desire to understand it...you will.

  • 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

  • I could care less about the speaking style. I often find brilliant tech people not great at speaking. That´s because they have a totally different way of thinking.

    The important part is that if you want to connect hundreds of people together in real time, with code you can understand and write in a few hours..... Ryan has made it possible and open source. That´s awsome. This is the third video of him speaking that I have watched and it has increased my understanding remarkably.

  • Why not make os threads less heavy?

  • Ryan is a clear and convincing speaker. Really impressed.

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

  • hope you all have memorized "ten thousand users" by now ;)

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

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

  • @ollekullberg Saw that too. Important catch.

  • 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!

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

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

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

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

  • Sounds all much like Python's Twisted.

  • hahaha love how he air quotes about erlan "processes"

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

    ry ftw

    @lennyhome good point!

  • Not a great public speaker.

  • Here goes another hour of my life.

    <3 node

  • @lennyhome Stop trolling and at least say why you think so. Everyone's a critic...

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

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

  • @DevelX666 "javascript", "usability" and "accessibility" used in the same sentence. That's interesting.

  • @lennyhome You think it's not possible?

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

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

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

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

  • @lazyd0g i think he meant that it _should have_ just been a hashtable instead of the clusterfuck that it is...

  • @lazyd0g they said it to try to say it's difficult, dont take it literally

  • best company ever!

Loading...
Alert icon
0 / 00Unsaved Playlist Return to active list
    1. Your queue is empty. Add videos to your queue using this button:
      or sign in to load a different list.
    Loading...Loading...Saving...
    • Clear all videos from this list
    • Learn more