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."

Comments

Funny ...

[gstoddart]

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.

Re:Funny ...

[i kan reed]

Nothing says "professional tool for serious tasks" like crappy adware shoved in.

Open Source it

[ArhcAngel]

Everyone is thinking it but everyone knows Larry doesn't give anything away for free. Even his free software costs you money somewhere...

realworld suggestions for Java 8

[nimbius]

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'

Re:Oracle is why I don't use java

[Anonymous Coward]

Microsoft doesn't own C++, nor do they release the primary runtime for C++.

False equivalency.

Real mature

[RedBear]

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.

Re:Real mature

[Nerdfest]

No kidding. I'd like to see the sort of syntax sugar that would cut the length of my classes source in half by generating setters and getters (perhaps via annotations like project Lombok does). There are a few other things of this sort that would vastly reduce the amount of boilerplate code.

Re:Real mature

[sid.the.technician]

Could you enlighten me please, what is your language of choice for your next big project? Php, perl maybe? And I am talking about writing business logic, database access and soap communication. I hate Oracle with passion (because of their database product and pricing), but java (on servers, not some shitty applets) is in reality the only option when you want to write anything "business oriented".

Re:Real mature

[Wdomburg]

1) How many of the people who reflexivly project hate at Java have solid, defensible reasons for doing so? Do you think people form opinions based on evidence and thoughtful consideration?

2) Examples, please.

3) Well C is not a long-lived programming language, then. COBOL, FORTRAN and LISP have been going strong since the 1950's!

3.1) Plenty. Most of the applications on my phone runs Java (Android). My cable box (OCAP). My Blu-ray player (BD-J). Several of the applications I administer or use professionally (IntelliJ, Confluence, Jira, Zimbra, JMeter).

Just because you don't see it doesn't mean you don't use it. And even if you don't use doesn't mean other people don't use it. Java is an incredible pervasive language in the embedded and server space.

3.2) And?

3.3) With a twelve year history, multiple implementations and no hint of a successor, this strikes me as needless fear-mongering. Microsoft is proprietary, not fickle. Most of their standards have excellent longevity and they have far longer support cycles for their products than most of the Unix world.

As for performance, you're full of it. :)

Java >> Scala

[djbckr]

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.

Re:Open source what exactly?

[ArhcAngel]

Hand it over to IEEE or another organization to steer its development. Oracle doesn't exactly want what's best for Java.

Re:Oracle is why I don't use java

[Kimomaru]

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.

Re:Security

[broken_chaos]

They should just ditch the browser plugin by default. Support it as 'legacy' for a version or two, but don't ship or install by default (hell, they could even only offer it to corporate customers for all I care). It's the biggest problem with Java -- otherwise you pretty well get what you expect if you download and run unknown code, no worse than any other language. It's not like C's ability to completely tear your operating system apart if you run code you don't know is a bug, after all.

Re:Oracle is why I don't use java

[John Allsup]

No, but in my early programming days, trying to program Windows nearly put me off programming entirely.

Re:Java Scala

[bagman1673]

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.