When comparing Scotty vs Spock, 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 Scotty is ranked 5th. 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 Easy to pick up and use
A simple framework cuts development time and costs. To get started, developers only need to understand how to write routing and actions.
Pro Available on gitHub
Having the source code on gitHub means developers can easily suggest improvements and error reports. They also have a community that can help with any problems that come up.
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.
Cons
Con Lacks features due to its small size
Since Scotty is small, it does not contain some features that a complex web application may need. Anything that Scotty can't provide must be either found or written, costing developers.