Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Nested-Routes vs Scotty, the Slant community recommends Scotty for most people. In the question“What are the best Haskell web frameworks for building RESTful web services?” Scotty is ranked 5th while Nested-Routes is ranked 9th. The most important reason people chose Scotty is:
A simple framework cuts development time and costs. To get started, developers only need to understand how to write routing and actions.
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 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.
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 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.
