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

The actual aluminium that people work with in actual real life are also alloys.

How about when they say “a phenomena”?

How is that supposed to remove lead and mercury from the food supply? If you use that as fertilizer, the heavy metals will still be in there, and likely get picked up by your crops…

“Squeezes”, “20%”. Interesting word choice. Feels almost like downplaying. When, in reality, 20% is massive, especially on a CPU like the Threadripper.

Generally yes, but what’s shown here isn’t, it only looks a bit like it if you ignore the clearly spelled out context.

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.

Funny thing: “Hello” was actually not a common greeting until that point.

Unlike with Neil DeGrasse Tyson, with Dawkins, I would be quite surprised if he brought that up without being quite specifically asked about it…

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

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

It’s getting increasingly carbonated, though…

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.

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…

“Horned Screamer”? Makes me wonder how that bird looks and sounds…