That's an application (as is Docker, also built in Go), but the question was about internal Google services and... we don't know because company secrets, but it's likely on the rise as it was written as a replacement for C++ which was their previous main language for backend services alongside Java/Kotlin. One source with the charming name "assbuttass" [0] says all new services are written in Go, with a follow-up by "deathmaster99" saying only 10% of code is Go, but this was a year ago and even 10% at Google's scale probably represents tens of millions of LOC.

[0] https://www.reddit.com/r/golang/comments/1c9fhet/how_much_go...

Why would you type out how to prompt an AI instead of just link to the source or an article?

Save some energy, https://news.ycombinator.com/item?id=28401030

vector, galois field, 2 to the power of 8, affine transformation.

there's also the inverse: https://www.felixcloutier.com/x86/gf2p8affineinvqb

Good collectors are language independent. Bad collectors like Mark & Sweep are just needed for stable extern pointers, like in ffi callbacks.

All better languages use a modern copying collector, if they have enough memory. It's also compacting, and doesn't stop the world. I think lisps just do mark & sweep on phones or embedded, and the mentioned ffi callbacks.