Java's New G1 Collector Not For-Pay After All 171
An anonymous reader writes "As a follow-up to our previous discussion, Sun appears to have quietly edited the Java 6u14 release notes language to say now: 'G1 is available as early access in this release, please try it and give us feedback. Usage in production settings without a Java SE for Business support contract is not recommended.' So does this mean it was all one huge typo? Or was Oracle/Sun tentatively testing the waters to see the community's reaction? In either case it's nice to see Java's back on the right path."
Right path? (Score:5, Funny)
Did kdawson even read the article before writing the summary? I don't see anything in the article about Java becoming more like Haskell!
No Way! (Score:5, Funny)
A kdawson article that totally blew something out of proportion? What a shock!
Re:But it could be! (Score:5, Funny)
Where Java really fails is in the inability to trust the finalize method. At least in C++, the destructor of an object is guaranteed to be called as soon as the object is deleted.
Destructor!? Finalize!? Deleted!? You talking like a crazy man, have you never heard of a system REBOOT?
Re:But it could be! (Score:1, Funny)
windows user?
Re:Well.... (Score:0, Funny)
Re:Not quietly (Score:5, Funny)
What you said here. People were so buy foaming at the mouth that they never bothered to read the actual article or the thousands of posts that spelled out pretty clearly how and why the slashdot story got it wrong.
Never seen that before. No, not ever.
.. SHUT THE FUCK UP!" - Bill Hicks
It's funny when you can cut+paste your comment and drop it into multiple discussions without having to modify it. It is truly one-size-fits-all.
"Stop. Look. Listen, learn, read, think