Filesystem fetishization at its finest. Not only is /etc poorly structured (just like portions of the registry are), it also suffers from lack of uniform format for the data. But hey, registry is bad because it's bad.
They aren't just passing by. There's an ongoing fight for the control over this terrain. And, in the unlikely event of Russian troops retreating, I wouldn't put past Russia bombing it.
Unsurprisingly the majority of comments here focus on "how to prevent my free dependencies from breaking" instead of "can we have a systemic way of supporting developers that maintain critical software".
Both-Sides-Ism is such a tiresome stance. Yes, PO fucked up on their way out but that in no way justifies PiS actions, not does it even explain them. They'd dismantle democracy with or without PO's unlawful judgment. It's dishonest to claim otherwise.
This doesn't scale though, and OpenBSD - as much as I love it - is a clear example of that. Compare Theo who remains abrasive at times, and Linus, who realized that project the size of Linux cannot be handled with complete disregard for safe, inviting environment. Toxic leaders are the reason there's this idea that projects that are built on merit somehow must be ruthless and uninviting. It's really easy to e.g. confuse critique and criticism and in result give project the "avoid whenever possible" badge.
There are always types of events that are not suitable for public discourse (pretty much any form of harassment or abuse, where victims are still subject to pressure or were yet unable to process what happened falls into this category). I have no insight into what happened but it's not hard for me to imagine what could prompt moderation team to resign w/o disclosing specific instances.
Other tools can do that too. The thing that keeps me on VS is muscle memory. And I'm fine with that. But that doesn't mean that there's no entire different world out there that's viable. :)
Accessibility of that blog is absolutely abysmal. I read the post thinking "cool, too bad you have no contributor list easily available" but the problem is that links are no-underline white, just like the text itself.
At the very least a bespoke engine will deal with state management, data loading and saving, audio, gameplay systems and probably AI. I'd even argue that these are more of a focus in indie games than rendering is.
That's not the point. You've got code responsible for audio, asset loading and streaming (which tends to be ad-hoc in "engines" that focus on rendering), UI, state loading and saving, visibility query DB, nav meshes, and a lot of system and gameplay logic further divided into unique modules (character management, damage management, etc.) Yes, editor is a must these days (and has been for over 20 years) but that's not the point DeathArrow was making.
This text starts with the wrong (and outdated) assumption that animals are owned. If your motivation is to OWN an animal, then sure, I'm totally against it. Especially if you shop for a dog or a cat that looks good in your surroundings.
Taking care of rescue dogs and cats, improving their living conditions and integrating them into family on the other hand is absolutely fine if done responsibly.
This means that you have to take animal's behavioral tendencies into account. Many rescue dogs experience separation anxiety so if you can't devote enough time to help them overcome that problem, adopt an animal with confirmed, friendly disposition. Shelters should let you know which animals are a good fit for your lifestyle (and in some cases the answer can be "none").
In female cats and dogs neutering eliminates the risk of pyomyxia. The risk in females that have never gave birth is extremely high and consequences of delayed action when it happens are fatal (not to mention that cost of surgery may be prohibitive for many; it's orders of magnitude more expensive than neutering).
For male cats neutering reduces territorial spraying (urinating in order to mark your space; the smell of the urine is also much stronger if ca isn't neutered).