When was the last time you were sitting around trying to figure how to solve something, and said, dang-it, if java only had closures...
Apparently more often than you. I agree that the most complex uses of BGGA are complex to understand, but then these more complex cases are complex to express in java anyway - if these most complex cases prove to be common in your code-base you are probably abusing the facility and not writing the simplest solution to solve the problem... Abuse of language features in java is possible with boxing, anonymous classes, statics, initialisers - it's nothing new and poor language use by some developers is not a reason to restrict the growth of the language.
That said, if it proves more complex than the concept it's expressing it is an issue and if it sets the knowledge bar too high, making acquiring adequate developer resources impossible java may shit in its own nest - forcing projects to other languages. |
java.net RSS Feeds
