@bodil also #SystemD is evidently a "necessary evil" at worst, because noone accepts #SysVinit boot times measured in minutes!

Interestibgly the same folks hating systemd are loving #LaunchD & #SMF yet launchd is what inspired SystemD...

https://www.youtube.com/watch?v=o_AIw9bGogo

@CursedSilicon @gettie mostly because #systemD (and it's competitiors) took all the right lessions:

• Start less
• Start more in parallel
• Resolve dependencies to avoid waiting times

And basically everyone (#OpenRC, #Upstart, etc. Even #LaunchD [the #init for #macOS that is literally the SystemD but before SystemD and by Apple] and #SMF [#Sun's SystemD for #Solaris] did that to allow for boot times in secinds, not minutes…

https://www.youtube.com/watch?v=o_AIw9bGogo&t=12m17s

@fabiscafe @okapi espechally in the form of an interactive desktop...

• I could see it valid for multiple shell sessions, but #tmux & #screen cover that pretty well.

• If one has to login into different machines then chances are #aithentification is centralized anyway.

Needless to say #modernizations like #SystemD don't happen because people like #Poettering are "hobbyless", but because the preexisting status-quo (#SysVinit) was slow, inflexible and error-prone by strict linearity and non-parallelization.

• With a literal /etc/init file one can literally get a system to hang due to a mistake (i.e. certain call doesn't get invoked correctly), whereas on #SystemD (and competing solutions like #LaunchD on #macOS and #SMF on #Solaris) your desktop / laptop will continue to noot even if it doesn't have a network connection.

Not to mention as Benno Rice explained: 'Shit just gotmore dynamic!': We don't have that one big ass maingrame and serial terminals, instead we have laptops that may he carried around a campus or traveled with all day and that constantly switch between wireless and wired networks and have VPN tunnels open and whatnot...