The borrow checker makes things a bit more complicated to get running, definitely takes some getting used to when you come from a non-memory safe language. But the compiler is really helpful throughout almost all mistakes, often directly providing an explanation and a suggested fix. One of my favorites programming experiences so far

Dwarf planets sometimes have moons (e.g. Pluto)

Just took a look on Nexus, and yeah… They’re down bad

Helix!

Not even the first time tofu has been used, I know it as the key validation scheme “trust on first use”

It’s less so the wider tech-industry, as in corporate big tech. But the general open-source community and hacker spaces in particular have a lot of trans and other queer people in it

Most numpy array functions already utilize multiple cores, because they’re optimized and written in C

The quote is not wrong, however, Elon is neither harmless nor peaceful. He’s dangerous and a violent fascist

What decade do you live in? It’s closer to 2-4x nowadays, and 2TB is nothing

1

‘bans’?

Oh yeah, of course.

that’s amazing! Aren’t codecs fun

Yeah I agree. Although recently I’ve become partial to toml… In the end I’ll use what’s common in the ecosystem I’m developing in

Nothing too major about how it’s usually used, but the yaml spec does allow arbitrary code execution when parsing a file and relies on the parser to have that feature disabled: https://en.m.wikipedia.org/wiki/YAML#Security

That’s why for python, yaml.save_load() is a thing. That’s fine for your local config files and may even be a feature for you, but it shouldn’t be used to exchange information between services.

I don’t buy it

a good approach to Ubisoft games