News for hackers. Stuff that matters.

A comment on JEP Draft: Deprecate memory-access methods in sun.misc.unsafe for removal. Parent comment

Re:JEP Draft: Deprecate memory-access methods in sun.misc.un... by kaba0 on Wednesday January 17, 2024 @01:42AM (#39024076)
It won’t change for many many years to come. It becomes deprecated, which just gives you a warning.
[ Parent | on HN ]
Re:JEP Draft: Deprecate memory-access methods in sun.misc.un... by pjmlp on Wednesday January 17, 2024 @02:12AM (#39024306)
Since Java 9, deprecations are actually removed, after a couple of LTS releases.
[ Parent | on HN ]
Re:JEP Draft: Deprecate memory-access methods in sun.misc.un... by kaba0 on Wednesday January 17, 2024 @04:03AM (#39025207)
A couple of LTS releases is 2*n years, though.
[ Parent | on HN ]
Re:JEP Draft: Deprecate memory-access methods in sun.misc.un... by pjmlp on Wednesday January 17, 2024 @04:14AM (#39025307)
The planned releases for removal are listed on the JEP.

If they fail to provide parity, people will do like with modules, keeping holding to older Java versions longer than they should, use the escape command line options if available, turn back to JNI (the opposite this is trying to achieve), or move to other stack if they aren't that dependent on Java, e.g. ongoing Kafka ecosystem evolution.

[ Parent | on HN ]