News for hackers. Stuff that matters.
Re:Removal of Unsafe in Java 9 – A disaster in the making by taeric on Monday July 13, 2015 @11:24AM (#9878680)
That is a pretty crappy explanation, on the engineer's side.

To be clear, any explanation that is not immediately followed with examples to how current valid uses of Unsafe can be accomplished without it, are simply witch hunts by an engineer that hasn't had to meet the same requirements.

Re:Removal of Unsafe in Java 9 – A disaster in the making by danudey on Monday July 13, 2015 @12:49PM (#9879273)
It's a) unsafe, and b) an internal, undocumented API.

When you start importing from sun.misc.* you've made the conscious (or ignorant) decision to write non-portable code which may well break due to any JVM release. It sucks that these people are going to have to update their code (or that end users won't be able to upgrade to Java 9 without adding special command-line flags), but it's not due to fickle Oracle developers, it's due to technical debt that's finally catching up to them.

Re:Removal of Unsafe in Java 9 – A disaster in the making by kasey_junk on Monday July 13, 2015 @01:11PM (#9879434)
You quite simply have NO option to do on the JVM most of the things people are using unsafe for in Java 9/10 without a migration plan from Oracle.

What Oracle is close to "hey all you performance sensitive folks, we aren't going to support unsafe anymore, can you tell us what you are using it for and how we can migrate to that explicitly?"

It just so happens that one of the leading proposals is "leave in java 9 but make it explicit to turn on". This is probably the right way to do this (in my opinion) but it does have the downside of making neither camp happy (it leaves unsafe so the purists are mad, and it causes headaches for people using unsafe).

Re:Removal of Unsafe in Java 9 – A disaster in the making by MrBuddyCasino on Monday July 13, 2015 @06:23PM (#9881562)
Whats wrong with:

- deprecate in Java 9

- "make it explicit to turn on" in 10, offer alternative official APIs as fallback

- remove entirely when most people have switched

Re:Removal of Unsafe in Java 9 – A disaster in the making by kasey_junk on Tuesday July 14, 2015 @03:12PM (#9887314)
Nothing at all. That's what I assume will happen at the end of the day. But people saying that we can just turn it off in 9 because you shouldn't be using internal api's don't seem to get that there is no external solution.
Re:Removal of Unsafe in Java 9 – A disaster in the making by justthistime_ on Monday July 13, 2015 @01:11PM (#9879435)
Why should third-party libraries pay for Oracle's technical debt?
Re:Removal of Unsafe in Java 9 – A disaster in the making by wtetzner on Monday July 13, 2015 @02:03PM (#9879824)
It's not Oracle's technical debt, it's the developers of the third-party libraries that are importing from sun.misc.*.