The State of Go: Where we are in February 2016
At work (Lytics) 100% of our backend code has been in Go since the beginning over 3 years ago, so slide #6 highlights one of the most things with nearly every Go release:<p>&gt; Changes to the language: None<p><a href="https:&#x2F;&#x2F;talks.golang.org&#x2F;2016&#x2F;state-of-go.slide#6" rel="nofollow">https:&#x2F;&#x2F;talks.golang.org&#x2F;2016&#x2F;state-of-go.slide#6</a><p>We generally get our entire stack upgraded to the latest release within 1-3 months with little effort. It wouldn&#x27;t be much more work to be ready to upgrade on release day, but we haven&#x27;t found a reason to worry about it.<p>Go is such a breath of fresh air compared to past Java and Python jobs where production was usually at least a major release version behind the latest and there was extra effort spent getting everyone using the same implementation (Oracle Java v OpenJDK or Ubuntu&#x27;s Python v CentOS&#x27;s -- there are differences!).<p>Conservative releases aren&#x27;t a must-have for a language, but I do appreciate having one less operational headache to consider.