When comparing Spock vs Snap, the Slant community recommends Spock for most people. In the question“What are the best Haskell web frameworks for building RESTful web services?” Spock is ranked 2nd while Snap is ranked 7th. The most important reason people chose Spock is:
Spock parses request URLs into well-typed data without requiring your routes to be declared at the type level.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Type-safe, function-level routes
Spock parses request URLs into well-typed data without requiring your routes to be declared at the type level.
Pro Small but complete
Unlike scotty it manages to be small and, at the same time, includes all the necessities like sessions and db pool.
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 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.