interolivary

I can recommend Kagi. Yes, it'll cost you to use it (but not a lot, eg. I'm on the $10/month plan), but people expecting to get everything for free online is what got us into this mess in the first place.

I live in an area with a lot of Russian immigrants, many of them fairly recent (likely moved because they didn't want to get drafted), and I wish I could say I was surprised by this behavior. Vatniks are violently belligerent

Chase that ivermectin down with a nice bleach martini

No no, you don't understand: the rules only apply to plebs like you and me. Corporations and their rich executives are free to do anything they want

For me, the whole point of paying for streaming was so that I could support the film makers without dealing with ads.

That doesn't sound profitable. How about artists and content creators only getting 0.1% of the profits and you have to watch ads? That sounds like it'd make the executives much richer.

Joke's on you: I don't consider myself a real programmer either

It's like with famines: globally we produce more than enough food to feed everyone, we just choose not to.

Our problem isn't the production of goods, but the allocation.

Sounds like sorcery

Go does have generics nowadays, although they have some limitations (like pointer types being inefficient because reasons).

But yeah I'd tend to agree. Go's strength and explicit design goal is that it's relatively easy to learn and get started with, meaning it's fast to onboard new devs. It's very much a "get shit done" language.

It's weakness is – to paraphrase someone criticism of Go – the core dev team's extreme unwillingness to adopt any programming language and tool chain designs and patterns invented after the 70's. Pike's rationale against generics was that in cases where you'd normally reach for generics you can either use interfaces (and especially interface{} which is like Go's void* and throws all type information out the window and is slower than proper types because reasons), or just copy and paste code. Because what you as a developer want to do is reimplement something like Find(needle SomeType, haystack []SomeType) for the Nth time in every project, or take a performance hit and lose all type information by using interface{}.

And don't even get me started on how long it took for Go to get proper dependency management and what the arguments against it were, Jesus fuck.

Go is currently the language I'm most fluent in after having written mostly Go for something like 8 years or even more (I remember when error was Error, pre 1.0 I think) and the one I'd be the most productive in, which is sort of unfortunate since I really don't like it as a language 😁 Learning Julia at the moment though, since I'm going back to the university to study some more computer science and maybe get into evolutionary algorithm research, and Julia is a neat language for lots of different number crunch-y tasks (no I won't touch Python, significant whitespace is a crime against common sense and fully dynamic typing gives me the heebie jeebies)