News for hackers. Stuff that matters.
Re:Removal of Unsafe in Java 9 – A disaster in the making by geofft on Monday July 13, 2015 @01:28PM (#9879562)
That link is a very useful contribution to this discussion (and possibly the first really useful comment in this thread), thanks. Everyone's entitled to their opinion, informed or not, but if you want an informed opinion, the question needs to be what the current uses of Unsafe are, why they're used, and whether there are plans for a migration path.

It sort of seems like the major use case (judging from those numbers) is reading and writing raw byte buffers, possibly mapped from other objects/files, with native performance. Is there a potential sensible design for a bounds-checked raw data API ("unsafe but only within these pages") that maintains the JVM's usual safety guarantees for all other data, and can be implemented in a performant way?

Re:Removal of Unsafe in Java 9 – A disaster in the making by pdeva1 on Monday July 13, 2015 @02:04PM (#9879827)
The document is also linked in the blog post, on the very first line...
Re:Removal of Unsafe in Java 9 – A disaster in the making by scott_s on Monday July 13, 2015 @02:26PM (#9879964)
It was not obvious to me that the other side of that link would be a living document on current uses of Unsafe.