Does that mean you’ll do typesetting now?

The only label on the map that’s both on Latin and in old German.

Is OpenBSD seriously still using CVS for development?

And “nothing” does not fit, either.

Rimworld for me.

(I have never tried Dwarf Fortress.)

Honorable mention goes to War Thunder, while it isn’t on of my favorites, I was still a bit blown away to find out it runs natively on Linux.

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.

https://www.youtube.com/watch?v=qmVnr7rsWrE&t=70s

https://upload.wikimedia.org/wikipedia/commons/transcoded/c/c1/It-Gnocchi.oga/It-Gnocchi.oga.mp3

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 wonder when, if ever, Warner Bros. Is going to learn that players are actively pushing back against corporate greed and live service games are already way past the limit of microtransactions that players deem acceptable.

Some time after that actually happens.

Yes, there are a lot of players in various social networks loudly complaining about the phenomenon (although I suspect many of those are not even in the target audience to begin with), and there are even some actively boycotting these games, but so long as there are enough of them left willing to play ball, and especially some with an exploitable addiction-prone personality that can be hooked on loot boxes and microtransactions until they spend more than they have, there just isn’t anything for these companies here to “learn”. Other than “hey, this is insanely profitable”.

They may get insulted on Xitter for it, but who cares, everybody gets insulted on Shitter…

MacOS is basically a different world.

Paywalled.

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.

Legalisiert soll das ganze bis zur 12. Schwangerschaftswoche werden, und dann soll immer noch eine Beratung verpflichtend sein.

Frage: Wie lange dauert es im Normalfall, bis eine Frau überhaupt merkt, dass sie schwanger ist? Wie lange dauert es in ungewöhnlichen oder extremen Fällen? Wie lange muss man auf so einen Beratungstermin warten? Wie lange anschließend auf einen Termin für die Durchführung der Prozedur?

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.