Anyone transition from ASP.NET(MVC) to Play Framework

Question

Been a long time user of the Microsoft stack and looking at other frameworks to learn and maybe transition to. I ran across the Play Framework recently and started working through some of the demos and really like it. Anyone from a .NET background transition to Play and if so what has been your experience so far?

Answer 1

Ive mostly written projects using ASP.NET MVC/C#/SQL server but choose to experiment with Play/Java/Postgres in a recent project.

On the whole Im quite productive with Play, specific things I like include:

• The way in which views are compiled which greatly helps spot typos
• The futures and promise framework
• Very easy to package and deploy, i.e. play stage
• Ability to write and include plugins in just a few lines of code
• The fact that caching is built in

Potential disadvantages

• Can take a while to compile which can be annoying during development/testing
• Documentation is not always as detailed or extensive compared with ASP.NET MVC
• Availability of code samples
• The fact that the http context is lost during async events (i think it has since been fixed in play 2.1)
• I find the membership provider and config of role permissions in the web.config file easier to work with compared with the Play Secured class (then you dont need to specifically annotate each controller/method)
• No LINQ within Java (Not a fault of Play itself) but if you use scala then you can use lamda expressions
-