Why I'm Moving Away from the Play Framework
whilefalse.blogspot.com
Why I'm Moving Away from the Play Framework
1–10 of 88 posts
Re: Why I'm Moving Away from the Play Framework
#2I'd be very interested to hear people's responses to this post. I've been considering learning Play as I was very impressed with what I saw.
Re: Why I'm Moving Away from the Play Framework
#3I'm interested to know what alternative framework the author has chosen in place of Play!.
Re: Why I'm Moving Away from the Play Framework
#4I'm curious as to specific code examples where the author is having problems. I'm thinking about using Play! or Lift for a pet web app using Scala. Does anyone have experience using either?
Re: Why I'm Moving Away from the Play Framework
#5I'd be very interested to hear people's responses to this post. I've been considering learning Play as I was very impressed with what I saw.
It is a very well written opinion piece that gives his ( valid ) reasons for not using play any more. That being said he doesn't say anything bad about the framework or the idealogy behind it and in fact laments having to move away from its ease of use.
He does bring up the point that Play 1.X is essentially out to pasture at this point. Thats not to say typesafe can't come back and once 2.0 is settled and fix the outstanding bugs , but as far as the community is concerned most have moved on to 2.0 or are aren't experiencing these issues.
For my part I have never ran into any serious bugs on my Play apps and services. I would note that I don't have any very large scale deployment, mostly just internal applications. I am however using Play 2.0 as the foundation for my next big project and so far even the RC have proven stable and functional.
Re: Why I'm Moving Away from the Play Framework
#6I looked into Lift. Steep learning curve. It would be ok for a single person, but a large team coming up to speed on Lift/Scala looks hard. Then I decided to stick with what I know best Ruby/Javascript/Node.
Re: Why I'm Moving Away from the Play Framework
#7I think that any platform has some gotchas especially a 1.x version, however in my experiences with it it was fast and less boilerplate than a normal Java project and we didn't have any of these issues rolling out locally and to Google AppEngine.
I'd still only choose it if I had to use Java though.
If you can roll with Django you can roll with Play. Although, I always prefer a python microframework such as flask nowadays.
I also see how Play is now part of typesafe, so that could get better or worse, but it is the right direction for Java web apps to go.
Re: Why I'm Moving Away from the Play Framework
#8So what's the best alternative for a Java shop?
Re: Why I'm Moving Away from the Play Framework
#9I'd be very interested to hear people's responses to this post. I've been considering learning Play as I was very impressed with what I saw.
It is a very well written opinion piece that gives his ( valid ) reasons for not using play any more. That being said he doesn't say anything bad about the framework or the idealogy behind it and in fact laments having to move away from its ease of use. He does bring up the point that Play 1.X is essentially out to pasture at this point. Thats not to say typesafe can't come back and once 2.0 is settled and fix the ou…
s/he/she/
s/his/her/
Re: Why I'm Moving Away from the Play Framework
#10Valid points about bug fixes and outstanding issues. I think the Play 2 announcement was met with a mixture of trepidation and excitement from the community. If support for 1.2.x was to decrease further then I'd be concerned.
For what it's worth, I've been developing a Play (now 1.2.4) app for a year now and it's been a blast. Sometimes you can see the framework's immaturity, but I haven't run into any showstoppers like the author.