As someone who's used Play heavily for the past couple of years, I'm very excited by this release, which is Play's best yet.
As someone who's used Play heavily for the past couple of years, I'm very excited by this release, which is Play's best yet.
I always thought Play looked incredible, but the focus on Scala puts me off. Every time I tried it, Java seemed like a second-class citizen in the Play world. I don't have anything against Scala, I'm just not really interested in learning it, especially if I all I want to do is use a web framework.
EDIT: never used the Java side myself, though. EDIT2: here is a nice comment on Java vs Scala: https://groups.google.com/forum/?nomobile=true#!searchin/pla...
It works fine. The only annoying thing is the asynchrone nature forces you to have abstract classes everywhere, but with Java 8 it's no longer a problem.
Could you elaborate?
Akka uses callbacks to handle asynchronous behaviours, which means you need closures, and in Java <8, that means anonymous classes littering your code, which is a real PITA.
I'm not entirely sure why Play has a reputation of being for Scala except that there are fewer web frameworks for Scala than Java, so Play is more popular among Scala developers. I think the other thing that confuses newcomers is that the templates are Twirl templates. They should probably have an extension like .twirl but unfortunately use the extension .scala.html even though you're really not writing Scala at all. You're writing Twirl which is it's own thing and doesn't take more than a few minutes to pick up. (The reason for the .scala.html is that templates get compiled to Scala, but you really don't have to know or care about that)