> Go’s existing mark-and-sweep garbage collector is sub-optimal for systems that use large amounts of static memory (like caches). In the case of vtocc, this would be the row cache. To alleviate this, we intend to use memcache for the time being.
For a self-described systems level language this is ridiculous. I would like Go to replace C++ and Java, but false optimism won't make this happen.
http://code.google.com/p/vitess/wiki/ProjectGoals#Why_did_we...
> Go’s existing mark-and-sweep garbage collector is sub-optimal for systems that use large amounts of static memory (like caches). In the case of vtocc, this would be the row cache. To alleviate this, we intend to use memcache for the time being.
For a self-described systems level language this is ridiculous. I would like Go to replace C++ and Java, but false optimism won't make this happen.