Pauseless GC is a thing, and has been thoroughly studied for decades. It’s not even hard to implement. The problem is that a naive implementation of such a GC makes so many sacrifices in other areas—memory usage, throughput—that it’s undesirable in practice.
-
-
It's pretty clear you're subtweeting Go here. Care to elaborate more?
-
It’s not just Go I’m criticizing, but also attempts to carve out “GC-free” subsets of languages like what Unity is trying.
- 2 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.