I am going to disagree with this simply because it's talking about the stack, not the language. As a Haskell developer who uses a much more complex stack than

I am going to disagree with this simply because it's talking about the stack, not the language. As a Haskell developer who uses a much more complex stack than provided in the article, and seen too many "there aren't enough basic Haskell web stack tutorials!" posts here and there, I would say the library choices here fit that bill perfectly. That said, once the adventerous non-Haskell user builds a basic application using this stack, they will then run into the brick wall of using a language which you are calling "complex", I would argue "different", and realizing there are a lot of new things they need to learn to actually be productive in it.