When comparing Miso vs Nested-Routes, 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 Miso is ranked 12th. 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_.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Fast
Pro Easy
Pro Isomorphic
Pro Virtual DOM
Pro Type-sharing
Pro Type-safe routing
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.
Cons
Con Bloated
Requires nix, ghcjs, and a lot of other sources of significant technical debt to the project.
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.