[afavour]

> seems to be an extended complaint that Go isn't as portable between Linux and Windows as the author would like it to be

I don't think that's true. The author is using that lack of portability as an example of what they think is wrong with Go:

> And they're symptomatic of the problems with "the Go way" in general. The Go way is to half-ass things.

> The Go way is to patch things up until they sorta kinda work, in the name of simplicity.

And I get the point they're making. The issue isn't that file permissions don't work consistently cross-platform in Go, it's that they can't work consistently cross-platform in anything but rather than add complexity Go has papered over the cracks. If that's an acceptable approach in a core file API who knows how often it's employed elsewhere in the runtime? The following section the post shows this mindset as implemented in monotime and the many potential footguns the official implementation introduces.

[Joker_vD]

> The issue isn't that file permissions don't work consistently cross-platform in Go, it's that they can't work consistently cross-platform in anything but rather than add complexity Go has papered over the cracks.

Interestingly enough, C of all languages had enough sense to not require permissions as an argument for fopen(3).