>One thing to consider is that Node.js is not just a language you're learning but a whole different way of doing things. Node.js is also not a general purpose backend - it works well for certain high throughput scenarios but it's terrible for CPU bound processing (ie. anything sequential that's not truly asynchronous). It's great to learn Node and use it for things where it makes sense, but as a one stop solution that's a very bad choice.

Hi Rick,

Thanks a lot for dropping in.

"it's terrible for CPU bound processing... Node and use it for things where it makes sense, but as a one stop solution that's a very bad choice."

I understand that js engines have made impressive steps forward. However I still fail to understand what javascript can provide on the backend that, say, java, python, ruby or C# and al... Since as most of us I do appreciate your communication skills when it comes to complex IT matters, I'd be glad you could be a little more specific on the subject.

What is nodes.js, and server js by the way, bringing than the current toolset I am aware of (java, python, ruby....) and others are not? Id' be glad to get your javascript, where it currently stand in the arena and where are we possibly heading to?

Regards from Paris:)

François

PS: My background on those issues: server side vfp à la foxisapi and west-wind and python servlets à modpython. All this was years ago... Not currently working on server code..