News for hackers. Stuff that matters.

A comment on Vert.x (JVM async) vs Node.js Http benchmarks results. Parent comment

Re:Vert.x (JVM async) vs Node.js Http benchmarks results by manuscreationis on Wednesday May 09, 2012 @11:05AM (#3948890)
Seeing these numbers (although as the author states, the data needs to be taken with a grain of salt since he didn't try to set up a more "proper" test environment) really makes me want to take a serious look at vert.x, but what you mention here is my main concern.

Node is a joy to use because of the NPM, and all the available libraries. I'd hate to lose that.

That said, so long as it has a solid websocket api, and I can do routing in it like I would express, I'd give this framework a shot

[ Parent | on HN ]
Re:Vert.x (JVM async) vs Node.js Http benchmarks results by eropple on Wednesday May 09, 2012 @01:50PM (#3949684)
> Node is a joy to use because of the NPM, and all the available libraries. I'd hate to lose that.

Maven's not bad at all (from a consumption perspective--from a dev perspective, it's a bit of a pain in the ass), and it looks like pretty much any Java library that doesn't do anything too insane should work just fine. (Disclaimer: never used vert.x myself, but I did a quick scan of the code.)

[ Parent | on HN ]
Re:Vert.x (JVM async) vs Node.js Http benchmarks results by manuscreationis on Wednesday May 09, 2012 @03:43PM (#3950137)
Cool, thanks for the tip
[ Parent | on HN ]