By bloid
via ola-bini.blogspot.com
Published: May 20 2008 / 00:17
As some of you might have noticed I am not extremely fond of everything the Java language. I have spent some time lately trying to figure out how I would change the language if I could. These changes are of course breaking, and would never be included in regular Java. I've had several names for it, but my current favorite is unJava. You can call it Java .314 or minijava if you want. Anyway, here's a quick breakdown of what I'd like to see done to make a better language out of Java without straying to far away from the current language
Comments
kunnar replied ago:
Why not to break compatibility in order to get some design issues fixed? In my opinion, it is not so bad idea at all. What if new language is very similar to current one and old code can be upgraded to new language easily? Then we could upgrade our current code base and could move on conveniently.
cbang replied ago:
kunnar, unfortunately there's a huge (underlined, in bold, empathized etc.) conservative movement who things the best virtue of Java is that of binary compatibility or people who just don't particular care for post 1.4 additions.
Nick Brown replied ago:
I think this is a moot point with Scala around. We have a language that has all these features and which can interact seamlessly with Java. Changing the language itself in a way that completely breaks compatibility is a pretty stupid idea, considering all the millions of lines of existing code that would have to be changed in order to support it. But the advantage of the JVM platform is that we can make a radically different language that retains compatibility with existing Java binaries.
Voters For This Link (13)
Voters Against This Link (14)