21–30 of 52 posts
How does this relate to Nashorn? With something like Avatar-JS [1] you can even run some NodeJS apps without modifications on the JVM. [1] https://avatar-js.java.net
It's built on top of Nashorn[1]. [1] https://github.com/purplejs/purplejs/search?utf8=%E2%9C%93&q...
I particularly don't find the problem it solves appealing. The power of Node comes specifically from its everything async programming model, Javascript is just a detail. So what's the point in taking away the good part, and keep the cumbersome one? If you just want to program a Synchronous server in the JVM,just stick to Java.
Why don't any of the examples use Java?... Even the examples on GitHub, none of it looks any different than a Node.js project.
Is it correct to say that this is like JRuby, but with JavaScript in place of Ruby?
Why do people think async code is complicated and keep trying to replace it? I think there are just people who will never understand or fully grok the beauty, power and simplicity of functional programming and will always seek to replace it. I feel sorry for them.
As usual, @munificentbob explains it best: http://journal.stuffwithstuff.com/2015/02/01/what-color-is-y...
That doesn't include the disconnect from the rest of the JS ecosystem which has centered around npm at this point (at least for the package repository itself, baring the yarn front end).
I'm just not sure I see the value... and in the end, not sure it will work out any better than the DLR attempts with .Net... It's interesting, just not sure I see the value. The Java runtime is about 60mb to download, then the extras for this... vs Node's runtime download under 14mb with a similar amount of library downloads for a given project. That doesn't include the disconnect from the rest of the JS ecosystem wh…