@mia @lucy @arcana >a system that’s good for productive tasks is a system that gets the hell out of my way and does its damn job.
OpenRC has never 'gotten in my way', quite the opposite I've never interracted with it once besides adding a couple new services at system boot. Syntax is easy to remember and it does one job.
>the idea of an “init” is antiquated unix garbage.
Genuinely what? This means nothing, an init is just a program/method used for system boot. It's not an idea that can be antiquated, you'll always have to start certain programs at system initialization.
>yes it does have to do more than launching shit.
like?
>which is what this does. for instance, it doesn’t matter that my disk setup is a messy pile of luks and stacked dm targets; systemd will figure out the correct sequence to unlock and mount everything. i didn’t have to tell it what to do. i also didn’t have to implement scheduling in several software projects because systemd user services/timers handle the task’s complexity adequately.
Nothing you say here isn't done on OpenRC or any other init system for that matter. Are you implying encrypted disks cant be utilized on OpenRC?
TL;DR you just said 'systemD is productive because it doesn't do much, also it does lots of stuff like (Lists stuff every init system does)'