> Can't share code between client and server
The question was about using haskell on the back end. Also, previous attempts at sharing client and server code in other langs are sophmoric at best. In reality, there will always be a boundary that requires differences in front end and back end code.
> Haskell is not Elm
Doesn't answer the question, circular reasoning at best.
> Haskell is not Elm
A service isn't a client though. They work in different ways and solve problems differently
They also, sometimes, solve the same problem. (Cited example: data validation)
There's value in sharing code between client and server. It may not outway the costs, but there's definitely value in doing so.
Most of the other reasons boil down to Haskell not being Elm --- they work in different ways and solve problems differently. There's always going to be impedance mismatch between the two. (Do I solve this problem with monads or with state-mutation functions?) This is going to use up valuable problem-solving bandwidth which I'd rather spend making the project more awesome.