Thanks for the reply and confirmation—theoretical but we have had systems
fail this way before (including the system this codebase will eventually be
deployed on). Of course practically once that happens, the go process
leaking one more file descriptor is probably the least of our worries.
For com
On Fri, Feb 3, 2023 at 12:38 PM 'Lucas Christian' via golang-nuts
wrote:
>
> Apologies for reviving an old thread, but thought this might be the most
> efficient way to keep context.
>
> I'm looking at a similar issue Thomas encountered, but in this case I'm
> concerned about how to handle error
Apologies for reviving an old thread, but thought this might be the most
efficient way to keep context.
I'm looking at a similar issue Thomas encountered, but in this case I'm
concerned about how to handle errors returned from
StdoutPipe()/StderrPipe() and properly clean up after that. e.g.:
I have a Mid 2013 Macbook Pro that stopped being supported by MacOS several
releases ago.
I heard about OpenCore, which magically patches the installer for the
current release of MacOS
to run on older hardware. To my utter amazement, it works! I'm now running
the latest version
of MacOS Ventura
Good idea.
FYI - this is on a Fedora 37 6.1.8-200.fc37.x86_64 server with go version
go1.20 linux/amd64.
I'm running a VM in Virtualbox with snapshots so it's very easy to go back
to an unmodified
system after running an experiment. Note that I'm adding the '-a' option to
the go build commands
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 wrote:
>
> On Fri, Feb 3, 2023 at 9:40 AM robe
On Fri, Feb 3, 2023 at 9:42 AM Jason E. Aten wrote:
>
> Primarily the argument is that High Sierra is the most stable version of OSX,
> and thus preferred by those who highly value stability and reliability. It
> is also the only
> version supported on older hardware, such as my 2015 mac book pr
On Fri, Feb 3, 2023 at 9:40 AM robert engels 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 ne
Primarily the argument is that High Sierra is the most stable version of
OSX,
and thus preferred by those who highly value stability and reliability. It
is also the only
version supported on older hardware, such as my 2015 mac book pro. These
mac books
have superior keyboards and better access to
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 ve
On Fri, Feb 3, 2023 at 8:34 AM Jason E. Aten 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 (m
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 conti
12 matches
Mail list logo
