What do you learn from not using Erlang?
summary
After 15 years on Erlang and a year writing Go, the main losses are Erlang-style stack traces, hot code reloading, an interactive shell and OTP project layout that makes 100-file apps readable; extra cognitive load comes from Go’s pass-by-value/reference quirks. The clear wins are package.go.dev discoverability, small ergonomics like defer, context for request-wide timeouts, and struct tags; tooling proves roughly on par and Go’s ecosystem has more batteries-included libraries. Recommendation: unify cross-referenced docs, ship more ready-to-use apps, and target a niche (example: Fenix)—currently building Aro’s sovereign European cloud in Go.
AI-written summary · about
chapters (8)
- 0:00Introduction and transition
- 1:56Erlang features I miss in Go
- 7:44Discovering Go's tooling
- 10:35Useful Go language features
- 12:32Reflections on Go libraries
- 15:00Lessons for Erlang newcomers
- 17:47Future for Erlang ecosystem
- 20:36Questions and answers
related talks
42mErlang from the Outside
46mRediscovering Go
36mGo for the Rubyist
39mUsing Nicer Programming Languages at Work
05mMaking the Leap from NodeJS to Go
21m5 things I love (or why you should learn Go)
47mDevelop Your Embedded Applications Faster: Comparing C and Golang
29mThink Pragmatically: Elevating Your Go Development Skills