←back to thread

Ergo: Erlang-inspired event driven actor framework in Go

(github.com)
175 points nateb2022 | 2 comments | 12 Sep 24 11:06 UTC | HN request time: 0.576s | source
Show context
nahuel0x ◴[12 Sep 24 16:56 UTC] No.41522944[source]▶
Three big differences in comparison with Erlang: 1- Cannot externally kill a process (yes, ergo process have a Kill method but the process will be in a "zombie" state until the current message handlers returns... maybe stuck forever) 2- No hot code reloading. 3- No per-process GC.
replies(4): >>41523113 #>>41523543 #>>41524544 #>>41525115 #
throwaway894345 ◴[12 Sep 24 17:50 UTC] No.41523543[source]▶
I've never written any Erlang before--why do I care about per-process GC?
replies(5): >>41523595 #>>41523906 #>>41523962 #>>41524224 #>>41527473 #
1. petejodo ◴[12 Sep 24 18:52 UTC] No.41524224[source]▶
One reason also is I believe it has something to do with fault tolerance even at a hardware level. A process has its data isolated somewhere in memory, if something happens to that memory, the process will crash next time it runs and starts causing supervisors to start attempting to recover the system
replies(1): >>41524297 #
2. hinkley ◴[12 Sep 24 18:59 UTC] No.41524297[source]▶
Forced decoupling between tasks is part of the deal here. Each task can fail separately because it only affects other tasks through messages.