It's true that the abstraction got attention when they realized it solved the IO problem. (Before the IO type, IO in Haskell was painful.) It's quite possible it wouldn't have become a significant part of the ecosystem without the fact that it solved the IO problem neatly.
But solving the IO problem neatly is a consequence of the value of the abstraction. It solves it so well because of its useful properties.
I'd say you should take another crack at haskell sometime. But if you're learning Erlang now, stick with that for the time being. It's also got plenty to teach.
But solving the IO problem neatly is a consequence of the value of the abstraction. It solves it so well because of its useful properties.
I'd say you should take another crack at haskell sometime. But if you're learning Erlang now, stick with that for the time being. It's also got plenty to teach.