What I always find frustrating about that, is that even a colleague with much more Bash experience than me, will ask me what those options are, if I slap a set -euo pipefail or similar into there.

I guess, I could prepare a snippet like in the article with proper comments instead:

set -e # exit on error
set -u # exit on unset variable
set -o pipefail # exit on errors in pipes

Maybe with the whole trapping thing, too.

But yeah, will have to remember to use that. Most Bash scripts start out as just quickly trying something out, so it’s easy to forget setting the proper options…

I don’t have the Bash experience to argue against that, but from a general programming experience, I want things to crash as loudly as possible when anything unexpected happens. Otherwise, you might never spot it failing.

Well, and nevermind that it could genuinely break things, if an intermediate step fails, but it continues running.

Yeah, indies are thankfully still covering 2D games, and there has been somewhat of a rebound in general, where e.g. Nintendo will also publish 2.5D versions of some of their games.

It just always felt weird that AAA studios treated 3D as mandatory, in the name of profit in particular, despite it locking out customers.
Well, kind of the obvious thing happened: Mobile games. Often fiercely 2D. Often controllable with one finger. And of course, obscenely profitable.

Huh, so if you don’t opt for these more specific number types, then your program will explode sooner or later, depending on the architecture it’s being run on…?

I guess, times were different back when C got created, with register size still much more in flux. But yeah, from today’s perspective, that seems terrifying. 😅

Yeah, it’s just wild to me, that we went full-force ahead with the whole 3D thing, when you lock out so many potential players with it.
With 2D games, you can chuck someone a controller and even if they’re just haphazardly pressing buttons, they can still participate in the game. With 3D, no chance.

And even those who do have practice still struggle with it. Think of a difficult 3D game and I bet it’s a valid joke that the true end boss is the camera.

What really frustrates me about that, is that someone put in a lot of effort to be able to write these things out using proper words, but it still isn’t really more readable.

Like, sure, unsigned is very obvious. But short, int, long and long long don’t really tell you anything except “this can fit more or less data”. That same concept can be expressed with a growing number, i.e. i16, i32 and i64.

And when someone actually needs to know how much data fits into each type, well, then the latter approach is just better, because it tells you right on the tin.

Oh man, a zero byte long unsigned integer? Lots of languages represent it as an empty tuple these days (the “unit” type), but from quickly scanning the documentation, it looks like HolyC doesn’t support tuples, so I guess you gotta get creative…

I am skeptical how I might use it to start a campfire even though it’s supposed to be a camping tool.

Could probably light some tinder with it, like thin twigs or dry grass…

Hmm, to my knowledge, tx generally means “transmit”, as opposed to rx – “receive”.

I don’t think, there is much logic to it…

I think, the problem is that management wants the expert humans to use the non-expert tools, because they’re non-experts and don’t recognize that it’s slower for experts. There’s also the idea that experts can be more efficient with these tools, because they can correct dumb shit the non-expert tool does.

But yeah, it just feels ridiculous. I need to think about the problem to apply my expertise. The thinking happens as I’m coding. If I’m supposed to not code and rather just have the coding be done by someone/-thing else, then the thinking does not occur and my expertise cannot guarantee for anything.
No, I cannot just do the thinking as I’m doing the review. That’s significantly more time-consuming than coding it myself.

I would also definitely recommend to get started with learning Rust. You will need to learn more concepts along the way, but you can still learn about them while you’re coding Rust.

Or rather: I always found it most productive to learn about concepts, while I’m actively using them in a project. So, I would even recommend to jump into Rust now, try to tackle a few smaller projects, and then continue learning general concepts later.

Can’t easily test this, but it might be possible to set the game itself to “Full Screen (Windowed)” and then tell Plasma to fullscreen the window. You can try this by launching the game and then pressing Alt+F3 to bring up the window menu. In there, you can fullscreen it through Plasma. You can also set a keyboard shortcut for this (I use Meta+F11).

Also has to be said that KDE on those slower-moving distros is actually buggier than on up-to-date distros. I have to use Kubuntu LTS at work and it has so many more glitches and crashes compared to openSUSE Tumbleweed and NixOS on my personal laptop.

A few years ago, I found Kaffeine and was so surprised that I never saw a video player before with controls in a collapsible sidebar.

Old screenshot, but this is what it looks like when a video is playing:

It seems like a rather obvious idea, but I guess, it doesn’t get copied much, because most video players don’t have a ton of controls to begin with…

Yeah, and you don’t have to know which fork to choose. Only the compatible fork will show up in the search.

(I was going to recommend that, but had something in the back of head, that you needed a manual step to enable the configuration. But I just saw that this is described in the Plasma 5 version, not the Plasma 6 fork, so I guess, it’s not necessary anymore…)

It is the first one, yes. Just the normal keyboard shortcut settings. And all the Krohnkite shortcuts are prefixed with “Krohnkite”, so you can find them easily.

I believe, that’s something which became impossible with Wayland?

But it wasn’t very good under X11 either. Even back then, it was much less clunky to use the various KWin scripts, which offer tiling. Well, and by now Plasma has built-in semi-automatic tiling, which those scripts basically just configure, so they do now feel quite smooth.

Should note that this is still a manual process. For auto-tiling, you want e.g. Krohnkite.

The one you linked is only for KDE Plasma 5. For Plasma 6, you would use this fork: https://codeberg.org/anametologin/Krohnkite

I’m genuinely baffled how many oligarchs had contact with Epstein. I do believe their primary job qualification is a lack of morals, but there’s so many ways to be amoral, you don’t have to all be friends with the guy that offers pedophilia.