Im not sold on node. Why should i ristrict myself? There are async librarys in lots of languages you can use them if you have a problem that suits the async modle but you can use other models to if they are better.
The other thing with node is that it is single threaded do do multicore you have to use process witch are slow in communicating. This could work now because we often only use quadcores but in the next years we will have many many more. Is it a solution to start node up for say 16, 80 or 1000 cores?
Im not ranting on node I hear it works fine for some stuff but the benchmarks that got everybody so exited in the beginning was not really that practical.
If I write a low level it might be fast because it maps to the C stuff good but if I write a big application with lots of layers of JS will it still be fast? (I know that V8 is getting better but it there jet for big server applications?).
Comments
Im not sold on node. Why should i ristrict myself? There are async librarys in lots of languages you can use them if you have a problem that suits the async modle but you can use other models to if they are better.
The other thing with node is that it is single threaded do do multicore you have to use process witch are slow in communicating. This could work now because we often only use quadcores but in the next years we will have many many more. Is it a solution to start node up for say 16, 80 or 1000 cores?
Im not ranting on node I hear it works fine for some stuff but the benchmarks that got everybody so exited in the beginning was not really that practical.
If I write a low level it might be fast because it maps to the C stuff good but if I write a big application with lots of layers of JS will it still be fast? (I know that V8 is getting better but it there jet for big server applications?).
Hope somebody can talks about this.
I don't get the threading criticism of Node, php and ruby are single threaded too (except for something like IronRuby which few people use).
The difference is PHP is thread (or, rather, process) per connection. Node is one process handing multiple connections.
PHP-FPM is a single process and is built into 5.3, though it requires some configuration.
http://interfacelab.com/nginx-php-fpm-apc-awesome/
Cool! Thanks for that... I'll definitely check it out. Looks like there are patches for earlier versions.
Thanks for the clarification.
I would never use PHP anyway but there you can use the hole server because the webserver does it for you.
Ruby does not? As far as I see JRuby does and is used a lot.
The diffrence really is that Ruby does not claim to be super fast and scale really good.