Earlier quoted context omitted.
While I don't agree with the general snarkiness towards Haskell of the commenter you are replying to, being lazy by default could be seen as Haskell original mistake. It was interesting from a research point of view though.
it's hard to call the sine qua non of a language a bad design decision. if it were, the language would be dead. haskell survives because it's a lazy purely functional language with some industry support. bad design decisions have to be something apart from that.
What set Haskell apart is how it successfully limited side effect to the IO type and the introduction of type classes.
Laziness by default is definitely a bad design choice as far as I'm concerned. The drawbacks are not worth it.