Are Java's days numbered thanks to Oracle?
-
Oracle: Java's worst enemy[^] The quotes that really got me where:
Finding a severe bug in Java SE 7 normally would be forgivable, but Oracle's behavior in the matter has been downright disgraceful. Now we learn that Oracle knew about the Java SE 7 bug fully five days before it shipped the product. And yet it shipped anyway because five days wasn't enough time to fix the problem. I'm slapping my forehead here. Seriously? The Java community has been waiting five years for Java SE 7, but Oracle was so desperate to "move Java forward" that it couldn't wait any longer, even when it knew it was going to ship a product that contained a major flaw? Oracle reportedly says it will fix the problem in its next service release -- whenever that might be.
So, Java SE 7 is basically broken out the door, and Oracle doesn't seem too concerned. Is Oracle the beginning of the end for the Java language?
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
Would be nice, but probably not.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels) -
Oracle: Java's worst enemy[^] The quotes that really got me where:
Finding a severe bug in Java SE 7 normally would be forgivable, but Oracle's behavior in the matter has been downright disgraceful. Now we learn that Oracle knew about the Java SE 7 bug fully five days before it shipped the product. And yet it shipped anyway because five days wasn't enough time to fix the problem. I'm slapping my forehead here. Seriously? The Java community has been waiting five years for Java SE 7, but Oracle was so desperate to "move Java forward" that it couldn't wait any longer, even when it knew it was going to ship a product that contained a major flaw? Oracle reportedly says it will fix the problem in its next service release -- whenever that might be.
So, Java SE 7 is basically broken out the door, and Oracle doesn't seem too concerned. Is Oracle the beginning of the end for the Java language?
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
Alexander DiMauro wrote:
Java SE 7
I guess that means Java Sucks Edition 7... "That's a joke, I say, that's a joke, son!" Foghorn Leghorn
It was broke, so I fixed it.
-
Dalek Dave wrote:
no
So, basically, you are saying...no? :)
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
-
Oracle: Java's worst enemy[^] The quotes that really got me where:
Finding a severe bug in Java SE 7 normally would be forgivable, but Oracle's behavior in the matter has been downright disgraceful. Now we learn that Oracle knew about the Java SE 7 bug fully five days before it shipped the product. And yet it shipped anyway because five days wasn't enough time to fix the problem. I'm slapping my forehead here. Seriously? The Java community has been waiting five years for Java SE 7, but Oracle was so desperate to "move Java forward" that it couldn't wait any longer, even when it knew it was going to ship a product that contained a major flaw? Oracle reportedly says it will fix the problem in its next service release -- whenever that might be.
So, Java SE 7 is basically broken out the door, and Oracle doesn't seem too concerned. Is Oracle the beginning of the end for the Java language?
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
Alexander DiMauro wrote:
Java SE 7 is basically broken out the door
It isn't a critical bug. There is a compiler optimisation option that, in certain circumstances, transposes steps in the byte code. There is a simple workaround - don't use the option - and a possibility to mitigate it's effect through code. This story was reported last month and was a non-story then and hasn't got much more since.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
Alexander DiMauro wrote:
Java SE 7
I guess that means Java Sucks Edition 7... "That's a joke, I say, that's a joke, son!" Foghorn Leghorn
It was broke, so I fixed it.
Foghorn would never joke. It's a serious business being the biggest cock in town.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
Would be nice, but probably not.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)Yeah, doing a job search shows that Java still dominates, so I also doubt it will go away any time soon. But enough of this type of behavior, and there has to be some sort of backlash against Oracle...I mean, more than they have already received thanks to buying Java just to sue the pants off of Google, that is.
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
-
Oracle: Java's worst enemy[^] The quotes that really got me where:
Finding a severe bug in Java SE 7 normally would be forgivable, but Oracle's behavior in the matter has been downright disgraceful. Now we learn that Oracle knew about the Java SE 7 bug fully five days before it shipped the product. And yet it shipped anyway because five days wasn't enough time to fix the problem. I'm slapping my forehead here. Seriously? The Java community has been waiting five years for Java SE 7, but Oracle was so desperate to "move Java forward" that it couldn't wait any longer, even when it knew it was going to ship a product that contained a major flaw? Oracle reportedly says it will fix the problem in its next service release -- whenever that might be.
So, Java SE 7 is basically broken out the door, and Oracle doesn't seem too concerned. Is Oracle the beginning of the end for the Java language?
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
Pretty cool bug, though. It's an optimization bug that's been around since version 6 and Oracle changed the default in version 7 to be on instead of off. Bet you a weeks pay, I know what the Oracle fix will be. :cool: Java's days are not numbered. Oracle is engaged in taking something that could loosely be considered quite open and trying to make it entirely closed, so that they can mint it for all it's worth. Just business as usual. :)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
-
Alexander DiMauro wrote:
Java SE 7 is basically broken out the door
It isn't a critical bug. There is a compiler optimisation option that, in certain circumstances, transposes steps in the byte code. There is a simple workaround - don't use the option - and a possibility to mitigate it's effect through code. This story was reported last month and was a non-story then and hasn't got much more since.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
It being default on in v7, when 99% of developers don't know that compiler options even exist and even fewer would think to look there when a bug showed up makes it a major problem even if it has a trivial work around.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius
-
Pretty cool bug, though. It's an optimization bug that's been around since version 6 and Oracle changed the default in version 7 to be on instead of off. Bet you a weeks pay, I know what the Oracle fix will be. :cool: Java's days are not numbered. Oracle is engaged in taking something that could loosely be considered quite open and trying to make it entirely closed, so that they can mint it for all it's worth. Just business as usual. :)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
Chris Meech wrote:
Bet you a weeks pay, I know what the Oracle fix will be.
"Have you tried turning it off and on again?" :-D
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
-
Oracle: Java's worst enemy[^] The quotes that really got me where:
Finding a severe bug in Java SE 7 normally would be forgivable, but Oracle's behavior in the matter has been downright disgraceful. Now we learn that Oracle knew about the Java SE 7 bug fully five days before it shipped the product. And yet it shipped anyway because five days wasn't enough time to fix the problem. I'm slapping my forehead here. Seriously? The Java community has been waiting five years for Java SE 7, but Oracle was so desperate to "move Java forward" that it couldn't wait any longer, even when it knew it was going to ship a product that contained a major flaw? Oracle reportedly says it will fix the problem in its next service release -- whenever that might be.
So, Java SE 7 is basically broken out the door, and Oracle doesn't seem too concerned. Is Oracle the beginning of the end for the Java language?
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
Alexander DiMauro wrote:
So, Java SE 7 is basically broken out the door, and Oracle doesn't seem too concerned
Were you expecting Oracle to act differently than any other major software shop? They all do this. It's basically industry standard. If they waited to fix everything they would never ship. Hell we still wouldn't have Windows XP if MS was waiting for the bugs to be fixed before it shipped.
-
TLDR
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
Alexander DiMauro wrote:
So, Java SE 7 is basically broken out the door, and Oracle doesn't seem too concerned
Were you expecting Oracle to act differently than any other major software shop? They all do this. It's basically industry standard. If they waited to fix everything they would never ship. Hell we still wouldn't have Windows XP if MS was waiting for the bugs to be fixed before it shipped.
thrakazog wrote:
Hell we still wouldn't have Windows XP if MS was waiting for the bugs to be fixed before it shipped.
Yeah, you're right. I guess the author of the article may have been revealing his own personal biases against Oracle? (gasp! horror! that never happens!) :omg: As for me, I've been trying to expand my skill set, and I just wanted to make sure taking up Java wasn't joining a sinking ship. I'm still torn between Java and Ruby. Dabbled in both, but want to take one up more seriously.
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
-
Alexander DiMauro wrote:
Java SE 7 is basically broken out the door
It isn't a critical bug. There is a compiler optimisation option that, in certain circumstances, transposes steps in the byte code. There is a simple workaround - don't use the option - and a possibility to mitigate it's effect through code. This story was reported last month and was a non-story then and hasn't got much more since.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
It was a trivial bug in Java 6, when that JIT option was off by default. Not so in 7, where it's on by default.
-
Oracle: Java's worst enemy[^] The quotes that really got me where:
Finding a severe bug in Java SE 7 normally would be forgivable, but Oracle's behavior in the matter has been downright disgraceful. Now we learn that Oracle knew about the Java SE 7 bug fully five days before it shipped the product. And yet it shipped anyway because five days wasn't enough time to fix the problem. I'm slapping my forehead here. Seriously? The Java community has been waiting five years for Java SE 7, but Oracle was so desperate to "move Java forward" that it couldn't wait any longer, even when it knew it was going to ship a product that contained a major flaw? Oracle reportedly says it will fix the problem in its next service release -- whenever that might be.
So, Java SE 7 is basically broken out the door, and Oracle doesn't seem too concerned. Is Oracle the beginning of the end for the Java language?
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
I sincerely doubt it, if they go to far it will go the way of open office and simply become librejava or some such. Java is used in mission critical applications, it is in my opinion going to become as ubiquitous as C++. All software has bugs, I work writing automation code in java with APIs and in JVMs that are so full of bugs it is not even funny. Oracle will get it sorted sooner or later, I doubt they would let the reason they bought sun languish for to long. It does not make strategic sense.
-
Oracle: Java's worst enemy[^] The quotes that really got me where:
Finding a severe bug in Java SE 7 normally would be forgivable, but Oracle's behavior in the matter has been downright disgraceful. Now we learn that Oracle knew about the Java SE 7 bug fully five days before it shipped the product. And yet it shipped anyway because five days wasn't enough time to fix the problem. I'm slapping my forehead here. Seriously? The Java community has been waiting five years for Java SE 7, but Oracle was so desperate to "move Java forward" that it couldn't wait any longer, even when it knew it was going to ship a product that contained a major flaw? Oracle reportedly says it will fix the problem in its next service release -- whenever that might be.
So, Java SE 7 is basically broken out the door, and Oracle doesn't seem too concerned. Is Oracle the beginning of the end for the Java language?
The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?
No, Oracle depends on Java too heavy to just kill it. All Oracle installers, IDEs, utilities are on Java. Even most important if you like to write your own UDF functions for Oracle (which is very useful since Oracle can handle such functions. It’s not wise using them in SQL Server though) you have to use Java or C++. Most of the examples and help are for Java language and this together with the fact that a very few developers have a good grasp of a low level C++ makes it the logical language of choice when you develop Oracle applications.
There is only one Ashley Judd and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.