Live data from Hacker News

Play framework 2.10 released

playframework.com

71–76 of 76 posts

Re: Play framework 2.10 released

#72

Speaking strictly about the website redesign, I think that (although nice) it fails to communicate the framework biggest selling points. Some comments on that: * The code-save-refresh workflow: this is mentioned briefly as "hit refresh workflow" which is confusing to say the least. * Some other weird or 'meh' bullet points like type-safety (you're using either scala or java so you take that for granted) or stateless-…

Anyone can write "stringly" typed code in Java or Scala.

Re: Play framework 2.10 released

#73
post #44
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…

You do not need "play" installed, as Play is using SBT as the package manager.

So without the framework installed and in your PATH, you can just go to an app's directory and do "sbt start". It will download all dependencies needed, compile your app and start the server.

Re: Play framework 2.10 released

#74
post #14

When they say "predictable and minimal resource consumption (CPU, memory, threads)", what kind of numbers are we talking about, roughly?

They say they're using Akka to provide actors. And Akka seems... fast and small: http://akka.io

How fast and how small? How many K of memory?

Re: Play framework 2.10 released

#76

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?

I have Play! running on my Raspberry Pi with a total of 232 MB RAM and it runs fine, although it's a bit slow. Play! itself uses about 55 MB, so it might get a bit tight if you plan to run some other software too.
Post reply on HN