Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariYesod vs CodeBehind
When comparing Yesod vs CodeBehind, the Slant community recommends Yesod for most people. In the question“What are the best backend web frameworks?” Yesod is ranked 12th while CodeBehind is ranked 36th. The most important reason people chose Yesod is:
While not required, Yesod offers templating through a Shakespearean family of languages to produce page code.
Specs
Question Ranking
Pros
Pro Offers templating for type-safe, well-formed content
While not required, Yesod offers templating through a Shakespearean family of languages to produce page code.
Pro Uses type-safe URLs
Ensures that data provided by the URL is type-safe. This means that data in the URL has a definitive type.
Pro Can be used without knowing much Haskell
While Yesod is written in Haskell, developers can achieve basic functionality without much investment in the language.
Pro Modern
CodeBehind is a modern framework with revolutionary ideas.
Pro Code-Behind
Code-Behind pattern will be fully respected.
Pro Under .NET Core
Your project will still be under ASP.NET Core and you will benefit from all the benefits of .NET Core.
Pro Get output
You can call the output of the aspx page in another aspx page and modify its output.
Pro Modular
It is modular. Just copy the new project files, including dll and aspx, into the current active project.
Pro Simple
Developing with CodeBehind is very simple. You can use mvc pattern or model-view or controller-view or only view.
Pro Fast
The CodeBehind framework is faster than the default structure of cshtml pages in ASP.NET Core.
Cons
Con Is hard to customize
Learning how Yesod works internally is hard. It is a large framework with complicated components. Finding the appropriate code and understanding how it contributes to the framework is difficult, meaning developers will struggle.
Con Too much template haskell
You actually want to code in haskell and not some DSL with "magic" hidden under the bonnet.
