Re:Removal of Unsafe in Java 9 – A disaster in the making
by syjer on Monday July 13, 2015 @11:55AM
(#9878904)
1. it's quite likely that the Unsafe classes will be accessible with a flag, so for this kind of projects it's not really a big problem, as they provide the shell scripts for launching the jvm with all the necessary parameters.
[ Parent
| on HN ]
[deleted]
Re:Removal of Unsafe in Java 9 – A disaster in the making
by jlarocco on Monday July 13, 2015 @12:26PM
(#9879119)
> The problem is for more then a decade companies were told this problem would never exist.
That's exactly opposite of the truth.
The Sun and Oracle documentation has always said (back to at least the Java 1.1 days) that internal APIs could change or disappear at any time, and explicitly said not to use classes in sun.* unless you wanted to fix your code with every new JDK release.
Re:Removal of Unsafe in Java 9 – A disaster in the making
by kasey_junk on Monday July 13, 2015 @12:20PM
(#9879074)
If you are using Unsafe in your code you have already decided that you know what jvm you are deploying to.
Re:Removal of Unsafe in Java 9 – A disaster in the making
by gizmo385 on Monday July 13, 2015 @04:48PM
(#9880957)
That's not necessarily true. What about for projects which are used across a wide array of platforms such as Spring or Gson? Those frameworks are meant to be deployed independently of platform.