Oh please, stop the act, we can see your shitty referral link.

Yup, that’s how it works.

If you the flea caravan has already moved you’ll be out of luck for now. You’ll be able to fight it later on though in a slightly different spot.

I do think those featues have become pretty common in PC gaming nowadays, which is why I’m more in favor of openSUSE as the beginner distro if I had to pick just one, but sure, let’s put that aside.

When it comes to Linux though I just don’t think there’s a one-size-fits-all distro yet that I can safely recommend to everyone. And getting beginners onto a distro that fits them can greatly benefit their initial experience, so I think it’s worth it to give them a few simple choices. That said, you’re completely right that the way OP tries to explain the differences isn’t how you should do it. Ever. Less choices, less jargon, less mentions of fringe distros. It also doesn’t help that a lot of it seems to be based on hearsay rather than actual first-hand experience.

Do you really want to recommend btrfs to beginners?

I mean, it’s the default on Fedora with all its spins, openSUSE, CachyOS and even SteamOS for its root partition.

So lots of people use it nowadays without even knowing.

Chiming in, I’ll say that I mostly agree with your points, except for one:

Someone who just started looking into switching to Linux is looking for neither X11 nor Wayland support.

They won’t care about X11 vs Wayland, sure. A non-ignorable number of them will care about stuff like HDR or multi-monitor setups where different refresh rates don’t stutter and VRR works, and that’s where proper Wayland support becomes a must.

If you recommend someone a distro that can’t do those things and later have to tell them that they have to switch distros for that chances are high they’ll just go back to Windows.

Yeah, that’s why I’m currently only recommending Mint to people who don’t do any gaming. It’s kind of a shame that Mint doesn’t have a KDE spin. It would be my unconditional beginner distro otherwise.

Personally I run CachyOS + KDE with native Wayland and HDR enabled system-wide. It’s kind of amazing how I don’t even need to clog the launch parameters of every game with a bunch of variables and tools like gamescope anymore. I just have to hit launch and all the fancy features just work.

I see.

HDR depends a lot on the monitor I guess. Mine isn’t really brighter in HDR mode than normal because it’s an OLED, so the big difference is that the darks can get darker and more detailed as opposed to the brighter brights on HDR LCD/LED panels.

As for VRR, I’m a huge fan of it and I can’t recommend it enough. Particularly on high refresh rate monitors and demanding game it’s a big win not having to tweak your settings so that the framerate always stays above the monitors specified refresh rate. No tearing. No penalty from not reaching the required framerate. Just a smooth presentation.

You can actually use VRR on X11, but only on for single monitor and it will introduce tearing on the others.

Neat theme.

everything has been running flawlessly.

I have to ask though: Do these monitors not have HDR or VRR and run at the same refresh rate?

Those are the things why I usually wouldn’t recommend Mint for high-end gaming rig like yours right now: None of the supported DEs are really ready for Wayland and therefore stuck with those problems (for now).

At the very least you can still pay a small one-time fee for the DWD WarnWetter app (or enter a code for firefighters).

Best 3€ I’ve ever spent purely out of spite, even if the reason behind it is complete BS.

Exactly. Locking basic services behind apps should be illegal. Services must be accessible to everyone.

What’s extra funny is that I already did all of this, and yet, I’ve been informed that my developer account is subject to deletion because I’m not active enough. Since my game does not get regular updates I said F this, let them delete my account. It’s still available for sideload on itch.io anyway. Jokes on me for believing that.

So yeah, it seems like Google is actively hostile towards building a library of software/games that just work and intentionally only wants live service garbage apps on their platform because those make more revenue.

I feel like a big problem is that a lot of people never learned how to learn.

Adding onto your examples, I’ve also heard about a study once where they were given similar basic Excel tasks. However, you didn’t even have to solve the tasks. Instead, just trying to get help from the help function or searching online got you into the highest skill bracket. That bracket ended up being the smallest group.

Because it wasn’t mentioned, I’ll just note that Joplin has also has the option to sync with a dedicated server component.

While it doesn’t work in a P2P configuration like a Syncthing setup allows, I’d recommend it for anyone with access to a server.

This, so much. Looking back, it’s just insane that pretty much every program you don’t regularly use will beg for updates on Windows. There are some bandaids like WinGet now that I appreciate, but it’s still nowhere as seamless as when the OS and the whole ecosystem around it are designed with a package manager in mind.

A huge chunk of the time I have to spend on tinkering is probably already saved by me not having to wait for updates.

Mint is a fine distro, but I wouldn’t recommend it to anyone that wants to do gaming right now either. None of the first class DEs are running on Wayland yet, which means that most monitor features of the last decade are not at all or badly supported.

I personally prefer lazygit nowadays, but when it comes to GUI clients on Windows then Git Extensions is definitely a very good pick.

I particularly like that it doesn’t hide that it’s just executing git commands under the hood and its focus on the history graph. Those two things really helped understand how git actually works and why I’m still recommending it.

I mean, becoming owned by IGN was ultimately a good thing, as the previous owners were apparently preventing DF from going indepent before. At least that’s how I understood it from their announcement video.

Looks like your keyboard actually has lots of revisions with different controllers.

Thankfully, this page on the QMK repository lists all of them and the different commands for compiliing: https://github.com/qmk/qmk_firmware/tree/master/keyboards/bastardkb/tbkmini

You’ll have to figure out if you have the v1 or v2 of the Elite-C revisions and use that.

So, based on the parts list on Github, I believe these actually have Elite-C controllers, which, as you’ve already noticed have an ATmega32 on them instead of the Raspberry Pi Pico. While the Pico will act like a disk when flashing, the ATmega will have to be flashed with the QMK CLI, or the QMK Toolbox on Windows.