Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariASP.NET MVC vs Pyret
When comparing ASP.NET MVC vs Pyret, the Slant community recommends Pyret for most people. In the question“What is the best programming language to learn first?” Pyret is ranked 50th while ASP.NET MVC is ranked 61st. The most important reason people chose Pyret is:
You can use the development environment without installation in your browser and share your programs via the Google Drive integration.
Question 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 Online IDE
You can use the development environment without installation in your browser and share your programs via the Google Drive integration.
Pro Designed for education
A primary goal of Pyret is to be an excellent choice for a first programming language. This heavily influences the development of the language. For example: if it's felt that some aspect of the language could be made better for the language's users, The development team won't hesitate about implementing breaking (non backwards compatible) changes into Pyret for the greater good of the language. This makes Pyret an impressively "wart free" programming language.
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.
Con Missing IDE features
For example: content assist, go to declaration, etc.
