Mojolicious vs Play: What are the differences?
Mojolicious: Perl real-time web framework. Back in the early days of the web, many people learned Perl because of a wonderful Perl library called CGI. It was simple enough to get started without knowing much about the language and powerful enough to keep you going, learning by doing was much fun. While most of the techniques used are outdated now, the idea behind it is not. Mojolicious is a new attempt at implementing this idea using state of the art technology; Play: 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.
Mojolicious and Play can be categorized as "Frameworks (Full Stack)" tools.
"Open source" is the top reason why over 13 developers like Mojolicious, while over 73 developers mention "Scala" as the leading cause for choosing Play.
Mojolicious and Play are both open source tools. It seems that Play with 11.2K GitHub stars and 3.77K forks on GitHub has more adoption than Mojolicious with 2.12K GitHub stars and 498 GitHub forks.
Coursera, Zalando, and Keen are some of the popular companies that use Play, whereas Mojolicious is used by WebbyLab, Binary.com, and OANDA. Play has a broader approval, being mentioned in 112 company stacks & 47 developers stacks; compared to Mojolicious, which is listed in 9 company stacks and 3 developer stacks.
What is Mojolicious?
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 Mojolicious?
Sign up to get full access to all the companiesMake 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.
Web part is fully written on top of Mojolicious. Thanks Sebastian Riedel and all the contributors for the great framework!
Веб бэкенд написан полностью на Mojolicious. Спасибо Риделю и всем участникам за этот фреймворк!
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).