When comparing Yesod vs IHP, the Slant community recommends Yesod for most people. In the question“What are the best Haskell web frameworks for building RESTful web services?” Yesod is ranked 1st while IHP is ranked 10th. 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
Ranked in these QuestionsQuestion 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 Easy for beginners
With the code generators even haskell beginners can easily build CRUD apps.
Pro Under the hood
Code generators, database schema editors, etc. work with Haskell and SQL files, which can also be edited manually, to get 'under the hood'.
Pro Instant live reloading
Makes for a super smooth development experience.
Pro HSX
If you have experience with react, you feel right at home with the HSX view syntax.
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.
Con (Small) Server deployment
I'm a bit unclear on the memory requirements for the server (which becomes less of an issue every following year).