Closures in Java 7: Not Likely http://www.davidflanagan.com/2010/05/closures-in-jav.html
Anybody on this list have any insight to what's going on at Oracle regarding Java? Is this article an over reaction or spot on? I have to admit am starting to get worried about Oracle's stewardship of Java. They need to be making a public perception that they're on top and on the ball with prior stated goals for the language. Yet it's more like they've all gone on holiday and turned the lights out. The sad thing in my case is I was on the verge of getting a development group that's been using C# .NET for a few years to switch to Java and an app server to do the re-tooling of their app. (This is not at all a web centric application and a JEE app server actually would have a ton of advantages for their particular middle-ware. This is very much of a case of the plethora of libraries and frameworks per Java platform would be much greater advantage than the latest C# language feature set.) Yet if Java is just slipping into the depths of language atrophy, as alluded to by this linked posting, then that makes for a tougher sell. If I could at least have said "see, you'll be getting closures in Java 7 real soon now..." C# has closures and lambdas now and once you start using those facilities you get spoiled to them. My very sold reasons for wanting them to switch has to contend with these kinds of nits - despite these things are not as crucial as the Java Concurrency library or the fork/ join framework, or cluster singleton mbeans, etc., etc. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
