I wrote a pure Haskell solution that implements a messaging middleware from a proprietary legacy DB system to a network for activating mobile devices. It was m

I wrote a pure Haskell solution that implements a messaging middleware from a proprietary legacy DB system to a network for activating mobile devices. It was my first real Haskell project, and although I had lots and lots of book knowledge about the language, the outcome was quite warty. Nevertheless, Haskell delivered what it promised: the software was completed much faster than a roughly comparable C product was before (by a better programmer than me) and making changes to a finished product was very easy and safe and did not cause new bugs. Perhaps the worst problem was the lack of quality libraries for doing some practical things, such as simple socket listening (I had to pretty much code Haskell like it was C in that part), and I had some trouble (bad memory leaks) from the curl library. And even worser than worst was the problem that only one person got interested enough in the language that he helped me with the project, and, although he was able to produce working code in a month from zero experience, he ended up disliking the language.