News for hackers. Stuff that matters.
Re:Go automatically downloads a newer toolchain if needed by IshKebab on Tuesday August 20, 2024 @10:57AM (#41300660)
Even in that case they did the behaviour change properly:

> To ensure backwards compatibility with existing code, the new semantics will only apply in packages contained in modules that declare go 1.22 or later in their go.mod files.

CMake and Rust and Android and lots of other systems have mechanisms like this that allow you to introduce opt-in breaking changes, but unsurprisingly Python doesn't. They just decided it was ok to start breaking backwards compatibility.

Re:Go automatically downloads a newer toolchain if needed by pjmlp on Tuesday August 20, 2024 @12:19PM (#41301406)
That doesn't apply to runtime and standard library changes.

Enough of them happened already, that a clarification post was needed,

https://go.dev/blog/compat

Re:Go automatically downloads a newer toolchain if needed by IshKebab on Tuesday August 20, 2024 @05:57PM (#41304518)
That's still among the strongest backwards compatibility guarantees in any major language. Maybe Java would be close? It's certainly better than C++ which is famed for backwards compatibility, and light years ahead of Python.
Re:Go automatically downloads a newer toolchain if needed by pjmlp on Wednesday August 21, 2024 @01:26AM (#41307029)
Yet it isn't without zero issues, as claimed.
Re:Go automatically downloads a newer toolchain if needed by tapirl on Wednesday August 21, 2024 @11:51AM (#41311422)
> That's still among the strongest backwards compatibility guarantees in any major language.

Not at all. See https://go101.org/blog/2024-03-01-for-loop-semantic-changes-... for reasons.

Re:Go automatically downloads a newer toolchain if needed by IshKebab on Thursday August 22, 2024 @08:21AM (#41319460)
What reasons? You need to pass one flag to the compiler to specify the language version? That's still very very good.

Please tell me what flag I can pass to Python 3.12 so `distutils` still exists.

Re:Go automatically downloads a newer toolchain if needed by tapirl on Thursday August 22, 2024 @09:03AM (#41319784)
Reasons are in the article.

I'm not familiar with Python, so I don't understand what is the problem with Python. But I think the problem of Go is unrelated to Python.

Re:Go automatically downloads a newer toolchain if needed by tapirl on Wednesday August 21, 2024 @11:48AM (#41311404)
> Even in that case they did the behaviour change properly:

Not in fact. Go core team has admitted that Go toolchain 1.22.n versions break backward compatibility: https://github.com/golang/go/issues/66092

There is another breakage case: https://github.com/golang/go/issues/66070 and the team leader doesn't plan to fix it.