News for hackers. Stuff that matters.
Re:JDK 8 Release Notes by fosk on Tuesday March 18, 2014 @04:44PM (#7424852)
Methods are marked as deprecated when they're planned to be removed in the next version.
Re:JDK 8 Release Notes by pohl on Tuesday March 18, 2014 @05:14PM (#7425031)
That's the story that gets told, but how often have they actually removed something after deprecating it? Does anybody have a single concrete example of a method that actually went away?

http://stackoverflow.com/questions/18063599/has-ever-anythin...

Re:JDK 8 Release Notes by meddlepal on Tuesday March 18, 2014 @06:42PM (#7425570)
I don't believe they have ever removed a Class or method from the JDK... Thread still has all of those super-unsafe or non-implemented methods in it (see: stop(), destroy() etc.)

I think part of the reason for this ultra-conservative approach might be that alternate JVM implementations could in theory have well-implemented versions of deprecated methods such as the above-mentioned Thread ones.

Re:JDK 8 Release Notes by coldtea on Wednesday March 19, 2014 @06:36AM (#7427717)
No, they (Sun) could not care less for alternate JVM implementations. The reason for that ultra-conservative approach was that they were hell bent on keeping compatibility.
Re:JDK 8 Release Notes by djpowell on Wednesday March 19, 2014 @08:11AM (#7428059)
System.getenv was deprecated (in 1.1?), and then replaced with an implementation that threw UnsupportedOperationException (in 1.2?) because it was considered to be non-portable.

Later they saw sense and re-implemented it and un-deprecated it.