Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Nested-Routes vs Snap, the Slant community recommends Snap for most people. In the question“What are the best Haskell web frameworks for building RESTful web services?” Snap is ranked 7th while Nested-Routes is ranked 9th. The most important reason people chose Snap is:
Snap provides "snaplets". These are self-contained modules of code that provide additional functionality without muddling the core library. Having these resources saves time when developing code.
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 Provides modules for changeable functionality
Snap provides "snaplets". These are self-contained modules of code that provide additional functionality without muddling the core library. Having these resources saves time when developing code.
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 Outdated documentation
The comprehensive Snap documentation is currently outdated (last activity appears to have been 2013), though Snap itself is under active development. Note that this primarily affects tutorials and guides; the API documentation is generated automatically and remains current.
