3 ms·
"Java or C will be much faster at any computational work" That is far from clear. I've been using nodejs for some computational work using https://github.com/
by niggler 14y ago
"Java or C will be much faster at any computational work"
That is far from clear. I've been using nodejs for some computational work using https://github.com/substack/gamma.js https://github.com/substack/gamma.js and https://github.com/niggler/bessel https://github.com/niggler/bessel and found that the JS version is faster than the straightforward Java implementation.
- halter73 14y agoThe OP made too general of a statement because there are certain cases where V8 can preform better than the JVM; however, generally Java does seem to perform better (ignoring startup time). http://benchmarksgame.alioth.debian.org/u64/benchmark.php?test=all&lang=v8&lang2=java http://benchmarksgame.alioth.debian.org/u64/benchmark.php?te... In the linked benchmarks, V8 only has a decided advantage executing regexes.
- gritzko 14y agoHeh. Last time I checked v8 regexes were really fast, except their string builder was a disaster... it wrapped every piece of string as a js object (gc and everything).
- Cthulhu_ 14y agoSounds familiar to Java's own string concatenation. In Java you use StringBuilder / Buffer to create larger strings from smaller ones; in Node you'd use Buffers, although I never dived too deep into those.
- loeg 14y agoWell, C will be faster anyways... and the JVM is probably faster than v8 more times than not.