Yeah, I read that like everyone else. I understand what a generational collector is. The problem with your argument, I think, is that there are much more popular languages with similarly dumb GCs that Go outperforms.
I agree that’s interesting, but how many customers have that situation? :) (I don’t see how that’s incompatible with generational GC anyway. TLABs are pretty awesome.)
-
-
Right! I'm not considering the Go team work on that, they can't keep up with today's customer demands. I was letting myself be theoretical for a moment. It concerns me because I think we are heading that way, and it may require fundamental changes to the way I program.
-
I also agree that solutions may be compatible with generational GC. But it is a problem that may require putting a lot of fundamental assumptions up for consideration. If something made me start writing non-GCed code again on computers with separate DRAM chips, that would be why.
- 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.