> Go doesn't follow "you pay for what you use" model. To be fair, isn't that implied since Go uses a GC? The "pay for what you use" model is only really viable

> Go doesn't follow "you pay for what you use" model. To be fair, isn't that implied since Go uses a GC? The "pay for what you use" model is only really viable for languages that don't rely on a fixed GC runtime. (You could have "pluggable" GC libraries like the Boehm collector for C/C++, but those imply very different tradeoffs.)