News for hackers. Stuff that matters.
Re:Removal of Unsafe in Java 9 – A disaster in the making by jart on Monday July 13, 2015 @11:37AM (#9878788)
I just read an article that says in order to even use Unsafe, you have to use reflection to unwind the stack and go searching for a reference to the Unsafe instance, because the Java authors worked so hard to make it private. So it seems to me that they'd be well within their rights to remove the class.

Normally when you go to that level of epic hackery, you can't expect for official support or backwards compatibility. So the author of this article using scare tactics to keep that feature seems rather disingenuous.

Re:Removal of Unsafe in Java 9 – A disaster in the making by orf on Monday July 13, 2015 @01:40PM (#9879646)
Could you provide a link to the article? I'm not saying you're wrong (I'm not a Java guy) but that sounds convoluted.
Re:Removal of Unsafe in Java 9 – A disaster in the making by twic on Monday July 13, 2015 @01:56PM (#9879777)
This is how you get access to Unsafe:

  Field theUnsafe = Unsafe.class.getDeclaredField("theUnsafe");
  theUnsafe.setAccessible(true);
  Unsafe unsafe = (Unsafe) theUnsafe.get(null);
Reflection, but no stack unwinding.