Enttäuschung ist die häufigste Reaktion auf die Ankündigung Mark Reinholds, JDK 7 werde erneut verschoben werden müssen. Typisch sind Kommentare wie:

I can't deny I'm very disappointed project JigSaw is delayed again. And that the lack of support for this project this last year amazes me really. Jan Goyvaerts

Both schedules are disappointing. Of course everyone knows this and no-one is surprised by that statement. Talden

Nicht selten münden die Unmutsäußerungen in eine offene Kritik an dem Führungsstil Oracles:

So this is what Larry meant by investing a whole lot of money in Java?! Walter Chang

To me, "JDK 7 minus Lambda, Jigsaw and part of Coin" doesn't sound much like "Getting Java moving again" :-( This schedule is very disappointing.Cedric

Werden die Entwickler vor die Wahl gestellt, eine schnelle JDK 7 Version ohne die Projekte Jigsaw und Lambda (=Closures) im Jahr 2011 zu veröffentlichen oder eine späte, aber komplette Version im Jahr 2012, so scheint die Mehrzahl zur ersten, schnellen Variante zu tendieren.

I'm waiting from 2008, I cannot wait any longer! I understand that without Lambda, Jigsaw, and part of Coin, we have to call it Java 6 & 1/2, but IMHO it is better than wait other two years... Claudio De Sio Cesari

We can all agree that it's disappointing that the schedule slipped! Even though I would love to get my hands on lambdas, I would much rather prefer a new release of Java to keep the kettle from freezing... Jeppe Cramon

Eine häufig geäußerte Meinung ist auch, dass durch die Stagnation bei Java andere JVM-Sprachen einen Schub bekommen könnten – allen voran Scala:

One more reason to go for Groovy, Ruby, Python, Scala, .NET or whatever. 95.136.52.32

Neither A nor B is particular compelling and I think alternatives to Java will get yet another boost; meaning, having to endure even more Scala evangelism. Casper

How many years do you think will java can be alive if there is a much much better language alternative "scala" !

Oracle should freeze java in 6 and shift all java lang. efforts to scala in my honest opinion to make java platform state of art again. Serdar Irmak

JRuby-Chefentwickler Charles Nutters Kommentar ist lesenswert. Vieles von dem, was er als Anwender in JDK 7 sehen wollte, sei bereits umgesetzt. Aus der Perspektive des Implementierers dynamischer Sprachen vermisse er allerdings Method handles, die als Bestandteil von Projekt Lambda umgesetzt werden sollten.

So would I be willing to give up Jigsaw, Lambda, and Coin? Jigsaw and Coin, perhaps, though they'd certainly be missed. As for Lambda...if it can't be done "right" in a short term, with a real function type and integration with method handles and invokedynamic, it should be delayed until it can be done right. Charles Nutter

Und Scala? Für Nutter keine Alternative! Insbesondere sei das Problem von Scala, dass die dort implementierten Closures nicht mit anderen Sprachen oder mit Java interoperabel seien.

Oh, and for folks crowing about Scala...please explain to me how Scala solves any of the missing features that "Plan B" would omit. Yes, it has closures, but they're generally not interoperable with other languages or regular Java code (unless you limit your design considerably), which makes them useless for all but Scala developers. Charles Nutter

Das Urteil Charles Nutters lautet deshalb: Scala wird niemals ein Ersatz für Java sein!

There's nothing to address the goals of Jigsaw. And most of the bits of Coin that Scala provides are (I believe) already ready to go. Scala is not a substitute for Java as the lingua franca of the JVM, and it never will be. Charles Nutter