Not only does it level some valid criticism, it also proposes (for the most part, omitting 'new' would break too much code) workable solutions.
Not only does it level some valid criticism, it also proposes (for the most part, omitting 'new' would break too much code) workable solutions.
Java thrives in environments where stability is a prime concern and Sun's commitment to maintaining backwards compatibility would inspire confidence.
The new languages that are being developed to run on the jvm reduces the need for Java to evolve as rapidly as some would like. If it is proven that these new languages solve problems better than java then it's only a matter of time before developers make the switch.
At this point when it's obvious what features are really desired then it Sun/Oracle may decide that adding those features to the Java language are appropriate.
In this way the new jvm languages sort of act like a research lab to test out new ideas to see which work better.
On top of that I can see one immediate benefit in implementing some of these, which is that to my eyes all java persistence layers are kludges, simply because of the way the language is structured.
This could make writing such software a lot easier and more reliable.