Functional programming debugs you

Hasql v2 is here!

For years, every serious Haskell PostgreSQL driver has been chained to the same C library - libpq - with no clean way out.

Hi, I’m Nikita Volkov - architect, consultant, and the author of hasql, one of the two main PostgreSQL drivers in Haskell used in major production projects like PostgREST and IHP.

If you’re working in an organization that maintains a private Haskell codebase chances are you’ve stumbled upon the problem of distribution of packages.

In this post I’m gonna highlight the issues of the “Internal” modularisation convention and provide a proper solution to the same set of problems.

Today I’m announcing the “compound-types” library.

Recently a question by Chris Done on Reddit has spawned yet another debate on the subject of whether Haskell’s laziness is actually a good thing.

Have you ever looked for a numeric type with a zero to hundred range to describe percentage?

Today I’m releasing the “record” library, which is an API of just two quasi-quoters, providing a full-scale solution to the notorious records problem of Haskell!

Like many other Haskellers even after considering myself an expert in the language I still get that amazing “wow” moment, when I learn another elegant thing about its basic concepts, from time to time.

This post is all about the performance of the “hasql” library and particularly its PostgreSQL back end in comparison to its popular direct competitors: “HDBC” and “postgresql-simple”.

Composition and Decoupling Proficient programming is all about decomposition of complex problems into smaller pieces.

A couple of days ago I released the “stm-containers” library.

Profiling in Haskell can be an overwhelmingly confusing task.