Re:Server-Side I/O Performance: Node vs. PHP vs. Java vs. Go
by issaria on Wednesday December 13, 2017 @01:41PM
(#15916345)
Java is compile to bytecode which is then interpreted by a virtual machine, it's not compiled to native code, that's why you cannot distribute Java programs as executable like go.
[ Parent
| on HN ]
Re:Server-Side I/O Performance: Node vs. PHP vs. Java vs. Go
by amorphid on Wednesday December 13, 2017 @04:16PM
(#15917740)
Is there a way to bundle the JVM (or the parts you need) with the Java app you'd like to run? Erlang (and Elixir) does this with the Erlang VM (BEAM), allowing you to bundle VM+app as a release. The Erlang release must be compiled for the platforms on which that release will be run. It's not quite as elegant as a Go binary, but it's still pretty handy.
Re:Server-Side I/O Performance: Node vs. PHP vs. Java vs. Go
by issaria on Monday December 18, 2017 @10:07AM
(#15952095)
Yes, there is a javapackager in java 7 and 8, but with jigsaw that comes with java9, it becomes easier: https://steveperkins.com/using-java-9-modularization-to-ship...
Re:Server-Side I/O Performance: Node vs. PHP vs. Java vs. Go
by pjmlp on Wednesday December 13, 2017 @04:11PM
(#15917693)
Sure you can, https://www.excelsiorjet.com/
Java has a specification and has lots of implementations.
The majority of commercial implementations of Java have native code compilers, and Oracle is in the process of improving the AOT compiler introduced in Java 9.