Arch compared to other distributions (Slovenský)
This page summarizes some of the similarities and differences between Arch and other distributions. This question comes up repeatedly and it would be nice to have a standard response. Please note: the best way to compare Arch to other distributions is to install it and try it yourself. Arch has a wonderful user community that is always willing to help new users. The summaries below are meant only to give you enough information to decide if Arch is really for you.
Arch vs Gentoo
Because Arch distributes binary, it is much less time consuming than Gentoo. Gentoo has more packages. Arch allows both binary and source based distribution. PKGBUILDs are easier to create than ebuilds. Gentoo is more portable out of the box as packages will get compiled to your specific architecture, whereas as Arch is i686 only (although i586 and x64 user-based spinoff projects are underway). There is no documented proof that Gentoo is any faster than Arch.
Arch vs Slackware
Slackware and Arch are both 'simple' distributions. Both use BSD-style init scripts. Arch supplies a much more robust package management system in pacman, which unlike Slackware's standard tools, allows simple automatic system upgrades. Slackware is seen as more conservative in its release cycle, preferring proven stable packages. Arch is much more 'bleeding edge' in this respect. Arch is i686 only whereas Slackware can run on i486 systems. Arch is a very good system for Slack users who want more robust package management or more current packages.
Arch vs Debian
Arch is simpler than Debian. Arch has fewer packages. Arch provides better support for building your own packages than Debian does. Arch is more lenient when it comes to 'non-free' package as defined by GNU. Arch is i686 optimized and thus faster than Debian. Arch packages are more bleeding edge than Debian packages (Arch current is often more up to date than Debian unstable!)
Arch vs Ubuntu
Arch has a simpler foundation than Ubuntu. If you like to compile your own kernels, try out bleeding edge CVS-only projects, or build a program from source every once in a while, Arch is better suited. If you want to get up and running quickly and not fiddle around with the guts of the system, Ubuntu is better suited. In general, developers and tinkerers will probably like Arch better than Ubuntu.
Arch vs Crux
Arch Linux is descended from Crux. Judd once summarized the differences:
- "I used Crux before starting Arch. Arch started out as Crux, pretty much. Then I wrote pacman and makepkg to replace my bash pseudo packaging scripts (I built Arch as an LFS system to begin). So the two are completely separate distros, but technically, they're almost the same. We have dependency support (officially) for example, although Crux has a community that provides other features. CLC's prt-get will do rudimentary dependency logic. Crux gets to ignore lots of problems we have too, since it's a very minimalistic package set, basically what Per uses and nothing else."
Arch vs Graphical Distros
The graphical distros have a lot of similarities, and Arch is very different from any of them. Arch is text based and command-line oriented. Arch is a better distro if you want to truly learn Linux. Graphical-based distros tend to ship with GUI installers (like Fedora's Anaconda) and GUI system configuration tools (like Suse's Yast). Specific differences between distros are described below.
Arch vs RPM based Distros
RPM packages are available from many, many places, however third-party packages often have dependency issues, such as requiring an old version of a library. There is also confusion between RPM packages for Red Hat vs. RPM packages for Mandrake. (These are issues I had as a Linux newbie with Mandrake 8.2, and may not reflect the current situation.) pacman is much more powerful and reliable than RPM.
Arch vs Fedora
Fedora is a spin-off from the RedHat distribution and has continually been one of the most popular distributions to date. Therefore, there is a massive community and lots of pre-built packages and support available. Like all RPM-based distributions, package management is a problem. Fedora supplied Yum as a front-end to manage the acquistion of RPMs and dependency resolution. The system lacks solid yum intergration and large parts of Fedora still use the outdated and broken up2date/anaconda/rpm system. Fedora does innovate and recently earned kudos for integration of SELinux and GCJ compiled packages to remove the need for Sun's JRE. Fedora famously doesn't attempt to support the mp3 media format due to perceived patent issues.
Arch vs Mandrake
Mandrake, though famed for its installer is a very handholding distro which can get annoying after some time. Another problem is that it is a RPM based distro as discussed above. Arch allows much more freedom and less hand-holding. You actually learn.
Arch vs SuSE
Suse is centered around its well regarded Yast configuration tool. This is a one-stop shop for most users' configuration needs. Arch doesn't offer such a facility as it goes against the TheArchWay. Suse, therefore, is seen as more appropriate to less experienced users, or those who want a simpler life with expected functionality working out of the box. Suse doesn't offer mp3 support immediately, post-install. However, it can be easily added through Yast at a later date.