I’ve found it’s either just that it’s a lack of support issue aka not enough Linux users for that product or service to justify support or good support. Either that or whatever I needed was a project run by a single guy so it works kinda but also kinda not.

I guess one issue I used to run into particularly in development was conflicts in setting up a lot of things. Now with atomic systems and a sandbox for all my dev tools alongside snapshots that’s essentially dealt with. Also flatpaks can be a massive pain in the rear if one wants more direct CLI control or is getting other issues with the sandbox of the flatpak format.

I was really into the VanillaOS project for a little while but it’s somehow gotten worse instead of better, at least the last time I used it earlier this year.

For me a quick web search turned up plenty of posts from people complaining about the desktop environment provided way of disabling it not working. Most of them had no replies. Others had tone-deaf replies suggesting to turn it off using the option they said wasn’t working. And finally a few suggested to run a variety of shady scripts that mess with the guts of the system with no way of undoing the if they break something.

And I’m so happy for you that it works for the games you play.

Edit:

Actual solution found:

After a much deeper search, I’ve found out that buried in there was the actual answer I was looking for: The Linux version of Firefox is independently applying a middle click paste on its own regardless of whether you’ve had it disabled in your desktop environment options or not. For those who are struggling with this: You can disable it in about:config by changing “middlemouse.paste” to false. If you’ve also disabled in your desktop environment settings, it should be gone for good.

Also whoever decided what the tar flags will be needs to be hit with a brick, repeatedly if possible.

without looking it up:

chown -R

cp -r

ls -r

rsync. (idk, i always google this one)

scp -r

zip -r

but why not look it up? you either use a tool and arguments often enough to memorize it, or you don’t.

without looking it up (man page, --help, web, etc):

But why? Why would you need to do this when we have access to these tools?

Pointless test.

-R -r -R -r -r -r I think

I don’t know if this is true, but if yes, then -R is a GNU weirdness No wait that doesn’t make sense. ls is also GNU.

Oh god oh damn my kde doesn’t tell me that…

Okay I’ll give it a whirl:

• chown: yes, I think
• cp: no, pretty sure
• ls: what? Like for a tree? For folder size? Idk I say yes because there’s nothing recursive to me about standard ls
• rsync: literally no clue have never used it but I’d guess no
• scp: yes pretty confident
• zip: yes also pretty confident

The actual reason I barely ever find Linux annoying is because my Fedora KDE just does all I need it to pretty much all the time.

A couple more challenges:

• As an unprivileged user, append multiple lines to a file owned by root, using sudo and a here document.
• Redirect both stdout and stderr to a file using Bourne shell syntax (not bash!)

Every damn time.

I think rsync is lowercase, and maybe zip. The rest I think are uppercase. Complete guess though.

funny I never had this specific issue with recursive behavior. I find it obvious that only rsync and zip are recursive by default, but I’m not sure why.

edit: ah you mean which ones are lowercase or uppercase, that makes more sense.