3 ms·

I would add that I/O in Haskell is pretty sub-optimal, so that hinders its adoption. But I feel you in that I'm an average-ish developer, and I write Rust with

I would add that I/O in Haskell is pretty sub-optimal, so that hinders its adoption. But I feel you in that I'm an average-ish developer, and I write Rust with a constant fear that I'm "doing it the dumb/noob/wrong way". For example, maybe I just want to write a print method for an object, but I know the Right Way is to impl Display, so I do that so I won't be ridiculed.

xedrac 4y ago
When you say I/O in Haskell is sub-optimal, are you referring to performance, or the fact that it can be cumbersome? I personally love that Haskell's type system tells you whether a function has any side effects, which of course includes I/O.