When comparing ASP.NET MVC vs CaptainCasa Enterprise Client, the Slant community recommends ASP.NET MVC for most people. In the question“What is the best web application framework?” ASP.NET MVC is ranked 13th while CaptainCasa Enterprise Client is ranked 15th. The most important reason people chose ASP.NET MVC is:
The framework has many build-in tools, and many packages have been written targeting the framework.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Mature
The framework has many build-in tools, and many packages have been written targeting the framework.
Pro Cross platform
.Net Core can work on any platform.
Pro Widely used
It's pretty easy to find a job with it and there's plenty of documentation and tutorials around.
Pro Extensive documentation
There are a lot of resources available to get help.
Pro Fast
Asp.NET Core on Linux is fast accordingly to TechEmpower benchmarks.
Pro Asp.NET core provides balance between magic/agility and craftsmanship
You can get ordinary details quickly but with complete freedom to make your craft, knowing everything that is happening underneath the cloths. The highly modular system makes it possible to scale small applications to large ones with ease.
Pro It has more users than any other backend web framework
Getting your next contract is easy with this on your CV.
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 Core and full ASP.NET are bit confusing sometimes
While not in feature parity (yet) they are still apart and support sometimes funky combinations of features - full ASP.NET has all the bells and whistles but doesn't offer cross platform so you may have to do some research what you really need. That being said, it got a lot better in 2.0.
Con Expensive
You need to have the plate to maintain a site.
