3 ms·

I'm an Archlinux user, and BC aren't happening that often (seriously). Some big moves (likes switching to systemd) required some work, but still ran smoothly.

• laumars 14y ago
  Normally I'd agree with you, but the last 12 months have seen some pretty disruptive changes (the glibc update caught me out more than systemd had). Arch is far from perfect, and I'm not convinced I like the direction it's heading in (re systemd), but that's a plauge for the wider ecosystem than an Arch-specific issue. However Arch definitely find a nice balance between "hands on" and "lazy administration" for desktop users. Sadly though, systemd was the last straw that saw the start of my migration away from Arch on the servers (now a balance of FreeBSD and Debian; depending on the requirements of that server). As with everything though, it's all personal preference. So I expect plenty of people to have a different opinion (and different experiences as well).
  • ffreire 14y ago
    What's worked for me has been to read the archlinux.org homepage before I upgrade (maybe once every few days). If there are any breaking changes they are listed along with the recommended method for handling them. If I somehow fat finger a command and it doesn't go smoothly then all I have to do is jump in #archlinux and my issue is resolved in under an hour. YMMV of course but I've found the entire Arch experience to be pleasant and it fits my work flow, but I understand that it doesn't fit everyone's.