Charadon
R. L. Dane 
Tell me a little about it
@RL_Dane Well...
- It's incredibly fast
- Barely uses any memory
- Uses shell scripts to create services, but aren't has asinine as sysvinit scripts are (Runit services are one line, versus sysvinit init, which can get up to 40 lines of shell for a simple daemon)
- Logging is incredibly easy compared to sysvinit
- Works on top of any existing init system if you don't want it to replace the old one outright. Yes, it can even be used alongside systemd.
- Very unixy way of managing services. It's basically just a bunch of symlinks and
touchfiles.
JdeBPThe whole "init scripts are massive shell scripts" was always a bit misleading, although I _have_ seen several lengthy Mewburn rc scripts, especially in the networking parts of the system.
Mewburn rc was designed with a bunch of shell function helpers to cut down on common script code. Even van Smoorenburg rc, in a push to modernize in the early 2010s that was spurred on by the advent of systemd, gained a mechanism for much shorter scripts.
van Smoorenburg #rc was never the thing to compare to. They realized this in the big Debian Hoo-Hah over systemd in ~2014, and almost everyone ruled it out as a reasonable option.
Mewburn rc pre-dated systemd by about a decade and a comparison to it would have ruined the whole "but-but-but look at the long shell scripts!" argument.
So too did comparison to the #daemontools family:
http://jdebp.info/FGA/run-scripts-and-service-units-side-by-side.html