4 ms·
There's several reasons, one of the simplest (but not the most trivial) being that I can't share code between the client and the server. For example, data valid
by david-given 10y ago
There's several reasons, one of the simplest (but not the most trivial) being that I can't share code between the client and the server. For example, data validation. I did a tonne of programming on GWT back in the day, and this was something it actually did well.
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.
- platz 10y ago> 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.
- deleted 10y ago[deleted]
- bbcbasic 10y ago> Haskell is not Elm A service isn't a client though. They work in different ways and solve problems differently
- phamilton 10y agoThey 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.
- bbcbasic 10y agoYes true. There is the option of ghcjs on the front end, so you can do both in Haskell. And ghcjs is very close to cbc. I think it even emulates the threading model.