ruario |
03-26-2013 05:55 AM |
I ran Arch as my primary OS for a little over a year before making the switch to Slackware. Arch in many ways surpassed the expectations I had prior to actually using it. I really didn't expect the level of stability I received from a bleeding edge distro. I thought I might end up having to fix it every other week. In reality, I had a couple of minor breakages in that time but nothing that couldn't be resolved fairly quickly. Also the things that drew me to it in the first place, its simplicity and the fact that it provides a great way of testing against the latest software and libraries were still true when I moved away from it.
The reason for switching was primarily the fact that the constant updates required too much of my attention, not just to run a few pacman commands but to consider what some of those changes will mean to me and what adjustments I might need to make. Granted for the most part very little but I still had to consider their impact (I don't like taking too many risks, especially on my primary work machine).
This started me on the hunt for something that, like Arch, had a simple design and didn't try to be too clever for its own good. Slackware seemed like an obvious choice though I must admit I was initially concerned by the lack of inbuilt dependency management. Nonetheless I made the jump and was suprised to discover that dependency management actually turned out to be something of a non-issue. I have never had the urge to move back.
That all said, Arch is a fine distro and if something dramatic ever happened in Slackware land it would probably be the first candidate shoud I need a replacement. FreeBSD would be the another obvious choice for me, though inferior hardware support and some missing proprietary software might make that a trickier option.
P.S. One area where IMHO Arch still trumps all is its Wiki. But this is not a problem as I still use it. ;)
|