I suspect that GC'd languages could mitigate this problem by introducing regions; separate areas of memory that cannot point at each other. Pony actors [0] have them, and Cone [1] and Vale [2] are trying new things with them.

If golang had this, then it might not ever need to run its GC because it could just fire up a new region for every request. The request will likely end and blast away its memory before it needs to collect, or it could choose to collect only when that particular goroutine/region is blocked.

Extra benefit: if there's an error in one region, we can blast it away and the rest of the program continues!

[0] https://tutorial.ponylang.io/types/actors.html#concurrent

[1] https://cone.jondgoodwin.com/fast.html

[2] https://verdagon.dev/blog/seamless-fearless-structured-concu...