One of the major focuses at Gophercon was on Go 2.0 being an _extremely_ incremental process. Go 1 development is planned to continue with backwards-compatible

One of the major focuses at Gophercon was on Go 2.0 being an _extremely_ incremental process. Go 1 development is planned to continue with backwards-compatible changes being incrementally added, and Russ Cox hoped Go 2.0 would happen when Go 1.n+1 would either: * have no changes to be made from Go 1.n other than backwards-incompatible ones, or * would have no backwards-incompatible changes at all. I get the feeling that the developers have learned a great deal about not making large breaking changes & segmenting the language.