Re:Node.js is Backwards
by daleharvey on Tuesday June 14, 2011 @07:07AM
(#2652528)
Re:Node.js is Backwards
by ricardobeat on Tuesday June 14, 2011 @08:53AM
(#2652745)
Putting it in words for those too lazy to click: node.js is built into webOS.
plurk
Not large and not Node.
That's not their backend, it's just servicing a front-end feature.
It's doing what normally Erlang would have been used for, which answers the original question. It's a node.js deployment, and very early version one at that. I'm not really sure what your point is.
Re:Node.js is Backwards
by ricardobeat on Tuesday June 14, 2011 @08:52AM
(#2652740)
Plurk actually gave up on node after failing to optimize their service and went back to Netty (http://amix.dk/blog/post/19577). A better answer is this: https://github.com/joyent/node/wiki/Projects,-Applications,-...
At work, every time we undertake a project in Node, it just doesn't work at scale, and it has to get re-implemented in Erlang.
A lot of this is for personnel reasons. To all of us Node is a neat new toy, where a few engineers are Erlang wizards. If Node crashes we don't have any experience debugging it. If it locks up there's little intuition why.
Can people point to examples of large production Node deployments?