We use Play heavily at work (eg. 50k SLOC). I love it.
However, I'm pretty nervous about 2.0, due to the tight coupling with Scala. I still have a bad taste in my mouth from trying to use Lift, and I did not care for sbt at all.
While typesafe templates seem like a good thing, I can't recall ever having bugs that would have been caught by them, and it looks like it will eliminate the magical boilerplate-free parameter passing from the current version of Play.
In two full days of effort, I couldn't get a simple set of pages done. I found Play! right after that, and finished the pages completely painlessly in roughly no time.
I would chalk it up to terrible terrible documentation, and being unable to read the example code that I did find due to the Scala practice of using random characters as method names. e.g. something = x % y %% z ||| a
The documentation was really the worst, though. Maybe it's improved in the last year.
Comments
We use Play heavily at work (eg. 50k SLOC). I love it.
However, I'm pretty nervous about 2.0, due to the tight coupling with Scala. I still have a bad taste in my mouth from trying to use Lift, and I did not care for sbt at all.
While typesafe templates seem like a good thing, I can't recall ever having bugs that would have been caught by them, and it looks like it will eliminate the magical boilerplate-free parameter passing from the current version of Play.
What turned you off of Lift?
In two full days of effort, I couldn't get a simple set of pages done. I found Play! right after that, and finished the pages completely painlessly in roughly no time.
I would chalk it up to terrible terrible documentation, and being unable to read the example code that I did find due to the Scala practice of using random characters as method names. e.g. something = x % y %% z ||| a
The documentation was really the worst, though. Maybe it's improved in the last year.