Probably why the comment you replied to didn’t say that at all.

Removed by mod

There is definitely more overhead involved (mostly due to proton) but not as much as you might think. The Plasma session has no performance impact, because it isn’t running when you’re not in desktop mode. Being a “full Linix distro” really doesn’t affect the gaming performance.

Most gamers don’t specifically follow gaming news or keep up with all the latest scandals (of which there are too many to keep up with in any case), but they will notice if the nostalgia project they’ve been looking forward to is suddenly gone.

None of them are right. Two thirds are looking in the wrong direction and the males facial expression is the exact opposite of the original photo.

Imagine a tool that gives you a language in which you can describe the hardware resources you want from a cloud provider. Say you want multiple different classes of servers with different sets of firewall rules. Something like Terraform allows you to put that into a text-based form, make changes to it, re-run the tool and expect resources to be created, changed and destroyed to match what you wrote down.

The guidelines for Windows developers kinda suck tbh. Maybe it’s better these days, but plenty of weird legacy software behaviour can be blamed on MSDN.

And the ability to breathe.

Consoles are not universally sold at a loss. Among the notable exceptions is the Nintendo Switch…

This looks loke something stupid, but it doesn’t really look like KKK costumes. I could understand if your point is that even a vague resemblance might be in poor taste, but “closely resembling” seems like a stretch.

I wouldn’t recommend Docker for a production environment either, but there are plenty of container-based solutions that use OCI compatible images just fine and they are very widely used in production. Having said that, plenty of people run docker images in a homelab setting and they work fine. I don’t like running rootful containers under a system daemon, but calling it a giant mess doesn’t seem fair in my experience.

XML aims to be both human-readable and machine-readable, but manages neither. It’s only really worth it if you actually need the complexity or extensibility, otherwise it’s just a major pain to map XML structures to any sensible type representation. I’ve been forced to work with some of the protocols that people like to present as examples of good XML usage and I hate every single one of them.

Fuck YAML though. That spec is longer and more complex than any other markup language I know of and it doesn’t have a single fully compliant implementation.

If I may ask: how practical is monitoring / administering rootless quadlets? I’m running rootless podman containers via systemd for home use, but splitting the single rootless user into multiple has proven to be quite the pain.

I feel like this was a trend started by video game journalists in the first place.

It would certainly help if the GitHub code search wasn’t utter garbage.

Is there a source for these haughty, cackling archeologists making fun of hairdressers or is that just to manufacture some kind of underdog victory scenario?

With bluray rips, I don’t really see any way to avoid that unfortunately, unless someone else has already added the hashes for your release. Most people use it to scan their encoded releases, which will (in most cases) have already been added to AniDB by the release group. I’m a bit surprised though, that none of your rips are recognized. Have you checked the AniDB pages for your series to see if anyone uploaded hashes for bluray rips?

Grouping seasons into a series folder doesn’t work well in some cases, because that’s not the way they are released in Japan. A new season is (most of the time) effectively an entire new show entry. Show seasons are mostly a north american thing. No matter which software you use, there’s always going to be some minor issues if you group seasons into one entry.

Shoko compares a files ED2K hash against the AniDB database. The filename doesn’t matter for automatic detection. Have a look at the log to see if there are any issues. It’s entirely possible that AniDB just doesn’t have the hashes for the raw BluRay rip. In that case you can either manually link them in Shoko, connecting the AniDB episode id to the file hash, or create new file entries on AniDB with your specific hashes.

Shoko also has rate limits. The problem is that AniDB does rate limiting in an extremely stupid way for a UDP API and doesn’t even have the decency to define clear time limits.