News for hackers. Stuff that matters.

A comment on Finding and Fixing a 50k Goroutine Leak That Nearly Killed Production. Parent comment

Re:Finding and Fixing a 50k Goroutine Leak That Nearly Kille... by cassonmars on Saturday January 17, 2026 @08:08AM (#46657781)
I had the same confusion reading this – what kind of go-based webservice framework can you discretely deploy new handlers without restarts/redeploys? Would be a really awesome thing to have!
[ Parent | on HN ]
Re:Finding and Fixing a 50k Goroutine Leak That Nearly Kille... by WJW on Saturday January 17, 2026 @08:21AM (#46657853)
TBH it sounds like it would be extremely against the whole "simplicity, even at high costs" philosophy the Golang people strive for. Deploying new handlers into a running web service seems much more like something the Erlang people would be interested in.

(and lo, the BEAM does indeed allow hot code reloads. I don't think this is commonly used in BEAM-based Erlang/Elixir web services though. Certainly the Gleam people don't seem to like hot reloads very much...)

[ Parent | on HN ]