1. 20
    1. 10

      I’ve been using IHP since last year, first simply for becoming more familiar with Haskell and some toy applications. Since this year my company is building two new projects with it (one is about to launch) and I couldn’t be happier. Working with remote devs is easier than ever (compared to our previous projects built with Django and Python) due to the strict type checking in the compiler and the fact that IHP encourages certain conventions (so a. no discussions between devs, and b. similar to Rails and Django you know instantly where to look for stuff)

      Compared with other Haskell web libraries like Servant or Yesod IHP removes lots of boilerplate is more “stack” or “framework” than library. Perfect for us who ascribe to Django’s “The web framework for perfectionists with deadlines” mantra.

      Not everything is perfect (yet) of course, but the community and maintainers are available in the Slack (accessible via IRC bridge!) and quickly help out with helpful comments / point you in the right direction for a fix / PR to IHP or put it on their todo list.

    2. 4

      To save other non Haskell types from whiskey tango foxtrot-ting at this article, I’ll quote the About link on the repo’s README:

      IHP is a modern batteries-included haskell web framework, built on top of Haskell and Nix.

      1. 4

        Thanks for the feedback! :) I’ve added a sentence describing IHP itself to the start of the release notes.

        1. 2

          That’s awesome thank you! It’s super helpful for folks who are new to your project, and consequently, for adoption :)

    3. 2

      IHP looks really cool and I’ve been following its development for a while now. The Stripe integration part in the release notes looked a bit weird as it made it sound like it shipped with ihp core, but it turns out it’s an optional dependency