• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • Fedora’s always run really sluggishly for me on whatever hardware I’ve tried it on, so I don’t recommend it in general because my personal experience with it hasn’t been great.

    Even ignoring this, I’m not sure I’d recommend it for beginners due to how it tends to jump on the latest hip new software. For some users this is a massive point in Fedora’s favour, but I’m not sure how much I’d trust a beginner to, say, maintain a BTRFS filesystem properly. Not to mention the unlikely, but still present, possibility of issues caused by such new software.






  • While I admit that the timing with Red Hat’s closed-sourcing is really bad, and I’m also going to start avoiding Fedora for the same reason, saying that opt-in telemetry (that one can literally read the source code of) is “putting dollars first” is really dumb. Do you think the same about Debian’s popularity-contest, which has existed since 2004?


  • This really depends on your definition of “stability”.

    The technical definition is “software packages don’t change very often”. This is what makes Debian a “stable” distro, and Arch an “unstable” one.

    The more colloquial definition of “stability” is “doesn’t break very often”, which is what people usually mean when they ask for “stable” distributions. The main problem with recommending a distro like this, is that it’s going to depend on you as a user, and also on your hardware.

    I, personally, have used Arch for about 5 years now, and it’s only ever broken because I’ve done something stupid. I stopped doing stupid things, and Arch hasn’t broken since. However, I’ve also spoken to a few people who have had Arch break on them, but 9 times out of 10, they point to the Nvidia driver as the culprit, so it seems you’ll have a better time if you have an AMD GPU, for example.


  • such as the GUI installer pamac allowing unsuspecting users to trivially install unvetted packages from the AUR without even a clear indication they may be dangerous

    Unless something has changed since the last time I used Manjaro, this isn’t actually true. You have to go relatively deep into Pamac’s settings menu to enable AUR packages, and when you do, a popup comes up telling you what the AUR is and why it might be dangerous (although iirc, it neglects to tell you that an extra reason is Manjaro packages being out of date).

    Not that I’m pro-Manjaro, for all the other reasons you’ve given.


  • Manjaro was my intro to Linux, but now that I know more about it, I can’t recommend it in good conscience. Letting their SSL certs expire is something that happens (even though they could automate it), but telling their users to change their clocks so it works is a big no-no.

    Worse than that is how they manage packages from upstream. Simply freezing them for two weeks is, in my opinion, the worst of both worlds. You don’t get timely security updates, but you still end up with the issues of being on the bleeding edge - just late. It also means that if you use the AUR (which is really one of the biggest perks of Arch-based systems), it’s possible that the necessary dependencies are out of date.

    I think that if one wants “Arch with an installer” they should go with EndeavourOS, or try the archinstall script.



  • I wanted to go the VM route about a year ago, but I ended up deciding that it was just too much hassle and have kept my Windows dual boot for the extremely rare occasions that I need to use it.

    I started out using the GTX 770 from my previous PC as the secondary graphics card to pass through to the VM - which is a lot easier than doing it with a single graphics card - but given how often I actually need to use Windows, I didn’t feel particularly comfortable with the extra power use.

    So I decided I’d have a go at single GPU passthrough - which took me probably about six months of on/off (mostly off, admittedly) tweaking to get to a usable state. The first time I managed to boot Windows from my Linux install, I nearly cried. After a while fiddling with it, I decided that, as technologically awesome as it is, it really wasn’t that much different than running it on bare metal. The straw that broke the camel’s back was my inability to get Windows to gracefully hand the GPU back to Linux, despite the fact that it should have been as simple as reversing the steps to give Windows the GPU in the first place.