Honestly it annoys me how much the well has been poisoned with rust that we’re even talking about the language here. There is so much focus on rust that we’re not even talking about how they literally couldn’t tell the difference between their software crashing in production and a ddos attack.

They had no visibility into their runtime environment, and from my understanding of the Blogpost, didn’t even look into the possibility until the entire cluster went down from this bad config.

Like, even assuming they did input validation, what should the clickhouse services do when they’re fed an invalid config? I’d argue the only sensible thing would be to refuse to start. But it seems like crashing wasn’t being detected at all.

That might be true, but claiming that people only moved because they were propagandized into doing so by a for-profit company is absurd.

This is incredibly reductive and at best looking at mumble through Rose tinted glasses.

Mumble has had a rocky past as a useful piece of software and it’s absolutely not been a discord competitor any more than TeamSpeak is a discord competitor.

Maybe it’s changed recently, but mumble has not had the feature set that made discord useful in the first place.

Isolation has the connotation of a single thing or individual being… Isolated from the group. Atomization is meant to evoke a sense of the more widespread impact on society. After all, if something only impacts a small subset it’s considered… “Isolated”

That being said, atomization is definitely not a new term to describe this…

History and good explanations of what was changed and why is incredibly useful for being able to determine if something is a bug, a feature, and why something was written a particular way.

I’m not super stringent on commit style, but it absolutely helps to structure commit messages, especially in larger projects where they’re being worked on piecemeal.

2fa isn’t a panacea and won’t solve every problem. It does help though. Why do you think supply chain integrity isn’t something they care about?

Phoronix comments are always such a mixed bag. I get that something still running after 20 years is cool and all, but it’s not necessarily a good thing.

Personally, I usually take issue with the missing institutional knowledge on such projects. It doesn’t matter if it runs, it matters that we’re running something we can fix if it explodes.

I recently built some stuff with the latest gcc compiler that was written in c89, but still compiled. That’s pretty sweet and very convenient for us, but the flags and the commands aren’t documented at all. So we have to spelunk through ancient scripts to find the right incantations or worse, read the code. Because who needs docs for an internal tool ammirite?