Void Linux vs OpenRC

A single instance of Void will be supported forever without needing to reinstall (you can update the system every day instead of having to install one major update every 6 months or so).

More minimalistic than Arch since it doesn't use systemd.

An init system with the "do one thing and do it right" mentality. Void Linux does not support systemd.

Unlike it's closest competitor, Arch, Void includes a very user-friendly and simple installer in the ISO.

Runit init system is incredibly fast to boot and very simple to use.

Arch Linux doesn't make ISO's with different DE's. One need to manually install it through CLI version. But Void which is competitor of Arch, provides a wide range of DE's ISOs.

Base installation can idle at less than 250 megabytes of RAM.

A brand new package manager that is fast, full-featured, and tailored specifically for Void Linux.

Full support for LibreSSL, an OpenSSL fork focused on maximizing security. The xbps-src package builder works in a similar manner to BSD's ports collection.

Musl libc is lighter and faster than bloated glibc. Musl has been argued to be more secure overall than glibc also but is also not supported by all software.

Unlike the Arch Forum, it is a friendly forum (although small).

Xbps-src is a source packages collection which is pretty similar to FreeBSD's ports and may replace AUR for Void users.

There are some packages in official repos, than may be found only in AUR.

Neofetch looks good.

Uses runit instead of systemd.

OpenRC follows the UNIX philosophy of 'do one thing and do it well', while it's true that it has more features than sysvinit, it does not stay away from its primary function with unnecessary added features.

All configuration is done via shell scripts and symlinks. Shell scripts can then use various specialized utilities to ease the development of init scripts.

OpenRC builds on top of sysvinit and adds some more useful features (like parallel booting) while still the simplicity that sysvinit is know for. Because of this it generally boots faster than other init systems, especially when parallel booting is enabled.

Does one thing and does it well.

Using OpenRC does not lock in a distribution by providing specific NON-POSIX extra services which programs then would rely on.

Basically OpenRC doesn't replace SysV init, but rather works with it, providing features that SysV is lacking while taking advantage of its benefits. It's also used by a fair amount of reasonably popular distros and is well supported and developed.

Uses multi-core and ram very efficiently.

It can be ported to other UNIX and UNIX-like operating systems.

I can add a new startup script for most cases in under five minutes. The ability to quickly insert new applications into the system is a big help.

It always initializes a system the same way; if OpenRC booted and ran a system properly today, it will boot and run properly tomorrow, and the next day.