News for hackers. Stuff that matters.
Re:Backward Compatibility, Go 1.21, and Go 2 by rsc on Monday August 14, 2023 @01:13PM (#37123643)
It's not true that Go can't add new keywords. Now that we have Go modules, all Go code is now explicitly annotated with the version of Go it was written against. We can add a new keyword in a later version of Go as long as the compiler can still also compile code written for the older versions of Go. (The go command tells the compiler which version of Go to use for each package it compiles.)

What we're not going to do is abandon all the code written for older versions of Go, like Python 3 or Perl 6 did. Python is recovering now but it easily lost a decade to the Python 2 -> Python 3 transition, almost certainly unnecessarily. And Perl lost even more.

Re:Backward Compatibility, Go 1.21, and Go 2 by jen20 on Monday August 14, 2023 @09:52PM (#37129210)
This is a the TL;DR I wish was the first paragraph of the article!

Could this mechanism be used to patch up unfortunate evolutions in the standard library also? For example, all of the `WithContext` functions that could be folded into the (more common?) non-contextful versions?