>>175
It doesn't even support long lived processes on 32 bit, the GC runs out of memory in no time since it can't tell the difference between a value and a pointer.
They need a conservative GC so they can do pointer arithmetic. Go was designed as a systems language, after all. What's that I hear? Go doesn't have pointer arithmetic? They released Go ``1.0'' with a broken GC because they couldn't be bothered to write one that keeps track of pointers? It sure shows how much Google cares about their new language.