The tradeoff Go made is the wrong one for most applications. That’s the issue.
Then it sounds like we agree that concurrent generational GC is the way to go!
-
-
As long as all your global and per-thread pauses are sub-100-microseconds, sure. I don't personally have much need for generational though I agree there are some programs that need it. I certainly don't think Go is broken for putting it off.
-
Go isn’t broken for putting it off, but it’s probably not the choice I would have made. Anyway, I wouldn’t have as much of an issue if the blog post announcing Go’s GC didn’t throw shade at “’enterprise’” garbage collectors, as if Go had discovered something new.
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.