I have yet to hear an argument for not including closures from someone who actually understands what closures are.
Lets assume for a moment this would be true. And now we look at the many developers who don't want closures. What would it mean? It would mean that many Java developers are overstrained with such a feature. It would mean that Java has reached a point where the average garden-variety programmer can't handle the language any more. It would mean that Java is becoming a elitists language. I fact, I do think that a lot of the imminent Java changes are suggested because the ones making the proposals want to demonstrate their superiority.
A side effect of programming becoming a mainstream job is that indeed the average clue-level of programmers has gone down. Outsourcing companies hire everyone with a pulse being able to spell the word Java. Java became successful because it was simpler, not better, than C++.
Java is finally at a crossroad. Either it will stay simple and manageable or it will become an elitist language. Which side are you on?
|
java.net RSS Feeds
