I have created and maintain a 130k SLOC Go codebase over the last four years or so, and there are a number of things about Go that irritate the shit out of me. I still get bitten by taking the address of a loop temporary on a surprising basis, for example, even though I am acutely aware of the issue. Or, I haven't really found any use for generics yet, because (as best I can tell) it's impossible to specialise and pr…
> 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 th…
Interestingly enough, C of all languages had enough sense to not require permissions as an argument for fopen(3).