3 ms·
None of those other systems have solid failure-domain oriented programming baked in. Let's say there's a netsplit and you want your connection to bring down tw
by dnautics 6y ago
None of those other systems have solid failure-domain oriented programming baked in. Let's say there's a netsplit and you want your connection to bring down two other processes that depend on it, self-heal when the netsplit is resolved, and not have any other resources associated with the process leak (memory, file descriptors, resource pools, database connections, etc). This is like maybe two lines of elixir/erlang.
- busterarm 6y agoAlso, error handling seems to be the worst part of working with Go by miles. I can't even imagine building such a system in the language.