←back to thread

Ergo: Erlang-inspired event driven actor framework in Go

(github.com)
175 points nateb2022 | 3 comments | 12 Sep 24 11:06 UTC | HN request time: 0.658s | 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 #
1. didip ◴[12 Sep 24 17:13 UTC] No.41523113[source]▶
(Not affiliated with Ergo) I have been watching Ergo repo for a while now and you wrote my observation concisely.

A while back, I tried to solve no.2 on your list by having a dynamically expanding and shrinking go-routines. POC here: https://github.com/didip/laborunion. It is meant to be used in-conjunction with config library & application object that's update-able over the wire. This idea is good enough to hot-reload a small IoT/metrics agent, but I never got around to truly solve the problem completely.

replies(1): >>41524133 #
2. mportela ◴[12 Sep 24 18:42 UTC] No.41524133[source]▶
Great project name, though
replies(1): >>41539654 #
3. justinclift ◴[14 Sep 24 13:25 UTC] No.41539654[source]▶
That could be another way to have AWS not poach a popular Open Source project. Name it something extremely pro-unionisation, such that every time they write the name they'd be reminding their developers that unions exist. :)