Introducing
The Slant team built an AI & it’s awesome
Find the best product instantly
Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Try it now
4.7 star rating
0
What is the best alternative to Servant?
Ad
Ad
IHP
All
6
Experiences
Pros
4
Cons
1
Specs
Top
Pro
Under the hood
Code generators, database schema editors, etc. work with Haskell and SQL files, which can also be edited manually, to get 'under the hood'.
See More
Top
Con
(Small) Server deployment
I'm a bit unclear on the memory requirements for the server (which becomes less of an issue every following year).
See More
Top
Pro
Easy for beginners
With the code generators even haskell beginners can easily build CRUD apps.
See More
Top
Pro
Instant live reloading
Makes for a super smooth development experience.
See More
Top
Pro
HSX
If you have experience with react, you feel right at home with the HSX view syntax.
See More
Specs
License:
MIT
Written in:
Haskell
Repository:
https://github.com/digitallyinduced/ihp
Hide
0
5
0
wai-routes
All
8
Experiences
Pros
7
Cons
1
Top
Pro
Provides type-safe routes
Automatically maps routes to datatypes which are checked at compile time. It uses Template Haskell to reduce boilerplate.
See More
Top
Con
Learning curve
Even though it's a "micro" framework, it has a steep learning curve when using advanced features such as subsites.
See More
Top
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.
See More
Top
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.
See More
Top
Pro
Lightweight
Performs quite well when compared with other Haskell web frameworks.
See More
Top
Pro
Subsites support
Subsites provide encapsulation and ability compile time enforcement of contracts between main site and subsites.
See More
Top
Pro
Provides nested routes
Nested routes allow reduction of boilerplate code.
See More
Top
Pro
Route annotations
Route annotations provide an easy way to "mark" routes for extra processing.
See More
Hide
See All
Experiences
Get it
here
3
0
Happstack Lite
All
5
Experiences
Pros
3
Cons
2
Top
Pro
Has extensive documentation
There is extensive documentation and tutorials for Happstack and Happstack Lite available for use. Documentation and tutorials help programmers write their code; with so many options, programmers will have an easy time learning the framework.
See More
Top
Con
Handles exceptions poorly
When an exception occurs on the server, the error gets printed. By seeing an error that makes no sense to the user, his experience is negatively impacted. Having a negative experience can mean a user never visits the site again.
See More
Top
Pro
Molded through 7+ years of feedback
Happstack has been around for over seven years. During this time developers used the framework and offered feedback to improve it. As a result, it is stable and unlikely to have major changes. Happstack Lite was created from all of this feedback
See More
Top
Con
Allows bad code by not enforcing logic separation
Happstack allows developers to write code for controllers, routing, and models together. Doing so will dirty the code and make maintenance harder.
See More
Top
Pro
Shares all of its components on gitHub
Having open source means that developers can customize the framework and offer suggestions and solutions to the code.
See More
Hide
Get it
here
2
0
Apiary
All
3
Experiences
Pros
2
Cons
1
Top
Con
Mediocre documentation
Users must rely primarily on the example project and auto-generated API documentation (Haddocks). The author of Apiary is not a native English speaker and openly acknowledges this issue.
See More
Top
Pro
Automatically generates API documentation
Apiary generates comprehensive HTML documentation based on your API routes.
See More
Top
Pro
Type-level routes
Apiary provides type modeling, down to URL parameters, ensuring type safety.
See More
Hide
Get it
here
2
0
Nested-Routes
All
4
Experiences
Pros
3
Cons
1
Top
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.
See More
Top
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.
See More
Top
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.
See More
Top
Pro
Simple and Concise
Routing a RESTful api is very literal in Nested-Routes.
See More
Hide
Get it
here
1
0
Yesod
All
6
Experiences
Pros
3
Cons
2
Specs
Top
Pro
Offers templating for type-safe, well-formed content
While not required, Yesod offers templating through a Shakespearean family of languages to produce page code.
See More
Top
Con
Is hard to customize
Learning how Yesod works internally is hard. It is a large framework with complicated components. Finding the appropriate code and understanding how it contributes to the framework is difficult, meaning developers will struggle.
See More
Top
Pro
Uses type-safe URLs
Ensures that data provided by the URL is type-safe. This means that data in the URL has a definitive type.
See More
Top
Con
Too much template haskell
You actually want to code in haskell and not some DSL with "magic" hidden under the bonnet.
See More
Top
Pro
Can be used without knowing much Haskell
While Yesod is written in Haskell, developers can achieve basic functionality without much investment in the language.
See More
Specs
License:
MIT
Price:
free
Written in:
Haskell
Repository:
https://github.com/yesodweb/yesod
Hide
Get it
here
49
11
Scotty
All
3
Experiences
Pros
2
Cons
1
Top
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.
See More
Top
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.
See More
Top
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.
See More
Hide
Get it
here
5
2
Snap
All
2
Experiences
Pros
1
Cons
1
Top
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.
See More
Top
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.
See More
Hide
Get it
here
6
3
Built By the Slant team
Find the best product instantly.
4.7 star rating
Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Try it now - it's free
{}
undefined
url next
price drop