Re:Why is this Go faster than the equivalent Java?
by matwood on Saturday April 01, 2017 @09:59AM
(#14012141)
Even without special compilers, most people are using java on the server. Startup time happens once on deploy.
Re:Why is this Go faster than the equivalent Java?
by akvadrako on Tuesday April 11, 2017 @12:03PM
(#14089364)
...and much more frequently during development.
Re:Why is this Go faster than the equivalent Java?
by rusk on Saturday April 01, 2017 @03:17PM
(#14013642)
True but these approaches have never been marketed as part of the java experience
Re:Why is this Go faster than the equivalent Java?
by pjmlp on Saturday April 01, 2017 @04:27PM
(#14014001)
Only by those that aren't doing Java programming.
I use Java since the very early days, and am well aware of them, as are my fellow Java developers, when I work in Java projects.
Re:Why is this Go faster than the equivalent Java?
by rusk on Monday April 03, 2017 @08:22AM
(#14022222)
Aren't you great. As a java developer I am well aware of them too. For most people java == java applets; or "hello world" with `javac Hello.java` and then `java -cp. Hello` followed by some interminable wait while all the apparatus of the JVM is marshalled for the sole purpose of emitting a static string and then exiting. And by interminable I mean 2 or 3 second but still.
Even in more enlightened scenarios a REPL on jruby is just eye-wateringly painful unless you've all the "secret speedups" enabled.
In many more modern development cultures such secrets are generally looked upon as "Yak Shaving".
Also another example is those that perceive the JVM as slow due to using it with Clojure, when the slowness in this case is caused by the Clojure implementation itself.