Why you never document your code? You didn't document your Clojure libs and now you're continuing the trend with Haskell. If you're going to make libs, please provide the adequate documentation with examples of usage in the code. I'm not gonna keep going back to the README. I'm going to use Hoogle and Hackage. All those comments in the README could be looking all pretty on Hackage right now.
that is frustrated me when entering functional language world. rarely good document compared to other language. In Perl, many modules will have their own tutorial
This is great advice, I read the follow-up links in that post and they're very informative! I'll jot down a task for figuring out how to flip the Seminearring over to bool.
The reason for the original design was that they mated to nested And/Or filters which I knew to be less than ideal but figured it work as a first pass.
Thank you very much and thanks to everyone that helped me build this. You, carter, and the others in the Haskell/Haskell.au IRC channels were a big help. The thank-you list would be huge if I tried to list everybody that made a library I used or whose blog post helped me along.
To be fair, errors are implicitly encoded in the HTTP statuses and I'm not doing anything about Conduit's exceptions right now. This is something I'd like to fix later.
It's spreading pretty rapidly in my circles. It's used by a lot of popular sites, such as Github, Soundcloud, Stumbleupon, Quora, Foursquare, Etsy, etc.
I run the Elasticsearch Berlin UG and we have a steady and fast influx of new people. I've rarely seen communities grow that fast. The community is great and active and Elasticsearch is caring a lot for that.
