3 ms·
As to your question, I think it is both. The author's ability to walk you through his thought processes in a clear and concise manner, his general strength as a
by hashtree 12y ago
As to your question, I think it is both. The author's ability to walk you through his thought processes in a clear and concise manner, his general strength as a writer, the fact that he added diagrams and models to help the reader, and that this did not seem to be written only for Haskellers to read... well they all add up to what you are describe. Kudos to the author.
- spopejoy 12y agoI'm having an interesting experience with this at my job ... Haskell appears to be MUCH more approachable when you understand the problem at hand. So much Haskell pedagogy wants you to write a compiler or a parser or ... whereas this article is taking you through a solution. And whaddyaknow -- Haskell comes across as gorgeous, elegant, compact, and highly comprehensible. When I show a FIX server or REST API written in Haskell to a non-Haskeller coworker (ie everyone else :) ), with minimal explanation they're getting what's going on. I look forward to many more "Haskell-in-anger" articles to show the world how fantastic it is to work with.
- eru 12y agoYes. Haskellers are just too much in love with compilers and parsers. Those are much easier to write in Haskell, but not enough people have grappled, and suffered (and failed) to write one in eg C to appreciate.
- stefans 12y agoAuthor here. Thanks for the kind comment, happy to see that other people and not just myself got something out of this exercise.