Re:JEP 295: Ahead-of-Time Compilation
by paulddraper on Thursday October 27, 2016 @09:17PM
(#12812128)
Well, it was a runtime option that was requested, and runtime options don't have to be identical on every platform.
Re:JEP 295: Ahead-of-Time Compilation
by valarauca1 on Friday October 28, 2016 @05:01AM
(#12814173)
Actually they do. That is the entire point of Java.
Re:JEP 295: Ahead-of-Time Compilation
by paulddraper on Friday October 28, 2016 @11:10AM
(#12816645)
No, the point was to make compile-once run-anywhere software. It's natural for tuning runtime parameters to vary.
The hotspot JVM will accept both -d32 (32-bit data model) and -d64 (64-bit data model) everywhere, but they will only work on certain platforms.
While nearly every other Green Threaded language offered as an additional library/option. This hurt adoption. While Go just forces you to use Green Threading.
Not in the slightest. A laundry list of reason:1. Change what functions do and don't block can cause huge issues with down stream libraries/people who depend on system libraries behaving the same thing tomorrow as they did yesterday.
2. Refactoring all code around system calls so they never block.
3. Write a multi-core and multi-socket scheduler.
4. Write a scheduler to balance multi-core and multi-socket thread load.
5. Determine how you will do polling, and write a polling strategy to figure out what green threads are/are not blocked, then figure out how to communicate this information efficiently.
6. Repeat the above 5 steps for EVERY platform Java runs on.