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

8 of 109 comments (clear)

  1. Funny ... by gstoddart · · Score: 4, Insightful

    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.
    1. Re:Funny ... by i+kan+reed · · Score: 4, Funny

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

  2. Open Source it by ArhcAngel · · Score: 5, Insightful

    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
  3. Re:Oracle is why I don't use java by Anonymous Coward · · Score: 4, Informative

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

    False equivalency.

  4. Real mature by RedBear · · Score: 5, Interesting

    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.

    1. Re:Real mature by Nerdfest · · Score: 4, Interesting

      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.

    2. Re:Real mature by Wdomburg · · Score: 4, Informative

      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. :)

  5. Java >> Scala by djbckr · · Score: 4, Interesting

    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.