はてなブックマーク

2017 state of Haskell survey results by Taylor Fausak on November 15, 2017 I am excited to announce the results of the 2017 state of Haskell survey, published by Haskell Weekly! To the 1,335 people that responded to the survey: Thank you! I appreciate your feedback. You can download the anonymized responses as JSON or CSV. The responses are licensed under the CC BY 4.0 license. November 29, 2017 u

Automatically export Haskell modules by Taylor Fausak on December 30, 2016 I am happy to announce the 1.0.0 release of Autoexporter, a tool for automatically exporting Haskell modules. What does that mean? Haskell modules can re-export other modules in addition to exporting things defined directly in them. In fact, my Haskell package checklist recommends providing a single module for users to impo

This post covers everything you need to know about developing a Haskell package. I wrote it because I made a few packages and nothing covers the entire process. The Cabal user guide provides good low-level information, and Sebastiaan Visser’s Towards a better Haskell package gives some nice high-level guidance. This post covers both of those and fills in some of the gaps left by them. Use Git for

Building a JSON REST API in Haskell by Taylor Fausak on October 21, 2014 I spent the last couple weeks building a JSON REST API in Haskell. I called it Hairy. It’s available on GitHub and on Hackage. I learned a lot in the process and wanted to share what I learned. I also wanted to put my code out there to see what I could do better. Patches welcome! Before we dive into the code, let’s take a loo

Haskeleton: a Haskell project skeleton by Taylor Fausak on March 04, 2014 I’m new to Haskell. I’ve learned enough to feel comfortable writing programs in it. I can solve code katas like exercism.io, H-99, and Project Euler. Yet I don’t feel comfortable developing software with it. Writing idiomatic, maintainable and well-tested Haskell code remains a mystery to me. Cabal, the Haskell build tool, p

Testing a Node.js HTTP server with Mocha by Taylor Fausak on February 17, 2013 I spent the better part of the past week updating a Node.js HTTP server from version 0.4.8 of Node to the most recent version, 0.8.20. I started looking over the change logs but they quickly overwhelmed me. Two years of development on Node, V8, npm, and dependent packages generated a lot of changes. Instead of trying to