Why building web-apps in Haskell is harder than it ought to be

Which database library? Problem of too much choice.

How to deal with values originating from the DB

Entity id val

How to deal with DB associations / nested records / nested tuples

[(Entity User, Entity Post, Entity Comment)][(Entity Vote, Entity User, Entity Comment)]

How to build a domain-level API

How many different names can one come-up with for the same thing?

How to deal with validations

Why are templates so hard?

Why are ORMs a taboo?

Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.

Any sufficiently complicated RDBMS-backed app, contains an ad-hoc, informally-specified, bug ridden, slow implementation of half of Active Record (or insert your favourite ORM here).

Lack of testing infrastructure — TODO

Conclusion

--

--

Hiring Haskell engineers & FP enthusiasts in Goa, India.

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store