3 ms·
I don't think "never breaks" is an appropriate description of Arch. At the very least, you should read the mailing list to know what updates to beware of becaus
by lorenzhs 11y ago
I don't think "never breaks" is an appropriate description of Arch. At the very least, you should read the mailing list to know what updates to beware of because they might break in a big way.
- coldpie 11y agoWell, yeah. Subscribing to arch-announce and following the instructions is a required part of maintenance.
- cookiecaper 11y agoYes. Arch is often "broken" intentionally, like when they switched to Py3 as the default about 1.5 years after its release. If you're not paying attention and you're not competent to recognize what's going on when your Python-based applications stop working, Arch is going to look "broken". I think this is a good test case for whether someone is suited for Arch or not; would you know what to do if you started getting weird errors that executed /usr/bin/python expecting python2 and got python3 instead? No? Maybe Arch isn't for you [yet]. Despite that, I find Arch is the least disruptive distro to daily work because it doesn't meddle. Canonical is full of people who think they are Steve Jobs and decide they're going to overhaul System Y with some super-special never-before-seen invented-here components this release because it's the visionary way to do things (and that other competing revitalization effort that's seeing widespread adoption, well, it's not). The result is 2-3 Ubuntu releases that are bug-ridden and really not production ready until the new system can stabilize. It seems as soon as one major userspace component begins to mature they decide to rip out another core component (Gnome->Unity; X->Mir). Source: Arch and Ubuntu user for the last 10+ years