That's a relief. For a while it seemed like I'd be locked out of the game I paid for.

Cool story. Must have been a pretty nice experience.

Wow, I'm impressed. I've ascended a couple of times in SLASH'EM as a doppleganger wizard, but that combination (while really fun) makes the game easier than most. As a tourist is a real achievement.

Windows 3, 3.1 and 3.11 were quite well-received as I recall. Most seemed to like Windows 95, at least at first. While 98 was hit-and-miss, 98 SE was considered as fairly solid. 2000 was highly regarded by those who used it, and despite a few big gripes XP was quite popular from the start. Windows 7 was an instant hit.

Looking back, the versions of Windows that remained popular were the ones that were popular from the start.

What about this one?

Going back to Windows 95, in fact. But apparently Windows 11 removed that ability.

That got cancelled 4 years ago, and I don't think they'll just pick it up again after all this time. If they do another UT in the nearish future it will likely be called Unreal Tournament 5 to match the UE version.

When did KDE ask for this? None of the articles mention KDE having anything to do with it. Do you have a reference?

Since you're changing the subject I trust that your earlier question is resolved. As for this new demand of yours, I don't write any software for iOS, so you're shouting at the wrong person.

I'd say that you're not being anticompetitive. But Apple wants you to stop using anything other than Apple for payments, and if you don't they'll ban all Apple users in the world from accessing your good or service. That's the rule that's being called anticompetitive.

I like that way of thinking. Don't know why they picked Block in the first place though. The logical progression would be Square-> Cube -> Tesseract-> Decateron

Rust's safety features are compile-time, not run-time. In fact this means you can have even less overhead than C. For example, if you have a C function that accepts a pointer it should check that the pointer is valid before using it and fail gracefully if it is not. In Rust you can skip that testing and error handling code inside the function because the code won't even compile if you try to pass a pointer that isn't valid.

Rust is basically like C but more explicit, rather than less.

It's Zenimax now. This is what Zenimax does. Id, as we once knew it, no longer exists.

It's a find-and-replace command for the program sed (stream editor). It means "open the the file named 'joke', then replace every instance of 'Chuck Norris' with 'Rajnikant' and write the result to a new file named 'fact'".

Basically it's saying that every joke about what Chuck Norris can do is a fact about what Rajnikant can do.

Stylus too - that ampersand is the syntax that pretty much everyone has already settled on, so it makes sense that they'd adopt the existing convention.

However, I think DrXym issue was not so much "why did they pick ampersand as the symbol?" and more "why not let us omit the ampersand when it can be inferred, as most style preprocessors already allow?".

The proposed feature is very nice as it is and, while being able to omit the ampersand would most certainly be even better, it comes with a rather heavy time and memory performance cost that would have to be paid for every single declaration of every stylesheet (even in stylesheets that don't even use nested rules at all, because the parser won't know that until it's already finished parsing) just for a rather minor improvement to the syntax. It's not worth it.

Preprocessors obviously have a different idea of what's worth it because the entire role of preprocessing it to perform expensive tasks once ahead of time to make the syntax as good as possible. While they still care about performance to an extent, the priorities are flipped around.