views:

329

answers:

2

Hey,

I've been wondering to try out server-side javascript for a while. And I'm finding a good amount of servers, like: Node.js Rhino SpiderMonkey among others.

Could anyone with experience on server-side javascript, tell me which are the best engines? and why? I like the Node.js because it's based on Google's V8 engine. And seems easy to use. But some feedback on what you would choose would be great.

Edit:

Some benchmarks for Node.

I'm thinking on going with this one but feedback is still welcome.

Thanks

+1  A: 

The word server is badly used. Those are different JavaScript implementations.

Personally the only thing I'm doubtful about these implementations is about the low amount of system libraries. Most of them come with standard stuff (sockets, filesystem etc..) but lack support for Threads and concurrency. That's why I usually use Rhino, unless I care for speed.

Luca Matteis
A: 

It might help to describe what problem you are trying to solve. There are a lot of "server-side" JS implementations that fill various needs. An there also several "server" platforms built around these implementations. I wrote one implementation on top of Rhino and Java Servlets, called Myna. Myna is for web applications, and I detailed some of its advantages in another question.

Are you trying to deploy web applications? Are you trying to script existing code? Does your code need to start quickly from a commandline, or is it going to be implemented as a daemon?

There are currently no clear winners in this space that do all of these things well, but there are good choices for specific needs.

Mark Porter
I don't have any needs specificly, i'm just trying them out
fmsf