Language wars
Posted on April 8th, 2009 in Java, Programming, Ruby, Work | 3 Comments »
Is it just me who’s loving this whole Ruby vs. Scala debate going on lately? So far it shows that:
- No language can prevent bad code.
- There will be never an ultimate language, but there will always be people to defend the one they are using.
- Java (the language, not the platform) is dead.
I know it’s not the first time we have a language war and I have to confess I was missing that a little. Years ago it was Visual Basic vs. Delphi, then C++ vs Java, now it’s Ruby vs. Scala. And I have to confess: I’m already curious to see what will be the next one.
3 Responses
“No language can prevent bad code.”
Isn’t that the ultimate truth?
I find it fascinating … not so much the cult-like debates, but the actual technology and the insight into the decision process of an organisation like Twitter.
The biggest factor for me is that Java is now really all about the JVM, and the language is a bloated misery that is best avoided
It’s always sad when people get religious about tools =/
More interesting question is – when will the big clients wake up to the fact that Java-as-a-language is mouldering and allow use of other languages on the JVM?
@Toby Hede
I hope it’s the truth. The funny thing is how people tend to forget that.
This decision process is interesting indeed. It even makes me wonder: could Twitter be as popular as it is if made completely in Java, for example? I really don’t see why not.
@James Shiell
I believe it won’t happen in the next couple of years. The bright side is that we can probably hide whatever language inside the WAR file