Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariSnap vs wai-routes
When comparing Snap vs wai-routes, the Slant community recommends wai-routes for most people. In the question“What are the best Haskell web frameworks for building RESTful web services?” wai-routes is ranked 6th while Snap is ranked 7th. The most important reason people chose wai-routes is:
Automatically maps routes to datatypes which are checked at compile time. It uses Template Haskell to reduce boilerplate.
Question Ranking
Pros
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.
Pro Provides type-safe routes
Automatically maps routes to datatypes which are checked at compile time. It uses Template Haskell to reduce boilerplate.
Pro Freely mix "unrouted" handlers with typesafe routing and middleware
Can be used without any routing or Template Haskell. "Unrouted" handlers can be freely mixed and matched with typed routing and middleware.
Pro Easy to customise
Wai-routes is extremely easy to customise. It's neutral to other parts of the system such as the templating language, or the wai server being used. Wai-routes only targets and provides full access to the wai API. The wai-routes handlers are also simple functions which are passed the request data and the environment and return a Response in IO. Arbitrary middleware, routes, and handlers can be mixed together to construct an application.
Pro Lightweight
Performs quite well when compared with other Haskell web frameworks.
Pro Subsites support
Subsites provide encapsulation and ability compile time enforcement of contracts between main site and subsites.
Pro Provides nested routes
Nested routes allow reduction of boilerplate code.
Pro Route annotations
Route annotations provide an easy way to "mark" routes for extra processing.
Cons
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.
Con Learning curve
Even though it's a "micro" framework, it has a steep learning curve when using advanced features such as subsites.
