When comparing Play vs CaptainCasa Enterprise Client, the Slant community recommends Play for most people. In the question“What are the best JVM web frameworks?” Play is ranked 3rd while CaptainCasa Enterprise Client is ranked 7th. The most important reason people chose Play is:
Play has quite a large community which provides numerous tutorials and videos related to developing with Play. The Play official documentation covers many things, such as the framework itself but also specific stuff such as Akka, SBT and Netty. There are also many big companies that base their main sites around Play, one of them is LinkedIn which provides third-party documentation on a regular basis.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Good documentation and a great community
Play has quite a large community which provides numerous tutorials and videos related to developing with Play.
The Play official documentation covers many things, such as the framework itself but also specific stuff such as Akka, SBT and Netty.
There are also many big companies that base their main sites around Play, one of them is LinkedIn which provides third-party documentation on a regular basis.
Pro Readable code
Play framework's convention over configuration methodology makes most Play projects have a very similar structure. This means that the code written for the framework is very readable. This enables a developer to switch between applications without having to relearn the ecosystem for every project. The built-in templating system also helps with code and makes it possible to have a very low count of lines of code.
Pro Simple for beginners
Play is very simple to get started. The documentation is very helpful for beginners and advanced users alike and the official website has a great "Getting Started" tutorial to begin developing with Play.
Pro Play feautures Non-blocking I/O by default
Play Framework is asynchronous from the bottom up: asynchronous is default in Play API.
Pro Play is an extensive ecosystem
Play uses Akka for concurrency, Scala for a templating engine, Netty as a client-server framework and SBT (Simple Build Tool) for building. And they all come out of the box.
Play also comes with the option to scaffold your applications. Play is an all-embracing ecosystem designed to increase developer productivity and shorten development times.
Pro Easy clustering
Pro Very fast dialogs
Very fast even with many controls. CaptainCasa Enterprise client is much faster than Vaadin when writting similar programs.
Pro Fast and powerful
Pro Longlife framework
Pro CDI via EL
Separation of the backend code and the creation of the pages / Injection of the code (CDI) into the pages via expression language (EL).
Pro High security
Pro Server development with Java
No javascript is needed, everything is developed on the server with Java. Optimized roundtrip.
Pro Free use
Pro Good scalability
In addition to the extremely good performance, which already ensures that the system can be scaled well, clustering of the system is already provided for in the software architecture.
Cons
Con Awkward, non-idiomatic Java API
Con Backward incompatibility
The jump from Play 1 to Play 2.x caused a lot of confusion. While it is important to have some kind of evolution, sometimes it causes backward incompatibility which can create some problems. It makes tutorials or modules made for the old version obsolete. This can make it hard for beginners to find useful resources. The template engine which used Groovy now uses Scala.