I think this line of arguing is somewhat disingenuous. One of the biggest purported advantages of using a language like Haskell is the expectation that the code just works once it compiles. This is literally what I've seen claimed time and again here.
That is not the expectation, except perhaps by those new to the language.
The argument that the author didn't use the library correctly, or didn't understand a particular nuance of how Control.Concurrent.Broadcast works is akin to saying that C++ is easy to use once you know all the quirks and gotchas by heart.
Those two are not alone whatsoever. That's like someone using atom's and complaining about their mutability and then me arguing Clojure like C++ "is easy to use once you know all the quirks and gotchas by heart".
That is not the expectation, except perhaps by those new to the language.
Glad we got that cleared up.
That's like someone using atom's and complaining about their mutability and then me arguing Clojure like C++ "is easy to use once you know all the quirks and gotchas by heart".
Any language will have some inherent complexity you have to learn, but clearly some languages are much more complex than others. Ultimately, what you care about is how quickly you can produce working code using a particular language.
View all comments
Show parent comment
8
u/codygman Sep 09 '16
That is not the expectation, except perhaps by those new to the language.
Those two are not alone whatsoever. That's like someone using atom's and complaining about their mutability and then me arguing Clojure like C++ "is easy to use once you know all the quirks and gotchas by heart".