I understand that these two languages have a completely different design philosophy and can't be compared apple to apple. But purely from an industry adoption point of view which one is more likely to be the winner ?
Rust has two <i>huge</i> things going for it:<p>1. C-based lineage<p>2. Designed for industry use<p>Haskell has become the "nights and weekends" language. People are using it on pet projects outside of work and they're arguably becoming better programmers for having done so. Rust though is in the C family of languages, for which nearly every developer has familiarity, and was designed for larger project teams to collaborate and maintain large projects. Add in Rust's memory management strategy and it's not requiring a VM (unlike Java/C#) so it runs fast in a Docker container and you have a winner.<p>To me a more interesting question to ask, because the answer isn't nearly as clear-cut, is whether Rust or Go will be used more in industry?
Oh, look there, my crystal ball's on the blink again...<p>My guess: Rust.<p>Why you should believe my guess: Rust seems to be growing faster than Haskell.<p>Why you should <i>not</i> believe my guess: I'm primarily in the embedded space, where Rust fits well with the problems I'm used to having to solve. Haskell? Not so much. This makes Rust appear much more generally useful to me, when it may only be more useful in my specific area.
That's hard to say. The biggest risk for Rust is that it'll get beaten by something better. The biggest for Haskell is that nobody wants to use it because lazy evaluation is bad.