Backward Compatibility, Go 1.21, and Go 2 - eviltoast

Boring is good. Boring is stable. Boring means being able to focus on your work, not on what’s different about Go. This post is about the important work we shipped in Go 1.21 to keep Go boring.

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.

  • nebiros@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    well, boring tech link is about battle tested tech, not about hype, so, in that sense, yeah, seems “boring” to me, but I love it, :)