Comment by LPCRoy
12 years ago
This has nothing to do with Go. It sounds like a case of poorly managed dependencies and build rules and likely weak engineering. The fact that they wanted to support the iPad and chose Go also shows this wasn't well thought out.
I would say bad engineering:
* Go 1.0 had a terrible GC, especially on 32-bit platforms (their target platform)
* No manual memoray management (and unlikely to ever exist)
* Can't bind to C++, can't cross-compile cgo (gccgo can though)
Go is really cool, and I use it every day, but it doesn't make any sense for games, especially not for their target platform. Maybe in a few years the GC will be more reliable, but I wouldn't try to build a game in Go if I thought I might want to try to sell it.