Re: @Override
On 7/24/2012 4:57 PM, Silvio Bierman wrote:
On 07/24/2012 01:53 AM, Arne Vajh?j wrote:
On 7/23/2012 6:22 PM, Silvio Bierman wrote:
True.
But we are still waiting for the language that gets everything right.
There is no such language and there never will be since it is and always
will be a moving target.
And both the problems to be solved and the people trying to solve them
are different.
I am not saying that Scala is the perfect language for anyone, let alone
for everyone. But for me it is so extremely much closer to what I
need/want than Java that, since it is already available, it would be
stupid FOR ME not to use it. The fact that Scala happens to fix a lot of
Java design errors is a minor point, by the way.
I also like Scala.
But I do not see it overtake the role of Java.
Two reasons:
- the language is not stable enough
- the language is too difficult
For others it may be Groovy, Clojure or perhaps even Ruby if you are not
tied to the JVM.
You can run Ruby in the JVM.
And for many staying with Java may be the most sensible
thing to do. But even then, it remains a fact of life that there will be
JVM languages that chose to fix Java omissions and mistakes.
For me one thing I like is that the Scala language developers are not
stuck on backward compatibility. They are not afraid to fix things, even
if that will break existing code. The language comes/exists in versions
and existing code may be tied to an older version. Does not have to be a
problem at all and the owner of the code can choose to update it if and
when he desires so.
If only they had done that with Java they could have fixed a lot of
annoying things. Now newer versions introduce new language features but
developers can not use them since their users do not want to upgrade to
the latest JVM. That is also a version problem, but then backwards.
A high level of backwards compatibility is a requirement in much
of the enterprise market.
Arne