@p@fsebugoutzone.org
I've just given up on Go at this point — not only the implementation, but the language itself keeps changing too fast, with Rust no one promised something stable and even Rust isn't that bad. God knows, I tried keeping up with it — 32-bit PowerPC is no longer supported, but I've built the latest version of gcc-go that works on the machine this instance is hosted on, which is Go 1.10. I've backported Bloat to it and it works fine on this machine, but beyond it — backporting is too much effort.
And it's not about essential things, it's no longer the language that "Go Programming Language" book is about, it's something else entirely. Like "Ya-ay, let's re-do iterators" — and no, some internal unification in the standard library does not sound like a good enough justification to me. But Go community seems to like it that way, go to HNews and you'll see articles like "I redid everything with new iterators so now you can't build my module with older toolchain". WTF did you do that for, just because you could?
And it seems a lot of people weren't keeping up, so they have added an option to add a line to go.mod that forces a particular version of toolchain which… gets downloaded from the Internet — just like that. No, Google, it's not supposed to work like that, so fuck you! Just fuck you!
In a lot of environments you can't do things like that and I can't do it like that because you have dropped support for the machines I want to run my tiny piece of software on. I'm not a corporate samurai, who builds only for the latest Intel and 64-bit ARM, hoping that it might also work on something else. So I'm out!

Go 1.20 might seem chosen almost arbitrarily, but it can build all the software in Go that I still use. I'm not relying on any other software in Go and not using it for my personal needs because it's cancer — Google has killed it for me.

@jae@fsebugoutzone.org @TeaTootler@poa.st