Slashdot Mirror
Oracle Says It Is 'Committed' To Java EE 8 -- Amid Claims It Quietly Axed Future Development (theregister.co.uk)
Media reports, citing anonymous Oracle engineers, noted earlier this week that development of Java EE (Enterprise Edition) projects at Oracle had been "practically ceased" since last fall. This led many to wonder about the future of Java. Well, it's all cosy, says Oracle. The software firm assures that it is "committed" to Java. The Register reports: The Redwood City titan said it will present fresh plans for the future of Java EE 8 at its JavaOne conference in San Francisco in September. Version eight is due to be released in the first half of 2017. However, over the past six months, it appeared Oracle had pretty much ceased development of the enterprise edition -- a crucial component in hundreds of thousands of business applications -- and instead quietly focused its engineers on other products and projects. Oracle spokesman Mike Moeller tonight sought to allay those fears, and said a plan for the future of Java EE is brewing. "Oracle is committed to Java and has a very well defined proposal for the next version of the Java EE specification -- Java EE 8 -- that will support developers as they seek to build new applications that are designed using micro-services on large-scale distributed computing and container-based environments on the Cloud," said Moeller.
They are LIARS!!!
.
Then there is Java EE, which is not a language, but a framework.
Then there is Javascript, which is a language, but is not releated to Java.
>> Well, it's all cosy, says Oracle.
Frankly, that reads like an Oracle license agreement. WTF is "cosy"?
Oracle, where tech goes to die.
It's big business that's in the business simply because they're big and locked into a lot of big clients that can't conceive of doing without them. Why would they innovate? That's hardly part of their business model. Let me put that another way: Their sales team is more important than their engineers. But at least they're not SAP.
It was a death knell for Java when Oracle bought Sun.
The article refers to Java EE, not Java specifically. EE is a whole other kettle of finish on top of Java, and it's used primarily by large companies who have the resources and manpower to figure out how to use EE in the first place.
Oracle wants sole control of Java EE, because there would be a great deal of money to be made. At least there would be in the short and medium term, for as long as Oracle has these companies by the balls, in the same way they do with their database and other software.
Unfortunately, they can't just "take control" of Java EE, cause it's a community-based system, so they were hoping to just quietly abandon it and roll a completely different - and proprietary - stack instead. Apparently it occurred to someone at the last minute that this would be a monumentally idiotic decision, and doing so would destroy Java in the same way Oracle has already completely fucked up MySQL, OpenOffice, Hudson, etc.
The submission said they want to move Java to the Cloud, but I already received a patent on doing Java-ey things on the Cloud. They need my permission first, and pay a hefty licensing fee if they want to put Java on the Cloud.
If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
I was hoping that java would quietly die not that java itself is bad but there is so much java junk developed by companies that is just good enough to ship on a schedule we'll finish fixing it later and then later never comes... I guess it's job security since there is no short supply of crap.
I was hoping that <some language> would quietly die not that <some language> itself is bad but there is so much <some language> junk developed by companies that is just good enough to ship on a schedule we'll finish fixing it later and then later never comes... I guess it's job security since there is no short supply of crap.
FTFY
The cesspool just got a check and balance.
OOM, GC limit exceeded.
What's the Oldest Technology You've Used In a Production Environment?
I'm sure java is not the only one and would quickly be replaced by something else but at the moment the problem children tend to favor java.
When I went back to school to learn computer programming after the dot com bust, the CIS department couldn't afford a Microsoft site license for Visual Studio C++ and taught all flavors of Java. My opinion then, and still is today, it was a some language that I didn't want to learn. In fact, I went into IT support after getting my diploma and never used Java since then.
There's lots of junk developed on lots of platforms; Java, PHP, .NET, C/C++, Visual Basic 6 and all the VB for Apps legacy cruft automating everything from Microsoft Access forms to Word documents.
Why exactly would you pick on Java?
The world's burning. Moped Jesus spotted on I50. Details at 11.
So you're saying then, that even a short run-in with Java ruined your career?
Made your wife leave?
Overfed your dog and made him fat?
Java: Not Even Once(tm)
4. To place officially in confinement or custody, as in a mental health facility.
http://www.thefreedictionary.com/committed
The only thing oracle is committed to is making and taking money. To say they are committed is to say, "as long as we keep getting enough money from it, we'll keep doing it!" It's MBA Stupidity 101, only money matters.
Anons need not reply. Questions end with a question mark.
it's true all of those things but java is the one I see the most so it annoys me the most and i'm sure if it dies one of those others would replace it in the not so distant future.
So you're saying then, that even a short run-in with Java ruined your career?
Not at all. When I went back to school to learn computer programming, I was working as a black box tester (no programming). I wanted to become a white box tester (programming). But I got an IT support job and never looked back, making that my career instead. Knowing how to program helps immensely in solving many of the IT problems at work. I'm a firm believer in taking opportunities that present themselves rather than sticking to something where the opportunities don't present themselves. I have no regrets in not being a professional programmer.
My experience with Java EE has been that it's too complicated to be worth it. Plus the recent push for microservices has displaced Java EE's biggest advantage of being scalable.
Spring has long since been the goto because it's much easier as a development platform and performs well. As an enterprise developer my biggest hurtle is that I have to get x done as quickly as possible and sometimes (almost always) I have to choose the less then elegant solution.
Sometimes we get a bad rep for writing crappy code. It's may be because we're just bad at our job and spend too much time reading slashdot. It may also be because we have constraints and have to take on a "it's good enough" attitude.
I digress: I think Java EE as a platform is losing it's place anyway in favor of simpler or more diverse solutions.
as someone who used J2EE once upon a time, i hoped that mess would die in a fire - most of it was developed by ibm and is a pile of overengineering to a mind-boggling level
This is where Arnold hangs up and tells the kid the Java developers are dead.
If I have been able to see further than others, it is because I bought a pair of binoculars.
A wedge to keep my desktop machine from rocking on my un-level desktop. Technically, it was a shim, which is only a slight innovation over a wedge. I wonder if the inventor of the wedge held a patent and sued the inventor of the shim.
Everyone has it wrong...they mean "committed" as in locked into a mental institution.
Does Oracle efforts in Java EE land even matter anymore? They are so far behind the curve that they are going to be lapped a few times before they get their act in gear. Clearly they need to simply release Java back into OpenSource land for it to remain relevant.
And as such, this whole kerfluffle baffles me. Java EE is not the Java or the JVM that so many people rely on. Nothing to do with Scala or Closure or Kotlin or the other interesting JVM technologies that are very much alive. Rather, it's is a clumsy and archaic framework technology that no reasonable person could possibly love. Move along. Nothing to see here.
From their point of view: "We've had this great innovation on how we can improve web-servers and Java productivity. Now shall we put it into WebLogic, where it will give us a competitive advantage and charge for it, or put it into J2EE where it will benefit everyone?".
a language has no name?