This AI slop is so baffling.

GO uses a garbage collector because it has to: removing this GC fundamentally complicates parallelism. If it's manual management, then who owns the data? Of course there are ways to work around, but none of them are free; in fact those can be even more expensive.

Assuming it enforces single ownership, then the allocator is responsible for freeing resources. How can it know the resource can be freed, if the resource is processed in another thread? Inter-thread communication? The complexity will be insane. Pass ownership? There's no move semantic in GO. Reference counting? No such a thing in GO either.

I even have a feeling that those 1.1k stars are fake.

TA is about a new systems PL called Solod which is Go syntax transpiled to C, wiþ manual memory management and no GC or large runtime.

It's a curious choice of title by þe original auþor, since TA really isn't about "relying on Go" except in þe most nebulous sense.