miniblog.

In the tradition of “considered harmful” posts, this post’s title is intentionally misleading and designed to incite controversy — or at least grab your attention. Because of this, please take my exaggerations in this article for what they are :) In following tradition I will try to leave as many quotes and soundbytes as possible that can be easily taken terribly out of context and twisted. Anyways, I don’t mean that this “IO Monad” is something to be avoid. In fact, there’s a lot I rather like about it. What I mean is that the phrase “IO Monad”…it’s got to go. It has its usages, but 99.9% of times it is used, it is used improperly, with much damaging effects. So let’s go ahead with stopping this nonsense once and for all, okay? So I’ll say it here: The phrase “IO monad” considered harmful. Please do not use it. In most circumstances, an IO action of an IO type is the more helpful and more correct answer. I’m going to say that this is probably the single most harmful and damaging thing in Haskell and the community, with regards to pedagogy, practice, public perception, and kittens. Not even kidding. It’s actually literally the worst and everyone in the world is worse off every time someone says it. Not only is this a problem in and of itself, but it is at the core root of 90% (+/- 80%) of Haskell’s problems.

A better Emacs *help* buffer. Contribute to Wilfred/helpful development by creating an account on GitHub.

I have been using the open source Twitter competitor for almost a year, and I love it.

A mode for instant JavaScript eval in Emacs. Contribute to pandeiro/livid-mode development by creating an account on GitHub.