That’s what I’m talking about. Go’s GC benchmarks well, but it is making the wrong tradeoffs. Throughput matters a lot.https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e …
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.
-
-
I just have to point out: that is not at all the argument you started with.
-
Well, I didn’t know Go was planning on generational GC! “golang generational gc” certainly doesn’t bring that up on Google.
- 3 more replies
New conversation -
-
-
I don't know the post you mean, but the only shade they could consider throwing is that a lot of big Java servers still have long pause tails. (Maybe not the JVM's fault, unless you blame hard-to-configure things for bad configs.) I am trying to avoid shade, but I'm a weak human.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.