4 ms·
Nashorn is said to be high-performance, and I've looked around for benchmarks several times since it was announced, but I still can't find anything but this: h
by hansjorg 13y ago
Nashorn is said to be high-performance, and I've looked around for benchmarks several times since it was announced, but I still can't find anything but this:
https://github.com/tadas-subonis/java-nashorn-performance-sandbox https://github.com/tadas-subonis/java-nashorn-performance-sa...
What gives? Wouldn't a real comparison to Rhino and V8 (at least) be interesting?
Edit: strike that. Found someone who ran Octane and SunSpider and compared it to V8 and Spidermonkey: http://wnameless.wordpress.com/2013/12/10/javascript-engine-benchmarks-nashorn-vs-v8-vs-spidermonkey/ http://wnameless.wordpress.com/2013/12/10/javascript-engine-...
- eropple 13y agoI've been using JDK8 for a while, but no Nashorn on Android keeps me on Rhino. Which is unfortunate. Rhino's a pain.
- suyash 13y agoNashorn is going to get faster with time. It is not a browser engine so don't try to compare it directly with V8 etc.
- camus2 13y ago> Nashorn is going to get faster with time. It is not a browser engine so don't try to compare it directly with V8 etc. v8 is not a browser engine either ,it's a javascript engine,just like Rhino. you are mixing up Webkit with v8.
- suyash 13y ago"v8 is not a browser engine either ,it's a javascript engine,just like Rhino. you are mixing up Webkit with v8." - I think you're partly correct but also confused. Webkit is a rendering engine and yes V8 is a JavaScript engine not a browser engine that was created for Chrome Browser by Google. It's used for Node.JS etc now but it's sole purpose was to make Chrome faster and that is not the same purpose of Nashorn - nashorn is a replacement for Rhino. That is what I'm trying to say.
- Skinney 13y agoAnd Nashorn is supposed to be faster than Rhino... Nashorn and V8 are both JS-engines, why wouldn't you compare them?