you are viewing a single comment's thread
view the rest of the comments
[–] 87 points 8 months ago (21 children)

I use Arch BTW full-time for work and personal for about 3 years now and haven't had any issues at all.

  • source
  • hideshow 21 child comments
  • [–] 49 points 8 months ago (8 children)

    I worked with someone who uses arch on his work laptop

    One day it just died and he had to spend a day or two setting it all up again

    I mean, its not common, but it happens

  • source
  • parent
  • hideshow 8 child comments
  • [–] 36 points 8 months ago (2 children)

    Yeah, I ran arch through college, it broke 3 times over 4 years, basically each time because Nvidia updated. Now that I don't have the time to fuss with spending a couple of hours chrooting in and fixing Nvidia stuff, I just swapped to endeavorOS sway community edition (and made sure none of my PCs have Nvidia anything in them) and haven't had an issue yet.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 13 points 8 months ago (1 child)

    Yep, the only time things have broken in Arch for me has been with Nvidia driver updates.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 8 points 8 months ago

    Yep. Funnily enough, never really had any issues with the drivers on a desktop, only on mobile, mostly switching between integrated and discrete. But after messing with them on my laptop for a few years, you better bet my laptop was only running Intel integrated and my desktop runs on amd.

  • source
  • parent
  • [–] 6 points 8 months ago

    I used to do much distro hopping coming from gentoo and settling down with endeavour. My tip for all of you: use lvm for everything outside boot, root and swap (vms, home, games). That way a complete reinstall just takes minutes.

  • source
  • parent
  • [–] 1 point 8 months ago

    I've been dailying the exact same arch installation since 2014 without reinstalling it a single time.

    Now to be fair I did have it non-bootable at several points. Worst of which was a PAM update which broke it completely because the new config was in a .pacnew file and the old one was not compatible anymore. But since it was a edge-case there was no forum post about it. Still recovered it just fine after an hour or so of troubleshooting.

    It's all open-source and usually decently documented. The only reason anyone should have to reinstall a Linux desktop is lack of experience, but I would always advise to persevere because troubleshooting my system is how I gained much of my expertise. If that's not what you want, stick to Debian.

  • source
  • parent
  • [–] 8 points 8 months ago (5 children)

    Around 10 years here. Some issues, but much less time wasted in total than if I had done β€œdist-upgrade”s the whole time.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 8 months ago (3 children)

    whats dist-upgrade? this is the first time ive heard of it

  • source
  • parent
  • hideshow 3 child comments
  • [–] 7 points 8 months ago (2 children)

    It's what Debian and similar distributions use to switch from one stable release to the next. This happens every half year for Ubuntu and every blue moon for Debian, which makes it a significantly more error-prone process than updating Arch every week in my experience.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 8 months ago (1 child)

    The only issue I ever had was Arch ARM changing the naming convention for network devices and making me have to plug the first Raspberry Pi that I upgraded into a monitor to debug what was going on.

    This was annoying for sure, but less annoying than using a 6 year old Python version like the Red Hat Enterprise Linux at work...

  • source
  • parent
  • hideshow 1 child comment