4 ms·

I really hope someone picks up Play 1.2.x and maintains it. The Play 2.x alleges to be bi-lingual, Java and Scala, but it's pretty much an Scala version of Play

• kirang1989 14y ago
  I've tried asking people about adding new features to the Play 1.2.x code, but the developers have firmly said that they would no longer add features to the 1.x line :(
  • mahmud 14y ago
    Play is begging to be forked, specially as the developers' vision diverges from that of Play 1.2.x users. We have a big ERP app built on Play 1.2 and have no interest in moving to Scala and 2.0. Our version of Play is, for all intents and purposes, a fork.
• nameiscarl 14y ago
  I second that. As javaists are concerned, Play 2.x is not a good thing : bigger, slower, more rigid and with a lot scala dependencies/idioms you don't care about. Forking Play 1.2.x could be a solution (and maybe remove the python console. After all that's a java framework) Or. Or one may use the extensibility of Play 2.x to remove the scala parts javaists don't want. It shouldn't too hard. Here's a thread on the official forum about it : https://groups.google.com/forum/?fromgroups=#!topic/play-framework/-BxpVFgyrgY https://groups.google.com/forum/?fromgroups=#!topic/play-fra...
• ubersoldat2k7 14y ago
  I'm developing several apps in Java and Play 2 and I haven't found any problems more than the templates being in Scala.