Personally, when little things like that piss me off, I find it more helpful to introspect "why do I have such a strong emational reaction to this little thing?" than to go about laying moral judgement. I find this approach is especially good at promoting effective communication in places where it's easy to misinterpret intenions, like text.
- polymorphic lambda calculus: Lambda calculus with generics
- lazy evaluation: Well, lazy evaluation. Not sure how else to describe this
- algebraic data types: Again, how else to describe this? Put in a full description of what algebraic data types are?
- type classes: Haskell has type classes.
I really don't see what the problem is. If you're coming in to an article about dependent types, and you don't know what these things are, I think don't think the reasonable response is for the author to explain all of it to the reader. This isn't a beginner's introduction to Haskell.
...
and being happy that it then can run at 450 fps on a desktop computer with non-negligible manual optimization work https://www.youtube.com/watch?v=PXxwYYNZhU8
Haskell allows you to write fast code, it doesn't safeguard you from writing slow code.