Lots of places are Java™ shops, and adding new shiny stuff from the NodeJS ecosystem for frontend work can be difficult. I couple years ago I had to build a weird multi-step build bridge between babel and the Grails asset pipeline. A pure JVM implementation would probably make this sort of thing less painful for a lot of companies.
Yep, lowers the entry barrier to add it to a project. I think most of the modern frameworks have decent support out of the box but for projects started a decade ago it's useful
ah! the memories of when I ran ember on rhino within a servlet container. fun thing was that some javascript reserved words are allowed in node and widely used. had to write a nodejs to vanillajs converter.
What? Where did they say that in that talk? They simply showed a way to execute native code with V8, so it's easier to run node on nashorn. Stop spreading misinformation.
There is no where they mentioned "replace nashorn", the main feature of nashorn is to interoperate with Java, V8 cannot do that. If you follow the development of Nashorn, they are working on ES6 features right now.
Also replace nashorn with V8 simply is a false statement, V8 is of it's own project established before Nashorn, and it doesn't even belong to Oracle, how can one replace a new project with an old one?
I prefer it's very cut and dry boundaries between Java and JS to Nashorn which tries to help by bridging Java into JS (but complicates both in the process)