Node.js is one of those technologies that should not exist. Definitely, theoretically, is not supposed to have this kind of success. But like the bumblebee he don't know he can't and so it goes :-)
6. •javascript as the
primary language?
•server side programming
in javascript?
•server side programming in a
vm (v8) designed for a browser?
•mono-thread? what about multicores?
•wtf are all those callbacks? worse
than lisp’s parentheses
9. “On the
server side,
our entire
mobile
software
stack is
completely
built in Node”
http://venturebeat.com/2011/08/16/linkedin-node/
10. “There’s definitely
that concern, We did
an analysis of a
number of
platforms -- Ruby,
Node, Java, Scala”
But with a technology so relatively
new, is LinkedIn concerned about bring
a somewhat untested technology to an
already at-scale app?
http://venturebeat.com/2011/08/16/linkedin-node/
11. “We’ll
continue to
use it and see
how it does.
That’s how
we’ll make
our
technology
choices”
http://venturebeat.com/2011/08/16/linkedin-node/
12. They went from running 15 servers with
15 instances (virtual servers) on each
physical machine, to just four instances
that can handle double the traffic
http://venturebeat.com/2011/08/16/linkedin-node/
19. NPM (2010-11)
(node package manager)
coder@apollo:~/Work/src/node/examples$ curl http://npmjs.org/install.sh | sh
...
npm ok
It worked
coder@apollo:~/Work/src/node/examples$ npm list | wc -l
1776