Gamey

Definitely not limited to RHEL!

Damn, I am quite sure it’s in Debians build-essentials!

htop, distrobox and in some cases Flatpak!

Edit: after reading the comments I want to add curl and git, seriously, why aren’t those a default?!

I don’t think it’s a SSD vs HDD situation (both should work perfectly fine with any DE) but rather a case of old and dieing HDD, that’s at least what caused my system to fuck up two years ago or somethimg like that. There are systems that work better on far slower than HDD (today only “achived” by dieing HDDs) speed tho so I could imagine that improving the situation, just don’t sotre important stuff on that till you got a new drive!

If you create multiple user accounts you can contain the user specific parts for those accounts if I am not wrong, certain thing will probably still be a little messy but I only tried it on the same account before and never did again, that could pribably help a little!

That’s because you are on XFCE and they haven’t adopted Wayland yet, NVidia drivers sadly really struggle with that but it’s slowly getting better!

KDE should run fine on those specs, I would try to replace the hard drive, I had one of those slow down a Laptop to a point where I almost threw it away but with a new one everything worked fine again. If it doesn’t I would say as a beginner Linux Mint with ether XFCE or Mate should be a great choice but I doubt you need it with those specs tbh!

I bet the dev gets a lot of angry comments over that, a absolute hero!

Lucky you, those idiots are fucking everywhere!

There are just too many terms, just give enough context and people will understand it regardless tho!

It can mess with configs, themes and some other annoying stuff so I never did it again but there is no big risk or anything, it’s just a little tedious to fix small things afterwards!

Did you read my comment at all? Flatpak and Snap share dependencies while Appimage doublicates all of them so unless you have no big dependencies on your system (literally impossible with Linux systems) Flatpaks and Snaps become more efficient in terms of storage usage the more you use them because they share big parts while Appimage still dublicates every single dependency because it’s a single binarie with everything in it…

Well, that’s your choice, I like and use Flatpaks but noone has to do so!

Flatpaks aren’t very relevant for servers if I am not wrong but Canonical definitely tties to push Snaps for that usecase, I feel like other container technologies like Docker or Podman are a lot more relevant in that context and containerization in general is really nice especially for server use and not that hard to wrap your head around! ;)

Appimage literally requires more storage for the apps because it dublicates all dependencies so in terms of storage flatpak and dnaps win by FAR, there are valid reasons to criticize all three but your comment is a sad joke!

With a focus on “sometimes” but yea, it’s certainly better than most in many cases!

The GDPR is one of the most important laws the EU ever created and the issues you talk about are probably cookie banners, that’s such a increadably tiny issue in a small part of a huge and hugely important law that this comment is nothing but fucking silly!

Yes, that’s the goal, there was a great blog post from one of the KDE guys about a meeting people from the Neochat, Matrix and XMPP projects where invited to to explain the benefits of interoperability between chat apps and that part actually made it into the law now!

Well, not about the DNS blocking, that’s absolutely great but it can only block on a domain basis so ads from the same domain aka first party ads (E.g. Youtube ads) can’t be blocked using it.

DNS blocking isn’t proper ad blocking but it’s certainly better than nothing!