Hacker News new | ask | show | jobs
by dTal 3427 days ago
I found this to be a real problem with using Arch in production. Updating is a bit of a catch-22: if you upgrade frequently, the workload of keeping up with the minutiae of not breaking your system is overwhelming. And the longer you leave it, the closer the chances of breakage when you do approach 100%. Result: you inevitably fall off the update treadmill at some point, usually during some sort of crunch time, and then never update again because who wants to tell their boss they spent a day debugging a self-inflicted problem? Safer to leave it alone and get on with your work.

This is why I switched back to Debian. Updating is stress-free and there's no downside to doing it as often as you like.