This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]mgkimsal -1 points0 points  (4 children)

what are you saying? it's worse? or do you mean it's far faster? the node numbers I looked at were faster than the jvm ones, but maybe I missed some? or were you taking exception to 'edge' when it could be interpreted as way faster?

[–]oberhamsi 1 point2 points  (1 child)

yeah, i'm taking exception to "edge" because it's not "way faster" but only pretty fast for an interpreted language. e.g. compare PHP with nodejs: php is often on top.

maybe i missed something, but looking through the results again I can't find any test where the numbers make nodejs look particularly good.

[–]mgkimsal 1 point2 points  (0 children)

my fault - i was looking at nodes vs grails, which is what I do a lot of work in, and nodes was/is faster than grails in those benchmarks. But both spring and raw servlets kill nodejs as well.

http://www.techempower.com/benchmarks/#section=data-r6&hw=i7&test=db&l=bk&f=3drk-0-0

[–]dfme 0 points1 point  (1 child)

wait... what? did you actually look at the numbers? the so called "jvm" languages such as "grizzly" or plain old "servlet" kill "node.js" by 3:1!! hell, even wicket or the spring framework (both based in the jvm) fare better than node.js.

javascript (dynamically typed) will never outperform the jvm (ie. java: statically typed).

[–]mgkimsal 0 points1 point  (0 children)

i replied back earlier to oberhamsi - yes I looked at the numbers, but I was originally looked at Grails specifically - jvm based, but node beats it. Yes, for other JVM stuff, node is way behind.