Or Garuda. Sure, the theme it applies to KDE by default is pretty garish but nothing keeps you from just going to System Settings and seeing a different theme. Other than that it’s basically just Arch with a bunch of stuff preinstalled and some convenience scripts.

I wish I was in that position. I never want to hear “good code is its own documentation” ever again.

Pool toy transformation is a whole thing. I don’t quite see the appeal either, although I can see it as a hybrid between latex kink (via the shiny and smooth “skin”) and doll kink (which in turn is related to D/s). It seems to be mostly a furry thing.

To be fair, it had its moments. Windows 95 was a pretty big step forwards and the alternative was OS/2 Warp, which has some nice features but was from IBM, who were still dreaming of replacing the PC with a vertically-integrated home computer again.

Windows 2000 (or XP starting with SP2) was also solid. 7 was alright. None of those had too much bullshit bundled with them.

Everything since Windows 8 has been some flavor of shitty, though.

Especially if you didn’t have a lot of spare time. With an active community you can just dip into discussions when you have the time. With a community you’re trying to establish yourself you absolutely have to provide a steady stream of content until it (hopefully) takes off.

The software development industry version of this is “we really need to fix that soon but it’s beyond the scope of this PBI”.

“Soon” is a shorthand for “we’ll put this on the backlog and never pull it into a sprint until it blows up in our faces, at which time we will gripe about how nobody bothered to fix it earlier”.

Exactly. If this was “Marathon: Return to Deimos” or “Marathon: Battleroid Arena” or even “Marathon Infinity Plus One” I wouldn’t complain. Much.

But just taking the name (and logo) of the original one? The game that started Bungie’s path towards being one of the big names of the FPS genre? That’s like saying they went straight from Pathways Into Darkness to Halo. That’s not honoring Marathon, it’s a soulless recycling of an old IP.

My vent cores feel distinctly unblasted.

We know that people have different chronotypes. We even know that most people of working age aren’t really morning people. Unfortunately, our business world assumes a standard circadian rhythm and is structured around getting up early because people needed to use every bit of daylight way back when. So that sucks, especially if you’re an evening or even night person.

Man, I hate it when they make new games that have exactly the same name as an older game by the same company. And this one’s not even a remake. I have no idea if Marathon (1994) and Marathon (upcoming) even play in the same universe but they don’t seem to have much in common gameplay-wise. Ugh.

Makes me wanna install M1A1 Aleph One (didn’t know it does M1 directly these days) and shoot some Pfhor, though.

There are many OS-related diseases. Many Linux users are affected by or at least know someone who suffers from the compulsive need to mention that they’re using Arch. Then there’s compiler flag addiction, which can develop in Gentoo users. iDependency, the pathological need to purchase any product Apple releases, has financially ruined many macOS users. Windows users’ feelings towards Windows Update and the associated increase in heart rate are known to substantially increase the risk of a fatal heart attack.

Knowing how to operate TempleOS is considered a mental disorder under the DSM-5.

I’d argue that unfun design elements can be useful in games if used with care and purpose. For instance, “suddenly all of the characters you’re attached to are dead” is not exactly fun but one of the Fire Emblem games used it to great dramatic effect at the midway point.

Of course the line between an event or mechanic that players love to hate and one they just hate is thin.

Hoo boy, you weren’t kidding. I find it amazing how quickly this went from “the kernel team is enforcing sanctions” to an an unfriendly abstract debate about the definition of liberalism. I shouldn’t, really, but I still am.

Oh yeah, the equation completely changes for the cloud. I’m only familiar with local usage where you can’t easily scale out of your resource constraints (and into budgetary ones). It’s certainly easier to pivot to a different vendor/ecosystem locally.

By the way, AMD does have one additional edge locally: They tend to put more RAM into consumer GPUs at a comparable price point – for example, the 7900 XTX competes with the 4080 on price but has as much memory as a 4090. In systems with one or few GPUs (like a hobbyist mixed-use machine) those few extra gigabytes can make a real difference. Of course this leads to a trade-off between Nvidia’s superior speed and AMD’s superior capacity.

These days ROCm support is more common than a few years ago so you’re no longer entirely dependent on CUDA for machine learning. (Although I wish fewer tools required non-CUDA users to manually install Torch in their venv because the auto-installer assumes CUDA. At least take a parameter or something if you don’t want to implement autodetection.)

Nvidia’s Linux drivers generally are a bit behind AMD’s; e.g. driver versions before 555 tended not to play well with Wayland.

Also, Nvidia’s drivers tend not to give any meaningful information in case of a problem. There’s typically just an error code for “the driver has crashed”, no matter what reason it crashed for.

Personal anecdote for the last one: I had a wonky 4080 and tracing the problem to the card took months because the log (both on Linux and Windows) didn’t contain error information beyond “something bad happened” and the behavior had dozens of possible causes, ranging from “the 4080 is unstable if you use XMP on some mainboards” over “some BIOS setting might need to be changed” and “sometimes the card doesn’t like a specific CPU/PSU/RAM/mainboard” to “it’s a manufacturing defect”.

Sure, manufacturing defects can happen to anyone; I can’t fault Nvidia for that. But the combination of useless logs and 4000-series cards having so many things they can possibly (but rarely) get hung up on made error diagnosis incredibly painful. I finally just bought a 7900 XTX instead. It’s slower but I like the driver better.

We used to have one: “Solang das deutsche Reich besteht wird jede Schraube rechts gedreht.” (“As long as the German Empire persists every screw is turned right.”)

Given that the German Empire failed spectacularly, this sentence isn’t very popular anymore.

Pretty much business as usual. Those things pop up every once in a while, which is why Germany has no shortage of experienced bomb disposal experts.

And yes, the fact that this is perfectly mundane is chilling if you think about it. That’s how intensely bombed areas work for decades. Battlefields don’t turn back to normal when the war is over. And we casually do this all over the world for a large number of usually stupid reasons.

I fix that problem by forgetting to turn off Do Not Disturb mode. Also works wonders for blocking all of the calls you do want to take.

They did PR campaigns against Linux and OpenOffice for quite some time – until cloud computing took off and it turned out they could earn more money by supporting Linux than by fighting it.

In fact, Microsoft weren’t happy about FOSS in general. I can still remember when they tried to make “shared source” a thing: They made their own ersatz OSI with its own set of licenses, some of which didn’t grant proper reuse rights – like only allowing you to use the source code to write Windows applications.

Nope, they just become less predictable. Which is why in some parts of Germany you can’t build as much as a garden shed without having EOD check the land first. In the more heavily-bombed areas it’s not unusual to hear on the radio that you’re to avoid downtown today between 10 and 12 because they’re disarming a 500-pound bomb they found during roadwork.

And yes, the fact that an unstable bomb capable of trashing a city block is mundane nicely illustrates war’s potential to fuck things up for generations.

Japan might want to get that land under and around the airport checked. There might be some other surprises hidden down there.

The main issue was that Vista asked for admin rights all the time. One of the first things they addressed with SP1 was to require admin privileges for fewer operations, cutting down on the number of UAC prompts.