ASP.NET Zero vs Play: What are the differences?
Developers describe ASP.NET Zero as "Base solution for web applications". It is a starting point for new web applications with modern UI and SOLID architecture. It saves time by providing common application requirements as a pre-built Visual Studio solution (with full source code). On the other hand, Play is detailed as "The High Velocity Web Framework For Java and Scala". Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications.
ASP.NET Zero and Play can be primarily classified as "Frameworks (Full Stack)" tools.
Play is an open source tool with 11.5K GitHub stars and 3.86K GitHub forks. Here's a link to Play's open source repository on GitHub.
What is ASP.NET Zero?
What is Play?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using ASP.NET Zero?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?
Play is a central framework/component/library (not sure what to call things these days) in Scala. We <3 Scala, and therefore we <3 Play.
Play is on of several frameworks we are prototyping and vetting for various public-facing websites, and may ultimately be the framework behind the main datapile.io website.
I used Play to build a configuration UI for the service, which let you create and manage the menus (a hierarchical tree of options and actions).