That’s a reasonable position. Yea, I’ve haven’t been too happy with Apple either in terms of newer OSes not working on older hardware - usually for no reason other than to drive hardware upgrades.
> On Feb 3, 2023, at 12:33 PM, Ian Lance Taylor <i...@golang.org> wrote: > > On Fri, Feb 3, 2023 at 9:40 AM robert engels <reng...@ix.netcom.com> wrote: >> >> I’d like to understand this a bit better as well. I currently develop an OSX >> app using Xcode/Obj-C and it runs all the way back to 10.9 (I recently >> raised the requirement from 10.7). >> >> Is the restriction only that the Go tool chain needs 10.15, but the produced >> binaries will work on an earlier version? Because that seems reasonable. >> >> Or do I have to use an old version of Go to produce binaries that run on an >> old version of OSX? This seems highly restrictive and harkens to the days of >> M$ and the continual upgrade cycles that churned through resources. > > What dropping support means is that we no longer fix bugs that only > occur on unsupported releases, and we no longer run our tests on old > releases. That includes both running the Go tools, and running > programs produced by the Go tools. > > We don't go out of our way to cause Go to break on unsupported > releases. That said, there are occasionally cases where we change Go > to require APIs that are only available on newer releases. That has > happened on macOS in the sense that we no longer support 386 or arm at > all; we only support amd64 and arm64. I don't know offhand if there > have been other such cases for macOS (there have been for Linux: for > example, we now require the accept4 system call to be supported > (except on arm)). > > Our position is that it is actually Apple that is driving the upgrade > cycle you mention, not us. Apple chose to drop support for High > Sierra back in 2020, so anybody running a High Sierra system connected > to the Internet is at risk. Should we invest our limited resources on > supporting releases that even Apple has declined to support? If Apple > continued to support High Sierra, so would we. > > Ian > > >>>> On Feb 3, 2023, at 11:34 AM, Ian Lance Taylor <i...@golang.org> wrote: >>> >>> On Fri, Feb 3, 2023 at 8:34 AM Jason E. Aten <j.e.a...@gmail.com> wrote: >>>> >>>> The Go 1.20 release notes say: >>>> >>>>> Go 1.20 is the last release that will run on macOS 10.13 High Sierra or >>>>> 10.14 Mojave. Go 1.21 will require macOS 10.15 Catalina or later. >>>> >>>> This is sad to hear, since High Sierra is the preferred (most stable) >>>> available mac operating system. >>>> >>>> Please consider continuing to support High Sierra in future Go versions. >>> >>> Our general guideline is that we stop supporting an operating system >>> when that operating system is itself no longer supported. According >>> to Wikipedia, Apple stopped supporting High Sierra in 2020, so >>> presumably people should be moving off it. It's also going to be >>> steadily harder for us to test it. What's the argument for us >>> continuing to support it? >>> >>> Ian >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "golang-nuts" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to golang-nuts+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/golang-nuts/CAOyqgcXUQLknkjw8Hk345bO6EazuEZcjKwvAw1AEEiCkz5OUwQ%40mail.gmail.com. >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/133B404A-283E-4060-956D-EFD3806556A5%40ix.netcom.com.
