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
Microsoft doesn't own C++, nor do they release the primary runtime for C++.
False equivalency.
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.
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.