Re:React-material-ui with a pure Java stack
by kevan on Tuesday August 29, 2017 @01:10PM
(#15125803)
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.
Re:React-material-ui with a pure Java stack
by kevan on Tuesday August 29, 2017 @02:26PM
(#15126480)
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
Re:React-material-ui with a pure Java stack
by LoSboccacc on Tuesday August 29, 2017 @12:45PM
(#15125583)
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.
Re:React-material-ui with a pure Java stack
by issaria on Tuesday August 29, 2017 @01:58PM
(#15126230)
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.
Re:React-material-ui with a pure Java stack
by issaria on Wednesday August 30, 2017 @07:01AM
(#15131120)
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)
Check this year's Java Languages Summit.
"Nashorn has been in development since 2010"
"Alas, only 2-3 engineers available to work on Nashorn at any given time"
"It takes a village to implement a programming language"
"ECMAScript 6 requires a significant number of changes"
"Other JavaScripts get better and better; V8, Nitro, SpiderMonkey"
https://www.youtube.com/watch?v=-JLhwsbMvjQ
Then follow from there up to the end.
It's really quite nice and I think there will be exiting news in this front from Oracle lab soonish...
[1] http://www.oracle.com/technetwork/oracle-labs/program-langua...
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?
https://github.com/eclipsesource/J2V8
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)
mvn clean package
just after
git clone
This immediately tells me of his attention to make builds reproducible.
edit: formatting