As a user of your stuff, it doesn't feel like it. It's been a few months, but I always felt the Java documentation and samples were lacking compared to Scala. Then again things may have changed.

Can you point me to some bugs or examples of this so we can get this fixed? Thanks!

Or the logger interface. It's awful. Great that you use the sl4j interface, but I can't cast it to that type because it's a wrapper for the "real" logger written in Scala. It's annoying, and agreed- using Java in the Play framework feels more like a "look what else it can do" than an intentional use-case.

I just checked it last night. It's much better now. Both Play and Akka documentation and samples for Java & Scala pretty much match.

Here's one example: ReactiveMongo, the only async db library ,is only for Scala.

Is reactivemongo actually tied to play in any way? It seems like it is a completely separate library.

It uses Play's iteratee feature. Also integrates seamlessly with play. My point is that, while the Play team might develop for Java and Scala concurrently, the Play community most definitely is Scala first.

Well let's be clear here.

In Play 1 development happened on Java first and Scala second.

In Play 2 development happened on Scala first and Java second.