Arch has never been a minimalist distribution. Splitting packages is rare compared to other distributions, and dependencies aren't made optional whenever possible. Arch has *never* been minimalist… a Linux kernel with every module available and every feature enabled at least when there's no non-bloat related cost, feature-packed/complex GNU tools, nearly all optional features enabled across all the packages, etc.
>pacman is fast but not safe, it tends to break shit and config protection is implemented in a terrible way
>there is no official process to verify that a package is stable within the distro, in other distros a lot of packages are in a testing repo despite that specific package's developer claiming it to be stable on its own, because it might not be stable within the environment of a specific distro
>(arch v gentoo related) arch users complain about 'muh compile time' when it comes to gentoo, while in fact they compile a lot of AUR packages themselves, namely the *- git packages that pull the source from a git repo
>but it gets even better: they only compile a handful of packages, and those not being libraries mostly, the self-compiled packages get linked against precompiled libraries from a different setup (e.g. different optimization levels), which can then cause even more instability because it's a clusterfuck of unequal shit
>arch uses (((systemd))) and switching to something else is hard
>the vim package on arch pulls in X, so if you want to have a fancy terminal text editor on a headless server, you need to install a shitton of GUI stuff which you'll never need nor use
>maintainer told the guy who complained to just symlink vi to vim (vi is inferior)
>arch users pride themselves in installing arch and learning so much about how linux works under the hood, yet the install is literally copypasting a bunch of commands, usually without proper explanation
>e.g. to chroot into the new install, you use arch-chroot, which automatically bind-mounts procfs, devfs and sysfs, but nowhere on the guide does it say that that's a very important step, so should archfags ever need to fix their system via chrooting from a livecd that doesn't have arch-chroot, they'd be fucked
>the kernel is auto-configured in a just werks way (basically make allyesconfig), which is unnecessary bloat and for such a diy distro, configuring the kernel yourself should be the official way of doing it
>arch cannot boot without an initramfs per default
>pacstrap always installs the same shit, uclibc, dietlibc, musl, gnu-less toolchains etc are not an option from the get-go
>>4>nowhere on the guide does it say that that's a very important step
you should add that to the wiki then.
very friendly reminder that rms hates gentoo
You're a shitty gentoo user if you're only concern is badmouthing other people's distro choice. To each their own, cut the holier-than-thou shtick.
—a gentoo user
But do you look like >>77
Cool people use Arch with OpenRC.
I've got Void with runit on my laptop right now, pretty good so far.
no cool person uses Arch, stop spreading lies