It's not because Node.js is a new thing. It just that JavaScript is a client language, why would use it on a server anyway? Use the appropriate language for your projects and in this case it's Erlang.
EDIT: For all those Node.js zealots, thanks for downvoting.
JavaScript isn't a "client" language - it's a language designed to be embedded in a host system, which is exactly how Node.js uses it. Server-side JavaScript has been around since Netscape Application Server back in the late 90s.
...and it's quite clear that using it on the server is not that efficient compared to other languages that were designed to run on the server. The article proves that point.
I'm afraid you've confused a language with a particular virtual machine that runs it. That's like criticizing CSS because Internet Explorer implements it badly. The article proves nothing other than one particular JavaScript VM isn't as efficient as Erlang, not exactly a big surprise considering that's not what the VM was written for.
I think that he meant to say that V8 wasn't designed for long running processes like servers. In the browser it starts up, executes some code and then shuts down. Keep state around for a long time tends to lead to issues that take time to find / fix.
Comments
It's not because Node.js is a new thing. It just that JavaScript is a client language, why would use it on a server anyway? Use the appropriate language for your projects and in this case it's Erlang.
EDIT: For all those Node.js zealots, thanks for downvoting.
JavaScript isn't a "client" language - it's a language designed to be embedded in a host system, which is exactly how Node.js uses it. Server-side JavaScript has been around since Netscape Application Server back in the late 90s.
> It just that JavaScript is a client language
No, JavaScript is a language, it's been used on clients and servers for quite a few years now.
...and it's quite clear that using it on the server is not that efficient compared to other languages that were designed to run on the server. The article proves that point.
I'm afraid you've confused a language with a particular virtual machine that runs it. That's like criticizing CSS because Internet Explorer implements it badly. The article proves nothing other than one particular JavaScript VM isn't as efficient as Erlang, not exactly a big surprise considering that's not what the VM was written for.
the language has very little to do with efficiency or suitability for server / client side.
There's no such thing as "client" or "server" languages.
Turing-complete languages like Javascript can be used for any purpose, regardless of its most common application.
Someone has even written a webserver in PostScript: http://www.pugo.org:8080/
Javascript is particularly well suited to evented style programming because it has a very simple support of first class functions.
I think that he meant to say that V8 wasn't designed for long running processes like servers. In the browser it starts up, executes some code and then shuts down. Keep state around for a long time tends to lead to issues that take time to find / fix.
It has absolutely nothing to do with the language.
Oh but it is otherwise people would be using JS to move robots.
They are: http://www.ros.org/news/2010/08/javascript-for-ros.html