05/19/2020 (Tue) 15:46:18
I actually don't have much of a problem with the "bloatedness" but the ever-expanding scope is just cancerous thinking and I don't even know why it is allowed. We want to add some additional semantics to how we run binaries and we want to write declarative configuration files - fine, do it, but you have to stop somewhere, like, there should be a place where we design things and where we decide what to do and what not to do. Honestly it just makes me think that the bazaar model fails here instead of the cathedral one.
>b-but it werks
It doesn't. Look at all the "features" systemd provides. I'm guessing more than half of them just don't work (if you want an example, my beef was with wake-on-lan preparation of network adapters) and it works for your paticular use case because you don't stray off the beaten path too far.
>but it still provides a way to add shell initscripts and whatnot
It does, but why would I use the systemd then if I can use old and tried initscripts? Why should I double my work on configuration or try to debug some obscure edge-case in a million LOCs work? No thanks.
Saying that though, for an end user it doesn't really matter as long as they don't do anything and stick with the distro default. Nice fucking new Windows we got here, I actually cannot wait for Linux to crumble already. There are tons of bugs in the kernel nobody fixes because not enough manpower and because it's actually hard, way harder than even 10 years ago. I would go to *BSD but using unix-like systems made me realize I don't like Unix that much. Time to look for a meme OS or to write one myself.