11–20 of 41 posts
So what? If you don't use it as intended, it might not do what you want. Don't use it on unsupported niche operating systems.
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…
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.
Doesn't rust suffer from the same, way too wide dependency web? I feel like its an unfortunate consequence of having a good package manager which encourages proliferation of too many very small dependencies.
I'm really glad I got off that ride.
The April 2022 update at the end of the article has a good short summary: > If you're looking to reduce the whole discourse to "X vs Y", let it be "serde vs crossing your fingers and hoping user input is well-formed". It is one of the better reductions of the problem: it really is "specifying behavior that should be allowed (and rejecting everything else)" vs "manually checking that everything is fine in a thousand t…
The April 2022 update at the end of the article has a good short summary: > If you're looking to reduce the whole discourse to "X vs Y", let it be "serde vs crossing your fingers and hoping user input is well-formed". It is one of the better reductions of the problem: it really is "specifying behavior that should be allowed (and rejecting everything else)" vs "manually checking that everything is fine in a thousand t…
Doesn't rust suffer from the same, way too wide dependency web? I feel like its an unfortunate consequence of having a good package manager which encourages proliferation of too many very small dependencies.
[1] https://medium.com/@divan/how-to-complain-about-go-349013e06...
The April 2022 update at the end of the article has a good short summary: > If you're looking to reduce the whole discourse to "X vs Y", let it be "serde vs crossing your fingers and hoping user input is well-formed". It is one of the better reductions of the problem: it really is "specifying behavior that should be allowed (and rejecting everything else)" vs "manually checking that everything is fine in a thousand t…