Re:Ask HN: In 2016, will Rails & Django be competitive again...
by saryant on Wednesday October 02, 2013 @10:56AM
(#6482752)
> builds upon the Akka actor framework
This is really where Play shines. I wouldn't bother with Play for a basic CRUD app, it makes you do too much grunt work yourself (e.g., authentication). But when you have a backend built on Akka and want to build a reactive, event-driven front-end Play makes it trivial.
Akka is the key. Its actor model just makes reasoning about concurrency so easy because of how it deals with state. Add in remoting and clustering and you've got a highly scalable, event-driven clustered backend without too much extra work on your part. Play fits into that sort of ecosystem quite nicely.
[deleted]
Re:Ask HN: In 2016, will Rails & Django be competitive again...
by saryant on Wednesday October 02, 2013 @10:59AM
(#6482774)
I think you're missing the real point of Play which is reactive programming. Integration with Akka, simple support for Comet/WebSockets, fully asynchronous. That's what makes Play awesome, not its support for request/response.
In many ways, it is beyond Rails. For instance, it offers type-safe URLs and builds upon the Akka actor framework (allowing you to schedule asynchronous tasks, make reactive web applications, etc.).