And “nothing” does not fit, either.

Attempted electrical substation sabotage is an easy way to fix your loneliness forever. And also all of your other problems.

After googling around for a bit, and then switching to duckduckgo instead (Google becomes aggressively unhelpful as soon as you have words like “ejaculated” in your query. Duckduckgo does the same thing, just not quite so much.), it seems the book in question might be “The tenant of Wildfell Hall” by Emily Brontë.

und ich hab nichts gesagt.

Going by what OP thinks “Chaotic Evil” means for sysadmins, they have clearly never heard of BOFH.

Writing good comments is an art form, and beginner programmers often struggle with it. They know comments mostly from their text books, where the comments explain what is happening to someone who doesn’t yet know programming, and nobody has told them yet that that is not at all a useful commenting style outside of education. So that’s how they use them. It usually ends up making the code harder to read, not easier.

Later on, programmers will need to learn a few rules about comments, like:

• Assume that whoever reads your code knows the programming language, the platform and the problem domain at least in general terms. You are not writing a teaching aid, you are writing presumably useful software.
• Don’t comment the obvious. (Aside from documentation comments for function/method/class signatures)
• Don’t comment what a line is doing. Instead, write your code, especially names for variables, constants, classes, functions, methods and so on, so that they produce talking code that needs no comments. Reserve the “what” style comments for where that just isn’t possible.
• Do comment the why. Tell the reader about your intentions and about big-picture issues. If an if-statement is hard to parse, write a corresponding if clause in plain English on top of it.
• In some cases, comment the “why not”, to keep maintenance programmers from falling in the same trap you already found.

I have been sort of following Wayland’s development for over 10 years now. I have been using Wayland for over 2 years now. I have been reading and watching various lengthy arguments online for and against it. I still don’t feel like I actually know it even is, not beyond some handwavey superficialities. Definitely not to the extent and depth I could understand what X11 was and how to actually work with it, troubleshoot it when necessary and achieve something slightly unusual with it. I feel like, these days, you are either getting superficial marketing materials, ELI5 approaches that seem to be suited at best to pacify a nosy child without giving them anything to actually work with, or reference manuals full of unexplained jargon for people who already know how it works and just need to look up some details now and then…

Maybe I’m getting old. I used to like Linux because I could actually understand what was going on…

The KDE team has already determined that this is not a bug and that both you and me must just be imagining it:

https://bugs.kde.org/show_bug.cgi?id=481058

Aw, too bad, they were working so hard on bankrupting themselves in defiance of that endless money cheat code they’ve got…

Honestly, this should be a bigger discussion, and not limited to just games. If a software company sells a software license for perpetual use to someone, they should not be allowed to use copy protection mechanisms that prevent the licensee from using it in perpetuity.

If there’s some other technical reason why the software won’t run any more after ten or twenty years, that’s another story. But if they just can’t be bothered to keep running the licensing servers, then they need to bloody well remove the stinking copy protection.

The biggest credit scoring institution in the USA.

Not very easily. Concise, easy to understand and correct explanations of how modern money (arguably since 1971) works are not easy to come by, and also the system just is a bit weird and counter intuitive. (Concise, easy to understand, but wrong explanations are, of course, all over the place. Almost everybody thinks they know how money works. Almost nobody actually does.)

One source that explains some of it would be “Debt: The first 5000 years” by David Graeber, but a) it’s a fairly lengthy book with quite a lot of historical background and b) it has a fairly strong politicial spin to it.

National debt is basically where money comes from in the first place. Unless you are willing to change the most fundamental, basic nature of how modern money even works, you cannot run a (major) country without debt. It’s not even just a question of good or bad fiscal policy, it is literally mathematically impossible.

It’s a lot better than the system that just randomly throws in your USB drives with your SCSI/SAS/SATA/PATA drives. Or the systems that calls everything a SCSI drive when it usually isn’t a SCSI drive.

Floating Point Unit. The thing that does mathematical operations on floating point numbers. It used come separately from the CPU as an add-on chip, but around the 486 era, manufacturers started integrating it on the same die as the CPU. Of course, as these things go, from the system programmers point of view, there is still no difference between an add-on FPU and an integrated one.

The one pictured here is an add-on FPU for an Intel 80386 CPU.

Ist der Ruf erst ruiniert, lebt es sich ganz ungeniert.

As someone who is in tech… not sure, either.

But this is about companies, not products or brand names.

WhatsApp is not its own company, it belongs to Facebook/Meta.

Also, on that topic, you could do the same thing you did with X/Twitter to Meta/Facebook.

*edit: Oh, and of course Alphabet/Google. Curious how many big tech companies seem keen on obfuscating their own name these days…

Smartctl works on nvme drives. Use it.