Lazy I/O is not especially popular. So I wouldn't really say it's a problem with Haskell since most Haskellers would use other solutions. And Haskell is cuttin

Lazy I/O is not especially popular. So I wouldn't really say it's a problem with Haskell since most Haskellers would use other solutions. And Haskell is cutting-edge in more ways than laziness so I don't think this is a big deal. It's _technically_ "why it exists" but in practice there's a variety of other reasons people pick Haskell nowadays besides laziness.