←back to thread

Ergo: Erlang-inspired event driven actor framework in Go

(github.com)
175 points nateb2022 | 1 comments | 12 Sep 24 11:06 UTC | HN request time: 0.204s | 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 #
throwawaymaths ◴[12 Sep 24 20:22 UTC] No.41525115[source]▶
Most beam developers will tell you they don't use hot code reloading, but if you're an elixir/phoenix (especially live view) you are using hot code reloading affordances in dev, though it's not the full suite of capabilities
replies(2): >>41526935 #>>41535763 #
1. hosh ◴[13 Sep 24 00:04 UTC] No.41526935[source]▶
I have used a portion of that capabilities for live debugging on prod machines to test things out before putting it through source code and using the regular CI/CD for deployment. However, the CD deployment does not rely on hot reloading because it hasn't been necessary.

On Kubernetes, running with regular pods it was not desirable. Maybe if we were deploying with StatefulStates.