openJDK-docker VS JDK

Install OpenJDK and Java Runtime Environment (JRE) 11

Reloading is nothing new under the sun for Lisp, I believe. For ML and adequate reload-ability, one might be hard pressed, but it's nothing new under the Sun (hint, hint). Maybe too on the nose, but one probably wants good inlining, and thus more "speculative" de/optimisation to preserve redefinition.

If they don't want Oracle's Java, why can't they use a subset of OpenJDK (licensing noob here)?

I think they use a circular queue of functions that is each executed for around 100 ms. I am guessing the system timer is used to generate an interrupt that pauses execution of the current function and starts executing the next function. Apple's Java code is probably closed source. I did find mention of an openjdk here: https://openjdk.java.net. I haven't looked at the source code yet.

https://openjdk.java.net

$ yum info java-1.8.0-openjdk Available Packages Name : java-1.8.0-openjdk Arch : x86_64 Epoch : 1 Version : 1.8.0.322.b06 Release : 1.el7_9 Size : 314 k Repo : updates/7/x86_64 Summary : OpenJDK 8 Runtime Environment URL : http://openjdk.java.net/ License : ASL 1.1 and ASL 2.0 and BSD and BSD with advertising and GPL+ and GPLv2 and GPLv2 with : exceptions and IJG and LGPLv2+ and MIT and MPLv2.0 and Public Domain and W3C and zlib Description : The OpenJDK 8 runtime environment.

For the rest: -+ PIP3 & Python scripts: export REQUESTS_CA_BUNDLE=/path/to/your/certificate.pem python script.py -+ JAVA =java -D'javax.net.ssl.trustStore'="/opt/site/cacerts.JKS" .....= https://serverfault.com/questions/636612/preserve-imported-ca-certificates-through-java-upgrades/636882 https://github.com/docker-library/openjdk/issues/327 -+ Windows server https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/valid-root-ca-certificates-untrusted certutil .. root fg.cer

I felt out of the loop, thinking that Zero VM was some kind of new distro for OpenJDK but chasing <https://packages.debian.org/sid/openjdk-22-jre-zero#:~:text=...> to <https://sources.debian.org/src/openjdk-11/11.0.23%2B9-1/debi...> lead me to https://github.com/openjdk/jdk/tree/jdk-22-ga/src/hotspot/cp...

It seems that it's a specific CPU target for the Hotspot JIT for non-mainstream architectures (or for research purposes, as I saw mentioned once)

Completely gutted from the OpenJDK, last I checked. See here for the culprit PR: https://github.com/openjdk/jdk/pull/18688

> Yes, they're changing one aspect of signal handler use to work around this problem. They're not stopping the use of signal handlers in general. Hotspot continues to use signals for efficiency in general. See https://github.com/openjdk/jdk/blob/9059727df135dc90311bd476...

This whole thread is about SIGSEGV, and specifically their SIGSEGV handling. However, catching normal signals is not about efficiency.

Some of their exception handling is still odd: There is no reason for a program that receives SIGILL to ever attempt continuing. But others is fine, like catching SIGFPE to just forward an exception to the calling code.

(Sure, you could construct an argument to say that this is for efficiency if you considered the alternative to be implementing floating point in software so that all exceptions exist in user-space, but hardware floating point is the norm and such alternative would be wholly unreasonable.)

> The wonderful thing about choosing not to care about facts is having whatever opinions you want.

I appreciate the irony of you making such statement, proudly thinking that your opinion equals fact, and therefore any other opinion is not.

This discussion is nothing but subjective opinion vs. subjective opinion. Facts are (hopefully, as I can only speak for myself) inputs to both our opinions, but no opinion about "good" or "bad", "nasty" or not can ever be objective. Objective code quality does not exist.

I remember talking to Brendan about the PreserveFramePointer patch during my first months at Netflix in 2015. As of JDK 21, unfortunately it is no longer a general purpose solution for the JVM, because it prevents a fast path being taken for stack thawing for virtual threads: https://github.com/openjdk/jdk/blob/d32ce65781c1d7815a69ceac...

Map doesn't implement the Collection interface.

https://github.com/openjdk/jdk/blob/master/src/java.base/sha...