I’m pretty sure everyone’s birth date is 1/1/1970

FTFY

“Won’t anyone think of the cHiLdReN?!”

Things are moving very fast right now with a lot of back end linux stuff changing rapidly to support more people and programs coming off Windows.

Please, indulge me. What exactly is it you’re talking about here?

Imo, not having access to the most recent Thunderbird or LibreOffice version doesn’t matter at all to beginners, making Debian-based systems perfectly viable.

Fedora KDE, on the other hand, may turn out to be an annoyance once they need to install proprietary drivers (as OP is due to their NVIDIA card).

Very basically (ELI5):

• Bazzite is an immutable distro, meaning anything in the file system but your /home is read-only. That makes the OS pretty secure: from the user (who cannot break it by messing around), from software bugs (which cannot really take down the system with them) and from potential malware incursions.
• Nice… But how do we install software on such a system? Linux software does need write access to system directories (e.g. /bin, /lib, /etc and others) during installation, and now it can’t. So we need to work around that. Bazzite does that in two ways:
  • installing Flatpaks, a special way of packaging software together with all of its dependencies and running it in a kind of sandbox, separated from the rest of the system.
  • installing it inside distrobox containers (for any software that does not come as Flatpaks). These are, essentially, a separate complete Linux distro (though stripped down as much as possible) running in a sandbox. And on these we do have system level write access. If we mess up, the software messes up or it’s malware, only the distrobox will be affected, not our host machine.

You may now begin to understand why I wouldn’t recommend Bazzite to beginners: it’s a cool, but advanced concept, and you need to understand its limitations and workarounds. Otherwise, you will just be roadblocked at some point, or, like you are, hacking away on the command line without actually understanding what you’re doing. On that note, props to you for succeeding so far! But also, at the risk of sounding like a gatekeeper, it shouldn’t be that way, for two reasons:

As a beginner switching from Windows, you have enough things to familiarise yourself with: the file system structure is different (“Where’s my C:\ drive?”), software installation is different (“Wait? I don’t just download random binaries from the Internet like a caveman?”) and a lot of software is different (“Where is Paint? Where is Outlook? And where did the ribbon menu in Office go?”). You really shouldn’t have to tackle the command line to get basic functionality working.

If and when you start working on the command line, you must understand what you’re doing, because the command line assumes you do. It lets you do anything with and to your system, which makes it a very powerful tool. But powerful tools need to be handled with caution, and as you can see from your experience, Bazzite does not teach you that: it expects you to use the terminal right away, and since you can’t, you just resort to copy-pasting random commands off the internet. In Bazzite, this cannot hurt you much because of how the distro ist built. But it’s an absolutely terrible habit for new Linux users to get into. Once you switch distros and move to something else than Bazzite, just running random commands on the command line can absolutely wreck your system.

Good advice on the Ventoy front. It makes trying out things very comfortable, if you have a large enough thumbdrive (>32GB).

Don’t push beginners towards immutable distros such as Bazzite though. Some things there can only be installed within distroboxes, and expecting beginners to fiddle with containers and images of other distros is way more than they should have to contend with.