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

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.

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.

You don't need "AI" for that. All you would need is some standardized APIs for the various shops, and you could easily solve this with computer technology from 20 years ago.

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.

About 20 years ago, Microsoft was found guilty and convicted, because they forced their browser on their users, driving out competitors by abusing their de facto monopoly on PC operating systems. These days, they are doing the exact same thing again, just on an even broader base. I don't even understand how this verdict took so long.

Also, almost all of that is written in C, which is a successor to B, which is a simplified version of the Basic Combined Programming Language. There was never an A.

The way I, as another European, understand this, he's flying an anti-oppression flag and a pro-oppression flag at the same time.

50 Euros a day is insane. That's a good portion of what I pay for a whole month.

I get the joke, but in contrast to heating, you can easily just... not run demanding games while the electricity is insanely expensive for a day.

Ever since Donald Trump was elected, I always had the impression that he just doesn't properly understand that being elected president is a fundamentally different thing from being crowned king.

AMD and nVidia on Windows: So your GPU is still very capable and useful for almost everything including most gaming tasks, but it's a couple years old and not making us money any more? Sucks to be you, have fun hunting for unmaintained legacy drivers with likely security holes from questionable sources.

Linux: Your video card is from a long bygone era of computing, before the term "GPU" was a thing, and basically a museum piece by now? We'll maintain a long-term support version for you for the next ten years.