Void Linux vs Red Hat Enterprise Linux

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.

Each released version of RHEL is supported for around ten years by Red Hat with constant bug fixes and security updates.

RHEL favours stability over being up-to date. For this reason it ships with packages that may be up to two years behind in order to ensure stability over everything else.

Using older versions for packages means that they have been thoroughly tested and used in production for quite some time, and are ensured to play well with each-other.

This strategy has paid off quite a lot in the past. One example is the Heartbleed bug which left RHEL unaffected since it was using a two-year old OpenSSL library which did not have the bug.

RHEL has several built-in solutions for disaster recovery. For example, it comes with pacemaker which can be configured to manage multi-site and and stretch clusters across multiple geographical locations for disaster recovery and scalability. It can also be configured to trigger notifications when the status of a managed cluster changes by using enhanced pacemaker alerts.

Since RHEL backports all updates and bug fixes to older versions in order to maintain package compatibility across releases, applications hosted on Red Hat Linux don't have to worry about potential breaking changes in libraries they use, especially language libraries.

This distro is by far the one with the largest number of certified server-class hardware.

Comes with built-in management tools for containers (Atomic CLI, Cockpit) and a container runtime in the form of Docker engine.