Re:Backward Compatibility, Go 1.21, and Go 2
by tmpz22 on Monday August 14, 2023 @01:42PM
(#37124047)
> We could at any point during the transition decide that now we are Go 2, which might be good marketing.
Among the (entirely?) dev-oriented consumers of Golang would the shininess of "2.0" really outweigh the "ugh documentation is going to get harder to find" and "ugh I now need to increase my auditing of dependencies" and other similar fatigue?
Among the (entirely?) dev-oriented consumers of Golang would the shininess of "2.0" really outweigh the "ugh documentation is going to get harder to find" and "ugh I now need to increase my auditing of dependencies" and other similar fatigue?
Is Google universally good at marketing?