Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariNested-Routes vs IHP
When comparing Nested-Routes vs IHP, the Slant community recommends Nested-Routes for most people. In the question“What are the best Haskell web frameworks for building RESTful web services?” Nested-Routes is ranked 9th while IHP is ranked 10th. The most important reason people chose Nested-Routes is:
If you have a data encoding you would like to allow as a path chunk, you can do so by routing with an attoparsec parser or regular expression _directly_.
Specs
Question Ranking
Pros
Pro Embed Attoparsec parsers and regular expressions in a routable url
If you have a data encoding you would like to allow as a path chunk, you can do so by routing with an attoparsec parser or regular expression directly.
Pro Nesting of Handlers
The ability to give a handler child handlers turns a list of handlers into a tree of handlers - much easier to maintain.
Pro Simple and Concise
Routing a RESTful api is very literal in Nested-Routes.
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 Complicated Types
There is a lot of advanced language extensions in use for the engine - if you have a typo somewhere, the errors are practically impossible to understand.
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).
