You want to be arguing that Go’s GC is SUBOPTIMAL. But instead, you’re arguing that it’s INAPPROPRIATE. You’re going to lose that argument.
Well, I didn’t know Go was planning on generational GC! “golang generational gc” certainly doesn’t bring that up on Google.
-
-
You’re oscillating now. Go’s Gen GC, which for all we know might never get merged, is not relevant to the point I’m making. You started with “this is categorically bad” and ended with “it’s not the choice I would have made, but”
-
It’s categorically bad if Go refuses to implement generational GC at all. It’s not as bad if generational GC is a work in progress. I still don’t like the fact that the initial blog post seemed to be attacking other GCs (putting ‘enterprise’ in scare quotes even), but whatever.
- 1 more reply
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.