Hacker News Reader

Comment by _bxg1 | Hacker News Reader

I'm not very familiar with Nashorn, but could they just create a thin Java compatibility layer and outsource the bulk of the work to V8? Are there license issues with shipping V8 alongside Java?

View on HN

The author of this proposal, Jim Laskey, is also the one behind exactly what you're describing: Project Detroit.

see: http://openjdk.java.net/projects/detroit/

speculation: It looks like he wants Nashorn dead from any angle? GraalJS and V8, lol

I’m wondering why Project Detroit, and the background given in the Jim Laskey preso about it, isn’t mentioned in the JEP. I’m sure it would help quell the outrage. That project will basically be Nashorn compatible, with better performance and ES6 and Node support. I wonder how it relates to Graal and TruffleJS though. Seems a bit left hand/right hand from Oracle to have competing projects like this. For anyone interested in JS on the JVM Jim’s video is a must watch: https://www.youtube.com/watch?v=-JLhwsbMvjQ

Yup, if Jim is behind this then I am more trusting of the technical reasons.

I can't wait for the first release of Detroit - very exciting!

It's possible. It wouldn't run on the JVM, with JVM gc, JVM security, JVM in-process latency, etc.

The biggest problem is the latency, but yeah separate V8 works alright.

I thought Nashorn was part of this agenda of keeping the JVM relevant even if Java becomes less so.

I would guess Graal has something to do with this housecleaning.

I don't know if this implements the javax.script API, but it does allow you to embed V8 in Java programs: https://github.com/eclipsesource/J2V8

There was a talk about that at last Java ONE, I think, but there are no more news about it.

Reply on news.ycombinator.com