MEAN vs Play: What are the differences?
MEAN and Play can be primarily classified as "Frameworks (Full Stack)" tools.
MEAN and Play are both open source tools. MEAN with 11.8K GitHub stars and 3.57K forks on GitHub appears to be more popular than Play with 11.2K GitHub stars and 3.77K GitHub forks.
According to the StackShare community, Play has a broader approval, being mentioned in 112 company stacks & 47 developers stacks; compared to MEAN, which is listed in 37 company stacks and 24 developer stacks.
What is MEAN?
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 MEAN?
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
I found mean.io just smooth, fun, orginized and just work out-of-the-box.
MongoDB is a solid NoSQL store. Angular.js is being vetted as a potential front-end framework for the website (though it may ultimately not be used for the non-app site). Everything is running on node.js and hosted via an Express.js web server (though we are looking into Koa.js as it is the official successor to Express.js)
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.
FULL STACK ( preferred if;at all possible! ). Any "NEW" project (all me) I am tasked with I try to sketch it out with MEAN in mind first and then will tweak or stray from the 'plan' when necessary
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).