The author says it himself: > Haskell code sucks, therefore Haskell sucks.” No, poorly organized code sucks. If that code happens to be written in Haskell, don

The author says it himself: > Haskell code sucks, therefore Haskell sucks.” No, poorly organized code sucks. If that code happens to be written in Haskell, don’t shoot the messenger. Basically, yes. Not all callbacks are harmful. Not all goto's are harmful either; you can write both elegant and maintainable code using both. That is not that point. It's like saying you can write elegant and maintainable code in assembly. Yes you can (no, really. I've actually seen some. :P)... but tangibly in real world situation is that how it usually plays out? By tacitly (some might argue expressly even...) supporting callbacks, are these modern frameworks leading to in general an improvement in code quality or a drop in code quality, compared to the non-callback based code. That isn't an intangible. It's empirically measurable, and I'd love to see some code metrics off git hub that measured it. Waxing lyrical about how how callbacks can be used for the Forces of Good by Clever Programmers doesn't really impress me. So can auto-generated xsd -> C# code (I suppose) in the right circumstances. Less arm-chair talking on both sides please; back your assertion up with some data.