Quo Vadis Oracle and Dynamic Languages?
Serdar Yegulalp has just written a post titled “What's Java's Future?” where he expresses his point of view about the evolution of Java in the perspective of Oracle's buy and the competition with dynamic languages such as Ruby and others.
It's an interesting post, even though some things can be seen in completely different perspectives - for instance, he asserts that a Java programmer from 2003 would have no problems in reading today's code; thus he concludes that there has been no evolution. That's right if you stayed in Serdar's perspective and looked only at the language; but in 2003 I would have rolled my eyes in seeing what EasyMock, or lambdaJ, or AspectJ annotations in Spring, or Project Lombok can do, not to mention that many design styles have changed, so I conclude that innovation (and doing “more advanced things that much faster“) doesn't necessarily happen within the syntactic bounds of a language.
But this of course is just my point of view - let's try a more objective perspective. For instance, let's focus on the initial statement: that other languages are “eclipsing” Java.
I've been hearing this for years, and yet I don't see much change around. I don't want absolutely to be harsh, but I think that when asserting such a sentence one should provide some data (which of course could prove me wrong). Sticking to anedoctal experience, in an industrial perspective I'm rather seeing more and more interest (and money) in languages such as ActionScript and (unfortunately) ObjectiveC, rather than Ruby or Python.
So, here it is my question: what is, in your opinion, Oracle's attitude towards dynamic languages
(with the exception of JavaFX)? What everybody agrees on, including the most harsh critics, is that they know how to make money. So, Oracle putting money on dynamic languages would mean they are growing; the opposite would make me think that the chances of Ruby and friends to “eclipse” Java are very low.
What do you think?
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)