305 karma · joined December 6, 2012
Not sure what issues you ran into, but this isn't necessarily a bad thing. I had a similar experience with Elixir, where some libraries had been last touched two years ago, but did the job with no issues whatsoever.
Though it's true that Haskell is easy to put you into a mindset where you want to simplify and generalize the code as much as possible, leading to wasted time on overly general solutions. Which shouldn't be the case, because e.g. if you want to extend the solution from lists to traversables, Haskell gives you the confidence to safely refactor the method at a later time.
Also, I don't see how "let's not make a thing better just because it was not meant to work this way" is an argument.
I'm sure there is a fallacy name for this, but consider some other examples: "You could always use fridges for cooling and let cars be" or "You could always use computers for browsing the internet and leave phones be".
IMO, any resource like the one in the OP is going to get bashed ("not the way I would learn stuff"). Might as well learn something from it.
While this is not exactly what you are talking about, I think it demonstrates that node.js streams can do that too.
var hello = function() {document.write("Hello World")}; hello();
while the javascript is the equivalent of document.write "Hello World" [str(x) for x in array]
Do this: map(str, array)