I've bought a couple of lewd games, sponsored development of another few, but generally their development pace tends to be absolutely glacial.

Either that, or it's turned out to just be a token "game" to try and sell a gallery of - oftentimes average quality - artwork.
Really not a fan of when people do that. If I want to buy an artwork gallery, then let me buy an artwork gallery. If I want a game, then I actually do want a game.

The predictable interface naming has solved a few issues at work, mainly in regards to when we have to work with expensive piece-of-shit (enterprise) systems, since they sometimes explode if your server changes interface names.
Normally wouldn't be an issue, but a bunch of our hardware - multiple vendors and all - initialize the onboard NIC pretty late, which causes them to switch position almost every other boot.

I've personally stopped caring about interface names nowadays though, I just use automation to shove NetworkManager onto the machine and use it to get a properly managed connection instead, so it can deal with all the stupid things that the hardware does.

Go really does do well in the zero-to-hero case, that's for certain. Unfortunately it doesn't fare nearly as well in terms of ease when it comes to continued development.

Well, one part of it is that Flatpak pulls data over the network, and sometimes data sent over a network doesn't arrive in the exact same shape as when it left the original system, which results in that same data being sent in multiple copies - until one manages to arrive correctly.

To be fair, having to interact with MS Teams with any part of your body is painful.

He won't be allowed to perform at Eurovision with the Windows 95 name/trademark/logo, so it would be hilarious if he switches to a name like Linuxman during it.

Well, there are people running Linux in all manner of ways, like VRChat shaders.

Eggroll

A lot of that data doesn't actually exist, ostree hardlinks data blobs internally, so the actual size on disk is much smaller than most disk usage tools will show.

People love to complain about CMake, often with valid complaints as well. But it - to this day - remains the only build system where I'll actually trust a project when they say they are cross-platform.

Being the Windows maintainer for OpenMW, it used to be absolute hell back a decade and half ago when an indirect dependency changed - and used something like SCons or Premake while claiming to be "cross-platform", used to be that I had to write my own build solutions for Windows since it was all hardcoded against Linux paths and libraries.

CMake might not be the coolest, most hip, build system, but it delivers on actually letting you build your software regardless of platform. So it remains my go-to for whenever I need to actually build something that's supposed to be used.
For personal things I still often hack together a couple of Makefiles though, it's just a lot faster to do.

I love their response to (paraphrasing) "Are you going to do another Darth Vader and alter the deal on us in the future?" - "Oh yes, potentially every year."

It's rather interesting to me how nobody puts any value on the Deck trackpads in comparisons like these, and yet they are basically essential if you want the device to be able to play anything but console-optimized games / games that are built for gamepads first.

Playing something like Skyrim on one of the alternative portables can certainly be done, but being able to comfortably play games like Against the Storm, Anno, Civilization, Dwarf Fortress, Factorio, Homeworld, Northgard, OpenTTD, Stellaris, etc is where the Deck really shines and where all the "alternatives" fall completely flat.

Edit: Not to mention that trying to run Windows without any kind of direct mouse input is really painful, and all the "alternatives" keep doing exactly that.