This is x86 assembler. (Actually, looking at the register names, it’s probably x86_64. On old school x86, they were named something like al, ah (8 bit), ax (16 bit), or eax (32 bit).) Back in the old days, when you pressed a key on the keyboard, the keyboard controller would generate a hardware interrupt, which, unless masked, would immediately make the CPU jump to a registered interrupt handler, interrupting whatever else it was doing at the point. That interrupt handler would then usually save all registers on the stack, communicate with the keyboard controller to figure out what exactly happened, react to that, restore the old registers again and then jump back to where the CPU was before.

In modern times, USB keyboards are periodically actively polled instead.

Non-murder solution:

Place and hold the apples precisely on top of one another. (Make sure your fingers are not in the way.) From one side of the apple tower, go horizontally exactly two thirds of the way to the other side. At that position, cut vertically through both apples from top to bottom. You now have two pieces that are two thirds of an apple each, and two pieces that are one third each. The kid you like best will receive the end slices without the apple core in it.

More realistically, disregard the stupid premise and make as many cuts as you need.

Files and directories starting with a dot are hiden by default. You are aksing for this stuff if you manually unhide them.

I don’t like the interrobang. It looks too crowded, and the sharp angle created between the question mark and the exclamation mark looks out of place in among latin alphabet letters.

There’s that “I never vote because politicians do not care about the issues of people like me anyway” attitude again.

(Hint: They don’t care because your kind won’t vote anyway.)

It should be 8 Hz, but according to the question text, that would mean answer “A”, while according to the labels next to the answer options, it would be “B”, because they’re inconsistent.

Is that really a meme? Looks more like some random software QA failure. Is there a community for software gore or something?

I’ve gotten used to this. The posts where I write several paragraphs and go kinda in-depth on a topic, and even do some research in the background on to make sure I don’t talk complete nonsese routinely get no upvotes at all. The ones that rise to the top are snippy one-liner remarks that get a cheap laugh out of people, but honestly don’t add anything of substance to the discussion.

IMHO, it was a mistake to make USB block storage use the same line of names also used for local hard disks. Sure, the block device drivers for USB mass storage internally hook into the SCSI subsystem to provide block level access, and that’s why the drives are called sd[something], but why should I as an end user have to care about that? A USB drive is very much not the same thing for me as a SCSI harddisk. A NVMe drive on the other hand, kinda sorta is, at least from a practical purpose point of view, yet NVMe drives get a completely different naming scheme.

That aside, suggest you use lsblk before dd.

It’s been pointed in several places already, but: That’s not the guy. The one in the surveillance camera footage had a jacket without these high front pockets.

Because after moving very slowly and steadily for just about forever, the other galaxies will suddenly make a jump of like ten thousandth of a degree.

Imagine the following:

You actually can stop the time by snapping you fingers, but it stops time for the entire universe, including yourself, with the exception of one single observer on some unimportant planet in the Andromeda galaxy. After 100 years from the POV of that observer, time resumes again.

Would you even be able to tell?

I can see it going both ways. Talking about execution times, this would be an exaggeration, but then, these memes always are.

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ë.

This is something that has been occasionally happening in Europe (at least in Germany, don’t know about France) for well over 10 years now. Probably more like 15.

What’s sorely needed at this point is much more storage to make this energy available when it is needed instead of when it isn’t. Before that happens, you cannot really decommission any gas or coal power plants, because you still need them during times of much less renewable production.

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.

In a language that has exceptions, there is no good reason to return bool here…