News for hackers. Stuff that matters.
Re:What Future Java Might Look Like by cbdfghh on Wednesday December 07, 2016 @12:37PM (#13124364)
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.

Re:What Future Java Might Look Like by twic on Wednesday December 07, 2016 @02:43PM (#13125538)
Re:What Future Java Might Look Like by fauigerzigerk on Wednesday December 07, 2016 @01:17PM (#13124745)
IntelliJ 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.

Re:What Future Java Might Look Like by pjmlp on Wednesday December 07, 2016 @04:04PM (#13126206)
> 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.

Re:What Future Java Might Look Like by user5994461 on Wednesday December 07, 2016 @02:06PM (#13125201)
Other languages don't do much better once you start to have a few dependencies.