That raises an obvious question: when should we expect the Go 2 specification that breaks old Go 1 programs?
The answer is never. Go 2, in the sense of breaking with the past and no longer compiling old programs, is never going to happen. Go 2 in the sense of being the major revision of Go 1 we started toward in 2017 has already happened.
There will not be a Go 2 that breaks Go 1 programs. Instead, we are going to double down on compatibility, which is far more valuable than any possible break with the past. In fact, we believe that prioritizing compatibility was the most important design decision we made for Go 1.
I’m not well-versed enough in either programming or the Go programming language, but this seems like good news for Go programmers.
Go Golang! Its a vibe as the kids say. I think the hype has died down a bit as rust as grabbed a lot of attention. But I think they each have their own use cases as do most programming languages. The less C the better.
That’s really great to hear. I don’t use Go, but I started learning and using Python right smack in the middle of the transition from 2 to 3 and it was such an uncomfortable mess.
drcouzelis,
Same! I started a python project and some components I needed/wanted were targeting 2 and others 3. New APIs had to be learned and the breakages were frustrating.
This is/was quite common for PHP as well.
That sounds cool! While I`m not using Go, I`ve been searching for language with good backward compability, so maybe I`ll look on this.