There's a bit of handwaving in the introduction concerning the garbage collector. There's a compiler option to turn it off allowing you to manually manage memory, but what if libraries you're using aren't all written to manually clean up after themselves? It seems to me that one of two things will happen:
1. Not everybody in the community manually manages their memory, making the --gc=none option impossible to use in practice.
2. Everybody is required to manually manage their memory so that others can gc off, effectively making the memory management mandatory.
So unless there's something more to this it seems like it's really just punting the gc decision to the community and creating confusion and uncertainty.
Can anybody with more knowledge maybe clear this up?