Play framework 2.10 released • Hacker News Board

Re: Play framework 2.10 released

#41

Post by bad_user » Wed, Feb 06, 2013, 4:00 PM UTC

pepr wrote: post #40

kclay wrote: post #37

Earlier quoted context omitted.

I'm also an Django developer and did a play application some time back[0], so maybe I can give some insight on development with Play!. My background in functional program was non-existent at the time so going in I was already going to have problems. I choose to create my project as Scala project since I wanted to learn the tech. While Scala can be done with normal OOP/procedure programming I wanted to have the full a…

Great writeup, but I have a comment on deploy: do you mean that "play start" can be used for production? Because otherwise, Django has runserver for development. It just shouldn't be used for production.

Play's server is included in the framework and it is production ready.

Re: Play framework 2.10 released

#42

Post by Bogdanp » Wed, Feb 06, 2013, 4:02 PM UTC

pepr wrote: post #40

kclay wrote: post #37

Earlier quoted context omitted.

I'm also an Django developer and did a play application some time back[0], so maybe I can give some insight on development with Play!. My background in functional program was non-existent at the time so going in I was already going to have problems. I choose to create my project as Scala project since I wanted to learn the tech. While Scala can be done with normal OOP/procedure programming I wanted to have the full a…

Great writeup, but I have a comment on deploy: do you mean that "play start" can be used for production? Because otherwise, Django has runserver for development. It just shouldn't be used for production.

`play run` is sort of the equivalent of `runserver`. `play start` is one of the recommended[0] ways of running Play applications in production.

[0] http://www.playframework.com/documentation/2.1.0/Production

Re: Play framework 2.10 released

#43

Post by benmccann » Wed, Feb 06, 2013, 4:29 PM UTC

MatthewPhillips wrote: post #21

Why did they decide to use static methods for the controllers?

With Play 2.1 static controller methods are optional. If you prefix the controller reference in the routes file with @ then Play will instantiate the controller and call your instance method. It can instantiate it with Guice/Spring if you want as well.

Re: Play framework 2.10 released

#44

Post by kaeawc » Wed, Feb 06, 2013, 4:36 PM UTC

Bogdanp wrote: post #42

pepr wrote: post #40

Earlier quoted context omitted.

Great writeup, but I have a comment on deploy: do you mean that "play start" can be used for production? Because otherwise, Django has runserver for development. It just shouldn't be used for production.

`play run` is sort of the equivalent of `runserver`. `play start` is one of the recommended[0] ways of running Play applications in production. [0] http://www.playframework.com/documentation/2.1.0/Production

There is also `play dist` and `play stage`. They both wrap up all necessary assets / dependencies so that you don't even need play installed in order to start a play server (as the play framework jar gets bundled too). We use this for deploying rather than `play start`. The difference between dist and stage is that dist creates a single zip file in the target directory, whereas stage does not. Both create a file named 'start' in the target directory. The docs are not completely clear on that point.

http://www.playframework.com/documentation/2.1.0/ProductionD...

Re: Play framework 2.10 released

#45

Post by seivan » Wed, Feb 06, 2013, 4:47 PM UTC

I've been looking for a way out of Rails. I dislike not having a compiler & analyser as I'm very comfortable with CLANG and LLVM.

Recently I've been looking at GoLang and Scala. Not sure which to go with, but Play seems better than most web frameworks for Go.

But my concern is always ecosystem. Now before you say "You have access to Java ecosystem" please take a look on how amazing the ruby eco system is.

Re: Play framework 2.10 released

#46

Post by ineedtosleep » Wed, Feb 06, 2013, 5:01 PM UTC

I've been eyeing Play for a bit now, but I've been wondering what kind of server it would require for a modest app with basic CMS functionality.

So, for example, will it run fine on a 128MB RAM VPS (assuming average IO speeds), a remote db and nginx?

Re: Play framework 2.10 released

#47

Post by [deleted] » Wed, Feb 06, 2013, 5:25 PM UTC

kaeawc wrote: post #44

Bogdanp wrote: post #42

Earlier quoted context omitted.

`play run` is sort of the equivalent of `runserver`. `play start` is one of the recommended[0] ways of running Play applications in production. [0] http://www.playframework.com/documentation/2.1.0/Production

There is also `play dist` and `play stage`. They both wrap up all necessary assets / dependencies so that you don't even need play installed in order to start a play server (as the play framework jar gets bundled too). We use this for deploying rather than `play start`. The difference between dist and stage is that dist creates a single zip file in the target directory, whereas stage does not. Both create a file name…

[deleted]

Re: Play framework 2.10 released

#48

Post by koevet » Wed, Feb 06, 2013, 5:36 PM UTC

jplmelanson wrote: post #19

rfinley wrote: post #10

nothing that awesome to make me switch from Grails.

Is it easy to do non-blocking code in Grails? I have played with Groovy lately and it is definitely a productive language.

Is not as easy as using the Scala Future API or Akka Actors.

In Groovy you have to use Gpars (http://gpars.codehaus.org/), a third party library which is not as simple as Scala Futures, IMHO

Re: Play framework 2.10 released

#49

Post by tonybaroneee » Wed, Feb 06, 2013, 5:59 PM UTC

speeder wrote: post #8

Why all those fancy effects of things flipping in your webpage? It confused me for a while, until I understood it, then I think it is fancy, and useless. But impressive maybe, if it was done using the tech they want you to use.

It's just a flashy thing to do nowadays in web dev, probably using jQuery Waypoints. I personally think it's quite cool, despite it's apparent uselessness.

Re: Play framework 2.10 released

#50

Post by cellis » Wed, Feb 06, 2013, 5:59 PM UTC

ineedtosleep wrote: post #46

I've been eyeing Play for a bit now, but I've been wondering what kind of server it would require for a modest app with basic CMS functionality. So, for example, will it run fine on a 128MB RAM VPS (assuming average IO speeds), a remote db and nginx?

Play runs on Netty. No nginx needed.