Slashdot Mirror
Oracle Seeking Community Feedback on Java 8 EE Plans
An anonymous reader writes with this quick bite from Info Q: "Oracle is seeking feedback from the Java community about what it should work on for the next version of Java EE, the popular and widely used enterprise framework. As well as standardizing APIs for PaaS and SaaS the vendor is looking at removing some legacy baggage including EJB 2.x remote and local client view (EJBObject, EJBLocalObject, EJBHome, and EJBLocalHome interfaces) and CORBA."
Oracle doesn't usually give a damn about what people want.
If so, they'd already know we don't want that stupid Ask.com toolbar and they should stop trying to sneak it in.
Lost at C:>. Found at C.
Everyone is thinking it but everyone knows Larry doesn't give anything away for free. Even his free software costs you money somewhere...
"A person is smart. People are dumb, panicky dangerous animals and you know it." - K
Ive found several benefits to removing Java 8 entirely.
1. budget performance: by reducing expenditures on support contracts and Oracle licensing fees my budget has stopped looking like a Syrian casualty report.
2. maintenance productivity: developers have stopped hurling themselves nude through my expensive plate glass windows as they wail 'exception access violation!' This frees up maintenance to address more urgent concerns.
3. Environmental impact: We've reduced out environmental footprint by shredding our tear-stained contracts, and mulching them with our ancient blood-soaked documentation to create a spreadable compost that just brings out the absolute best in the landscaping.
4. Wellness impact: Thanks to removing Java our datacenter now runs closer to the temperatures the CRACS were designed to endure. While common HR functions like the weekly jboss report run luau-themed weenie roast have unfortunately been ended, the number of sysops that survive provisioning has improved. Analysts are also no longer permitted to refer to the datacenter provisioning process as 'the trip to mordor'
Good people go to bed earlier.
Microsoft doesn't own C++, nor do they release the primary runtime for C++.
False equivalency.
Put fewer security holes in it. Maybe just one or two.
Don't make it full of security bugs.
Don't include crapware in the installer for the package and EVERY subsequent update.
Speaking of updates... Don't make it so fucking hard to customize the installation! Having to create transforms with Orca which break installations preventing future updates is a bunch of shit.
I guess what I'm trying to say is, don't try to be Adobe.
Oracle is a tech company that manages to be worse than Microsoft.
So is Slashdot not capable of having any kind of informative conversation about one of the most commercially popular and long-lived everyday programming languages, because "Oracle, LOL" and "Java applets suck"?
Popped in here hoping to see some insightful discussion about the future of Java, to help inform my possible decision as to whether or not to spend a lot of time and effort becoming a Java developer. So far, sadly disappointed. Nothing but Java and Oracle jokes as old as the hills.
Then again, this is Slashdot. I don't know why I was expecting any kind of mature conversation about Java.
There is value in the JPA abstraction layer. Most large enterprises have multiple databases of various generations and need software that can talk to all of them. In that sense JPA is a blessing.
OpenJDK?
Since JavaEE is a server application standard, cutting old stuff means that you can no longer run apps that still use said older features on a newer JavaEE server. So, expect everyone to continue using the crusty, old versions of JBoss (for example) or to have the server manufacturers outright ignore Oracle's changes to JavaEE 8.
GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
Java itself is open-source already- OpenJDK.
There are several JavaEE servers that are open source, Jboss and Glassfish are the biggest two. As far as I remember, Glassfish is the reference implementation. It's as open-source as it can be.
Or are you talking about Technology Compatibility Kits? Or Java trademark? Development model itself? Or what?
--Coder
I've been programming in Java since it first came out, and I never had any particular problems with it, other than the fact that it's rather verbose. I've been thinking there must be a way to accomplish the same thing without so much boilerplate code. Then I discovered Scala (which runs on the JVM and can easily integrate with existing Java libraries).
Mind you there are some things about Scala that are kinda weird, like so much optional syntax and type inferencing makes it sometimes hard to read. But I've been finding it a joy for new code I write, almost Java-like but much less verbose, plus you get the functional programming capabilities that Java lacks. Some of the library code that's out there is hard to understand because of the nature of the syntax, but after you study it a bit, it's not too bad.
Yeah, Java and MySQL has seen better times - both platforms have recieved similar criticisms with regards to patching security issues. I don't much care if the world stops using Java, but the MySQL situation breaks my heart. On to MariaDB.
Why wouldn't there be? Sure, Windows has COM, but that doesn't help for other OS's. Is there some other language/OS agnostic object model that you think is better?
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
No, but in my early programming days, trying to program Windows nearly put me off programming entirely.
John_Chalisque
I've been programming in Java since it first came out, and I never had any particular problems with it, other than the fact that it's rather verbose. I've been thinking there must be a way to accomplish the same thing without so much boilerplate code. Then I discovered Scala (which runs on the JVM and can easily integrate with existing Java libraries). Mind you there are some things about Scala that are kinda weird, like so much optional syntax and type inferencing makes it sometimes hard to read. But I've been finding it a joy for new code I write, almost Java-like but much less verbose, plus you get the functional programming capabilities that Java lacks. Some of the library code that's out there is hard to understand because of the nature of the syntax, but after you study it a bit, it's not too bad.
For those of us old enough to remember, Java is, in fact, the new COBOL. COBOL, like Java, was the language of choice for software engineers of a bygone era (the 1970's), and suffered from a similar verbosity, clumsy syntax, and prevalence of boiler-plate code (substitute copylibs for jars and you are halfway there). I wrote COBOL for a living for decades and never, ever, coded most of the mandatory code sections.
When I was engaged in my first enterprise level Java project (a JBoss app), I was amazed at the similarities between the two languages. Despite the fact that the syntax and structure are completely different we have the same slavish devotion to form and "correctness". Of course, most people alive and writing code now are completely unaware of this, having never encountered COBOL in an enterprise environment.
Not saying this is a bad thing. Just saying. COBOL was also more or less controlled by one company, and that company was IBM due to the IBM's complete dominance of the mainframe market.
GNU Classpath, GCJ, GIJ. IKVM.NET, technically, too.
The road to tyranny has always been paved with claims of necessity.
REST is stateless. Also (as far as I know), works over HTTP. Java is plenty more than a web server platform. CORBA in java would allow one to consume an out of process object/server written in, say, Visual Basic or Lisp for all it matters, statefully, whether local or remote (think perhaps, a running service, or an instance of a document editor).
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson