AMD “just works” unless you dare expect hardware encoding that you explicitly picked your card based on to work properly

I actually just found that on there page thanks :)

Wow, that’s a thick write up, started picking though it. I’m still early into planning things out and still trying to settle on my setup. I haven’t even figured out my storage mess yet.

Yea so I tried nobara and to be honest unless I’m stupid it sucked… Constant graphical issues no matter the application(I could not play halo Infinite it started I old load game but then it would break). So I then put on mint after a day and downloaded Nvidia drivers through there GUI and then wine (not entirely sure what it does to be honest) and tried some games all worked great/well.

with c++ they’ll learn programming faster

I strongly disagree.

If you want someone to learn how programming works mechanically, recommend C. It’s a very simple abstraction over the hardware, unlike C++ which comes with a ton of complexity that’s completely unrelated to the task of learning how programming works. There’s way too much magic with things like templates, operator overloading, etc that gets in the way. In fact, I recommend learning C on very simple hardware, like an Arduino, where you don’t have any of the nonsense associated with operating systems, like system-specific nuances in file handling and whatnot.

That said, I’ll always recommend Python first to new programmers. It has relatively little magic while abstracting away most of the annoyances and footguns that you’ll get in lower-level languages like C. Once the user is comfortable using Python to get things done and is interested in learning more, I’d throw them in the deep end and recommend Rust, which forces you to contend with things programmers are expected to understand (but can easily get away with not understanding) in C/C++, such as ownership and lifetimes. Python is the “get stuff done” language, and Rust is “theoretical CS in practice.” If they really like Rust, I’ll steer them toward functional languages like Haskell which go even harder on the CS theory. Or if they want something a bit more “mainstream” than Rust (e.g. they want to make games), going for C++ makes a lot of sense, and they’d probably write better C++ because they’ve learned the strategies and terminology from Rust.

but with c++ they’ll learn programming faster simply

I strongly disagree with this. I’ve learn to program with C (pure C), and I lost so much time with that language’s cruft and idiosyncrasies. Python is a much better tool to teach programming concepts.

Too many experts who value the deeper teaching potential angle seem to never want to acknowledge the bounce rate it will also have.

No, not everyone asking about how to get into the Linux ecosystem is doing so specifically because the knowledge itself is its own reward. Those who are will tighten their belts, whiten their knuckles, and figure it out just like you hoped they would. Those who aren’t will collapse under the sheer weight of all the bullshit and bail out. Frankly I’d consider the bulk of curious new users to be the latter and I default assume it for everyone who appears unless they indicate otherwise.

Some people think this kind of filtering based on willingness to learn is a good and healthy thing. I call it elitism and gatekeeping.

Arch is fine, but you kind of need to know what’s going on or you’ll get overwhelmed and just nope out.

New users looking to accomplish a task (e.g. playing games, as in the OP) should use a mainstream distro with a graphical installer and whatnot. New users looking to learn Linux and want to use Arch can just use Arch. It’s really not that hard, but it’s also not the easiest to get started with.

I used Arch for 5 years and it was fine, but I got tired of a couple of annoyances and bailed (mostly Nvidia drivers getting out of sync w/ the kernel, manual intervention on upgrades, etc). I now use openSUSE Tumbleweed, which annoys me a lot less and has a very similar feel at the end of the day. I think Arch is fine, but I’m only going to recommend mainstream distros with a GUI-centric UX unless the person gives some indication that something else is preferred.

I “distro hop” repeatedly every day since we use a mix of ubuntu and rhel “at work” and I use a mix of debian and fedora “at home”.

My understanding of “distro hopping” is reinstalling the OS to try something different, not just using something different throughout the day. I also use a few different distros for different reasons (openSUSE Leap for my NAS, openSUSE Tumbleweed for my desktop/laptop, Debian for my VPS, Alpine for containers, etc). The package manager is the main important difference between them, and that’s really easy to look up as needed.

But you are more describing “learn openSUSE” or “learn Fedora” as opposed to “learn Linux”.

To an extent. A lot of people recommend “distro hopping” to try a different desktop environment or something, and I’ve always just configured those within whatever distro I’m using at the time. I only switch when I either need to reinstall anyway, or something with how the maintainers handle packaging annoys me enough to try something else.

So yeah, I only recommend “distro hopping” when first trying Linux because hopping is fun, but once you see what’s available, I think it’s counter-productive unless you have a clear reason why your distro won’t work with what you want.