←back to thread

56 points mghackerlady | 2 comments | | HN request time: 0s | source
Show context
larsbrinkhoff ◴[] No.45989967[source]
What happened to

1. Sun's JavaStation, 2. ARM's Jazelle, ??? 3. Profit!

replies(4): >>45990000 #>>45990288 #>>45990667 #>>45993727 #
dehrmann ◴[] No.45990000[source]
It's more like JITs got good.
replies(1): >>45990334 #
ck45 ◴[] No.45990334[source]
I never understood why AOT never took off for Java. The write once run anywhere quickly faded as an argument, the number of platforms that a software package needs to support is rather small.
replies(5): >>45990420 #>>45990438 #>>45990583 #>>45990837 #>>45994530 #
pjmlp ◴[] No.45990438{3}[source]
Because developers don't like to pay for tools.

https://en.wikipedia.org/wiki/Excelsior_JET

https://www.ptc.com/en/products/developer-tools/perc

https://www.aicas.com/products-services/jamaicavm/

It is now getting adopted because GraalVM and OpenJ9 are available for free.

Also while not being proper Java, Android does AOT since version 5, mixed JIT/AOT since version 7.

EDIT: Fixed the sentence regarding Android versions.

replies(3): >>45990522 #>>45991201 #>>45992006 #
1. rjsw ◴[] No.45992006{4}[source]
You could do AOT Java using gcj, it didn't need commercial tools.
replies(1): >>45992907 #
2. pjmlp ◴[] No.45992907[source]
If we ignore gcj was never production ready, and basically the only good case that Red-Hat sponsored was to compile Eclipse, which was usually slower than using the JIT anyway.

And that around 2009, most of the team left the project, some went to OpenJDK, others elsewhere, while GCC kept it around because gcj unit tests stressed parts of the GCC that weren't tested by other frontends, until the decision came to remove it completly.

As side note, I expect a similar outcome to gccgo, abandoned since Go added generics support.