I'm not sure if an opinion of this sort can really be wrong, but here's an attempt at an honest case: - If you're working with complex domain objects, Haskell

I'm not sure if an opinion of this sort can really be wrong, but here's an attempt at an honest case: - If you're working with complex domain objects, Haskell has somewhat better (edit: or at least more powerful) tools for forbidding invalid states during runtime and assisting refactors as your data model changes. - Haskell seems to have better libraries for writing parsers and compilers than Rust, if that's relevant to your project. - Some folks prefer ML syntax to Algol-like syntax. - The GC, immutable-by-default data, and reasonable concurrency model are pretty nice features of the GHC runtime. - The performance difference between Haskell and Rust probably doesn't matter for most projects. - Haskell might actually compile faster if you avoid crazy type-level programming shenanigans. - Haskell has a pretty decent REPL. Obviously, Rust has a different set of trade-offs, and the bigger cost to either is going to be that both are a bit off the beaten path and require some practice and experience to be productive and comfortable in.