3 ms·
Yeah the linked issue (16570) is the most interesting one, with the Go runtime breaking multiple times in the runup to Sierra as Apple changed the ABI of the un
by masklinn 10y ago
Yeah the linked issue (16570) is the most interesting one, with the Go runtime breaking multiple times in the runup to Sierra as Apple changed the ABI of the underlying gettimeofday syscall.
- iainmerrick 10y agoWow, that seems like a really bad approach for Go to take. So is anybody actually using Go on OS X? I guess maybe not, if all the real Go deployments are on servers running Linux.
- zimpenfish 10y agoI do a bunch of development work using Go on OSX but I do deploy the resulting solutions on Linux.
- iainmerrick 10y agoAha, that's kind of what I'd figured. Work on Mac, deploy on Linux. It makes me think twice about e.g. using Go as part of the build workflow in a big project if it's going to randomly stop working on various OS X versions.