My take: node'sand vert.x's goals are different. Vert.x aims to make the async programming model available and convenient on the JVM, node's initial goal was to make it easy to develop network networked apps using http.
Node's target aren't highly scalable apps (like for example Google's search request handling), it's something for building a remote control with a web interface for your AVR, automating testing for a web service, mocking out a web server for integration tests of a client application or similar tasks. Vert.x wants to be serious competition for Akka and a serious alternative to servlet containers for developing network applications, allowing developers to build highly scalable apps, reachable over http but not necessarily tied to the http protocol, easy to deploy, take down, distribute, reconfigure and whatnot. One is lightweight and focussed on ease of configuration, deployment and development, the other one is heavyweight and focussed on performance. You can't really compare the two unless you plan to use one of them in a context it's not intended for, IMO. I will for sure not give up on either of them, in spite of the performance differences. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
