3 ms·
What's the uptime, reliability and distribution story for Haskell? If I want to have three nodes sharing common state (either eventually consistent or using a
by dnautics 8y ago
What's the uptime, reliability and distribution story for Haskell? If I want to have three nodes sharing common state (either eventually consistent or using a consistency model like raft) how do I implement this with (X) Nines of uptime in Haskell? What's the process restart story for Haskell?
- truth_seeker 8y agoNitpicking won't help. I was comparing the probable features to be implemented and not Languages. I used the reference of Haskell just to make a point that "Immutable Abstraction can be backed by safe mutable implementations"
- dnautics 8y agothe point is that the data structures in erlang are chosen with abstractions necessary to support its features. "safe" for haskell is not the same as "safe" for erlang, and that why it's not easy to implement some of the things that are trivial in erlang, in haskell. Conversely, there are some things that are really safe in haskell (type safety and preventing process crashes) that you kind of have to add boilerplate to get confidence in erlang (or you just 'let it crash', which is a perfectly fine philosophy too). This is not saying that erlang is necessarily better, most of those problems have been "solved by kubernetes" anyways.