Very similar to Scotty, except with the ability to nest handlers and embed parsers as a location to handle.
Ranked in these QuestionsQuestion Ranking
Pro Simple and Concise
Routing a RESTful api is very literal in Nested-Routes.
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 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.
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.