I concede that Go’s ideas about generics didn’t catch on outside that particular community. (I’m glad they didn’t!) Exceptions, userspace threading, GC, etc. are another story.
If you had a properly architected generational GC, you’d sacrifice a *tiny* amount of latency for huge throughput gains. Bump allocation in the nursery is such a huge benefit it’s virtually never worth throwing it away. That’s why Azul’s ultra-low-latency GC is generational.
-
-
Azul and Baker (who sat a few desks away from me in NYC) have discussed these issues with them. I'm sure you've heard the escape analysis argument, but that's why bump allocation is lower priority. It's still on the list, gri@ complained about it in a dart comparison years ago.
-
Then it sounds like we agree that concurrent generational GC is the way to go!
- 7 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.