The first two are obviously Scala only which is of no help to those with existing Java code bases. And for templates Japid is much, much faster than the Scala equivalent.
It does seem that real time data management is a good use case for Play2 but curious to know for typical web apps what benefits there would be.
play1.x with scala was quite experimental (play2 is really different and robustly designed) and those benchmarks always generate trolls... Anyway, I can't make people change their mind about those points even if I had numbers to show because everyone sees what he wants to see. This is just subjectivity ;)
Comments
The first two are obviously Scala only which is of no help to those with existing Java code bases. And for templates Japid is much, much faster than the Scala equivalent.
It does seem that real time data management is a good use case for Play2 but curious to know for typical web apps what benefits there would be.
Why would Japid be faster than Scala templates?
http://www.jtict.com/blog/rails-wicket-grails-play-lift-jsp/
This benchmark is based on Play 1 but you can see Japid is 4 - 5 times faster than the Scala template
play1.x with scala was quite experimental (play2 is really different and robustly designed) and those benchmarks always generate trolls... Anyway, I can't make people change their mind about those points even if I had numbers to show because everyone sees what he wants to see. This is just subjectivity ;)