4 ms·
What I would personally like (and I'm kind of surprised all projects which tried to implement it died) is a Java -> static exe/elf compiler (sort of like Go) or
by cbdfghh 10y ago
What I would personally like (and I'm kind of surprised all projects which tried to implement it died) is a Java -> static exe/elf compiler (sort of like Go) or at least java -> exe/elf +libjava.so .
I hate that deploying Java requires that everything has to be configured _exactly_ right, and write once run anywhere turns into write once debug everywhere.
- fauigerzigerk 10y agoIntelliJ or maven can at least create a fat runnable jar that includes all dependencies. So once you have a JVM on the target machine that jar is all you need to deploy. But I agree with you that an entirely static compilation target that includes the JVM and excludes everything that isn't necessary would be very desirable.
- user5994461 10y agoOther languages don't do much better once you start to have a few dependencies.
- twic 10y agoThat's been around since 2014: https://docs.oracle.com/javase/8/docs/technotes/guides/deploy/self-contained-packaging.html https://docs.oracle.com/javase/8/docs/technotes/guides/deplo...
- pjmlp 10y ago> Java -> static exe/elf compiler (sort of like Go) The ones that died where the open source ones, most commercial JVMs do support AOT compilation since the early 2000's.