JDK 10 Early Access Release Notes

Looks like a lot of housekeeping is taking place.<p>I just wish they implemented a native and full code hot-reload support on the jvm, instead of relying on external tools&#x2F;hacks that work sometimes.<p>That alone would single-handedly improve productivity by an order of magnitude.

If anyone other than me was concerned that the &quot;system property to disable JRE last usage tracking&quot; was something like the enabled-by-default telemetry of .NET Core[1] (which made me give up on it in disgust), it&#x27;s apparently[2] not – it&#x27;s just some (commercial add-on) logging feature.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;dotnet&#x2F;cli&#x2F;issues&#x2F;3093" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;dotnet&#x2F;cli&#x2F;issues&#x2F;3093</a><p>[2] <a href="https:&#x2F;&#x2F;docs.oracle.com&#x2F;javacomponents&#x2F;usage-tracker&#x2F;overview&#x2F;" rel="nofollow">https:&#x2F;&#x2F;docs.oracle.com&#x2F;javacomponents&#x2F;usage-tracker&#x2F;overvie...</a>

Beyond housekeeping could only find one real big changes that is parallel full GC for G1. That&#x27;s a big one in controlling the worst case.

As you can tell from the relnotes, there are a lot of removals. Fortunately, they&#x27;re all following a pretty reasonable deprecation procedure, but I still can&#x27;t shake what happened with Jigsaw and JDK9. Software broke. That didn&#x27;t happen (regularly) before unless that software was doing patently silly things. This was different: _most_ software broke. Here&#x27;s hoping that doesn&#x27;t turn into a pattern.

&gt; The clear passwords present in jmxremote.password file will now be over-written by their SHA3-512 hash by the JMX agent<p>I must be misreading this. As far as I can tell the ability to read the new format was added in the same version. Did someone forget about forwards compatibility <i>in the jvm</i>?

Sexy as always