Ryan Dahl talks about the history of Node.js and why he created it. This was filmed at the Phoenix meet up group Phx Tag Soup. http://tagsoup.github.com
@teddyknox You're right, that does explain how Node works a lot better. But the question was "how to explain Node to your boss", and I'm not entirely sure a lot of non-technical people would understand what "answering questions at the same time" means, or more importantly implies. I think they could more easily relate to having to wait for an answer rather than get the answer immediately...???
To help answer a question in this video about how to convince your boss to adopt node.js.
I think a good high level explanation of node.js and other web server platforms for non-technical people is:
How '[another web server platform] works' vs. 'how node.js works' is similar to asking a person a question. Node.js already knows the answer, and responds immediately. [another web server platform] doesn't know the answer, but will get back to you in one minute with a response (after googling)...
@elcapo1976 C handles concurrency just as well as Java (if you have the time), and he did say a thing or two about the beginning of Node when he made it a C-framework of sorts, and nobody was interested. Essentially you still have to do too much work yourself (a million classes comes to mind), whereas in JS everything is short and to the point.
So if Ryan Dahl would have started out using Java (which actually handles concurrency really well) instead of Mickey Mouse technologies like Rails and PHP, we probably wouldn't have Node.js today.
@teddyknox You're right, that does explain how Node works a lot better. But the question was "how to explain Node to your boss", and I'm not entirely sure a lot of non-technical people would understand what "answering questions at the same time" means, or more importantly implies. I think they could more easily relate to having to wait for an answer rather than get the answer immediately...???
joecorall 3 weeks ago in playlist Liked videos
@joecorall I had the impression that Node still didn't know the answer, but could find it while answering other questions at the same time.
teddyknox 3 weeks ago
tl:dr
Laur3ntLapo 3 weeks ago
To help answer a question in this video about how to convince your boss to adopt node.js.
I think a good high level explanation of node.js and other web server platforms for non-technical people is:
How '[another web server platform] works' vs. 'how node.js works' is similar to asking a person a question. Node.js already knows the answer, and responds immediately. [another web server platform] doesn't know the answer, but will get back to you in one minute with a response (after googling)...
joecorall 1 month ago
@elcapo1976 C handles concurrency just as well as Java (if you have the time), and he did say a thing or two about the beginning of Node when he made it a C-framework of sorts, and nobody was interested. Essentially you still have to do too much work yourself (a million classes comes to mind), whereas in JS everything is short and to the point.
athox 1 month ago
@bk2303 i see your like, and raise you uhm.
athox 1 month ago
like like like......
bk2303 2 months ago
Thanks Ryan, very interesting
alexeypetrushin 2 months ago
So if Ryan Dahl would have started out using Java (which actually handles concurrency really well) instead of Mickey Mouse technologies like Rails and PHP, we probably wouldn't have Node.js today.
elcapo1976 2 months ago
Some beer refresh mind @11:45 hehe
But this video is nice nodejs is something fantastic!
vitoracmm 2 months ago