... which is also not open-source. But yeah, it's areally good music player and organizer.

Looking into the metadata of the included PDF version reveals that it's from 2004, so even a bit older than that.

Just to give a bit of context: This comes after two months of outright refusal to do even the bare minimum, like transferring the Steam Store listings for games where the devs had full ownership of the IP.

So yeah, it's nice to see that this will seemingly be resolved somewhat nicely, but that's about it.

Hard to say. Obviously not a lawyer, but I'd say that it's within Valve's rights to decide which games it sells to which region at a whim, particularly when they could've also become liable if they knowingly continued selling a "defective" product in those regions.

That said, putting the legal perspective aside, I doubt that Valve would've done anything that could've hurt their relationship with Sony without consulting with them first.

I really hope so. I just can't comprehend how they thought that shutting down this studio in particular was a good idea, when Hi-Fi Rush has kind of been used as the poster child for GamePass for a while now. That alone should've been a good reason to keep the studio alive, even if it was operating at a loss.

All they had to do was to allow me to move the taskbar to the side and I'm only partially joking.

Yup. At the very least, they shouldn't have made it a requirement for TFT. If it were possible to cheat there that'd be more of a game design problem anyway.

I'd have a bit more symphaty if they at least tried to do the bare minimum before choosing the nuclear option.

Most notably, the PVE queues in LoL were infested with bots for years and you could tell them apart from real players before they even made their first move. Often times you'd be the only human player. If stuff like that wasn't caught, I have serious doubts about their previous efforts to catch "real" cheaters.

Lots of good advice already, but there's two things I'd add:

1. If you can't find a place to test different keyboards you could also get a switch sampler first. They're relatively inexpensive, at least compared to getting a keyboard you don't end up liking. You don't need one with lots of keys or with multiple brands, as long it contains the major types (Clicky, Tactile, Linear) and has some variation in actuation force. Worst case, you end up with a new fidget toy.
2. You don't necessarily need VIA, just QMK. There's the online QMK configurator, which allows you to configure your keyboard, download it as custom firmware and flash it. If you have some experience as a developer you can also just grab the QMK firmware and customize it that way. QMK offers excellent tooling and tutorials that makes this incredibly easy, particularly on Linux. I'd recommend checking this out even before deciding on a specific keyboard model.

[...] I didn't bother to activate 2fa on my github account. I ended up writing a simple fetch for fun, ...

I'm not judging, but reading those two lines back to back is pretty funny.

Also good to know what causes those seams. I've noticed it in some consoles, but never bothered to check why exactly that is.

That's true. Personally though, it not being optional for any amount of time just shows that there's no good argument to have it be mandatory in the first place.

Yup. I've always loved having a handheld device as a companion to my PC. The first few months with the Switch were great, but as time went on I just wanted a better designed Switch that's also just a PC, particularly after getting hardware-banned for trying to fix some of the issues myself with homebrew apps.

I never would've thought that we'd actually get to see a device that's real so quickly (anyone remember the Smach Z?), is actually pretty good and how quickly it's now becoming its own market segment.

Yes, there were lots of other issues, but what I'm mostly referring to was that many of these broken systems wouldn't have to be built if stuff like DOTS and virtual texturing wasn't unfinished:

And the reason why the game has its own culling implementation instead of using Unity’s built in solution (which should at least in theory be much more advanced) is because Colossal Order had to implement quite a lot of the graphics side themselves because Unity’s integration between DOTS and HDRP is still very much a work in progress and arguably unsuitable for most actual games. Similarly Unity’s virtual texturing solution remains eternally in beta, so CO had to implement their own solution for that too, which still has some teething issues.

Considering that DOTS is allegedly at least partially to blame for the disaster that is Cities: Skylines 2 (Source), I'm almost tempted to say that's a good thing.

While the licensing changes were the last straw, I was always annoyed with the direction Unity was going, which was grafting a bunch of unfinished, barely documented features onto the engine, putting the stuff it's supposed to replace on life support and never actually finishing those features for years.

Oh yeah, I kind of skipped over that, but I actually meant that more flexible consumption helps bring down baseload demand, and in turn the need for backup generation as well once we reach that point where that matters.

Really good explanation of the issue though. Personally, I'm a bit more optimistic about being able to be more flexible demand. Particularly EVs and heat pumps are two areas where a smart grid can help shape demand without even being noticed by the people (apart from cheaper tariffs) as long as the car is fully charged in the morning and the room temperature is maintained.

The entire point of the nuclear is so that it can take the base load

The idea to cover baseload demand with its own baseload power generation is an outdated concept though from a time when demand was inflexible and generation could be controlled to fit. Now that generation is dynamic, having baseload power generation is the opposite of what's needed. We need flexible backup generation and more flexible demand to bring down baseload demand.

We also shouldn't just focus on generation, but also on consumption. If we had a smarter grid that could shift demand to fit the dynamic power generation of renewables better, that should reduce the required capacity for backup power generation quite a bit.

Don't worry. There's still plenty of ESP32 waiting to be flashed with ESPHome and placed into their own little enclosure out there.

Source: Me, who's got a Bluetooth Proxy for my adjustable desk and some small LED strips running, with a soil moisture sensor planned as my next quick project.

I use the CLI because it's keyboard-focused (though I use lots of mouse-enabled TUIs) and because it's programmable.

Generally though, I kind of get what you're trying to say, but 'uniformity' feels like an unfortunate choice in the context of your question, as the meaning can be very arbitrarily defined, hence the confusion. I could, for example, claim that GUIs are more uniform because all chat apps, browsers etc... are so similar to each other that once I've learned one I can use all.

Which is why It'd probably be better if you tried to reword your initial question avoiding that term, focussing more on describing the desired benefits of your definition of uniformity.

Otherwise I'd point towards voice recognition, as that's very similar to a CLI, but probably not what you had in mind, I'm guessing?

Even as a heavy user of CLIs, claiming that their text-only nature somehow makes them more uniform, feels a bit overly reductive to me:

To start with, there's simple fire-and-return commands, interactive commands, full-blown TUIs and so on. Then there's the parameters, which aren't really consistent either across applications either. Neither in the naming of arguments, nor their grammar. The representation of the output is also all over the place.

With all those things, it's really not so dissimilar from the different layouts of GUIs. Not to mention that there's also lots of CLI tools that do the same thing but have a different interface, so yeah.