Link Details

naa. Scala

No chance. I would hope that no language will "replace" Java (if that ever even happened) unless it had mandatory type checking.

"Java should always have been a dynamic language. Groovy gives us a glimpse of what the Java language could have been." - Why? What is so great about dynamic typing? Scala has shown us that static type checking can be done without getting in the way, using type inference. Therefore I can't see how dynamic typing gives you anything but another source of possible bugs.

You seem to be confusing "dynamic typing" with "dynamic language".

I'll agree with Kieron unless you want to define dynamic language.

String s = "My String" // static typing
s.myWackoMethod() // dynamic language

I can have myWackoMethod(s), but not s.myWackoMethod(), in Java. I fail to see how this makes Java more or less dynamic than any other language.

I'm a big fan of Groovy but also a fan of history.

History shows us that 'replacement' takes a very long time. Imagine someone writing in 1999 that Java would replace Cobol in 2-3 years.

I agree that it is plausible that Java wanes while the JVM thrives with many languages, but this list certainly doesn't persuade that Groovy will be 'dominant' over the others.

The title of this post should be "Why You Should Consider Groovy".

Well, speaking for myself, I already replaced Java with Groovy.
,

On a side note, when we see a link with high activity and a nearly equal number of up and down votes, it is almost always an item of significant interest. I bet we could develop some analytics to identify key currents and issues in the developer community by searching the logs for this pattern :)

I totally disagree. It reminds me of the people who told us a few years ago that Linux would totally replace Windows. I think that such replacements in technology can only occur on two occasions:
- one technology is dying, another one is rising
- a major revolution on the market creates some opportunity for a technology with better native support for this revolution.

IMHO, Java leveraged both opportunities: c++ was dying slowly and 3-tier applications became the norm. Java as a language is not dying, and the only major revolution I see on the marker is the opening of the mobile development world, and I don't see Groovy there.

Disclaimer: Steven's views are not those of the Groovy community, but his own. See my comments on his article.
,
,

No! Java will be replaced by a mix of Java, Groovy, and Scala.

Voted down. For a time, I was sure it was going to be Scala - but of late I have come to the conclusion that for the "masses" of programmers out there writing the typical "Enterprise" application - it will be Java for a loooong time.

The language that prevails has to be a language that nongeniuses can live with.

This post is ABSOLUTE GARBAGE. Groovy is extremely slow and ugly.

If anything Scala is a worthy successor to Java:
http://www.codecommit.com/blog/scala/scala-for-java-refugees-part-1

It is statically typed with Java level performance and is elegant.

I have ZERO interest in Groovy and neither does anyone else I know. Scala. Scala. Scala!

I like and use Scala, but I can't imagine why this comment got upvotes. Perhaps it's humour.