You can get Steam on just about any distro, for years at this point. And there’s always Flatpak for these cases too although for Steam I recommend native packages.

You’re not wrong, it’s definitely not something a n00b should attempt in most cases. But I’ve done this before to save myself the need for distrobox. A lot of proprietary software only offers .deb, but is usually either statically linked or comes with its own set of nearly all the libraries it needs. So just extracting and running it often does the trick on non-debian distros like Fedora in my case.

Seriously though, just use distrobox or see if there’s an unofficial package for your distro that you trust (AUR/copr/ppa/OBS). It’s more straight forward especially if you don’t know what you’re doing.

That’ll work but distrobox is a much simpler solution

Also great when you get some software as a deb for old Ubuntu and don’t want the trouble of manually making it work on a new system. Just make an old Ubuntu distrobox.

I use fish which is quite nice OOTB, although if you want a posix compliant shell, zsh with some plugins is also great.

Use a shell with decent auto-completion. I have not been irritated by this in years.

Reminds me of this…

You can use VAAPI or NVENC for hardware encoding, I believe there are presets for that in the render dialog nowadays. I think that is or was broken in the AppImage though. Using the GPU for actually processing heavy effects (like color correction, chroma keying, transformations etc) is currently not possible and the GPU processing option in the settings is broken. And many of these effects are single threaded on the CPU.

Kdenlive unfortunately isn’t amazing at really utilizing your hardware. Getting better though.

I’ve never had good luck with distro packages of Kdenlive, on any distro. Always crashing and glitching. The Flatpak has always been much more stable for me, and the AppImage is even more solid.

Btrfs snapshots are a blessing. Call me a cheater :P

I don’t use Wine so I’m really not sure if this would be prevented

It is not prevented. In fact I saw a video where someone removed the Z:\ drive for wine (the path that gives windows apps access to the whole Linux rootfs) and then ran Wannacry, and it was somehow still able to encrypt all writable folders on the system.

That wouldn’t remove the Wine prefix, i. e. the virtual C:\ drive where the virus most likely lives. Uninstalling Wine wouldn’t do shit since it only removes files that your user (and thus wine) can’t even write to, and if a virus manages to get around that you have bigger problems.