As a user you probably don’t know, and maybe don’t care.
This is more for developers, technology is not magic, vendor/technology-locking can be problematic. It’s not like systemd was made by bad people with bad intention. You may have heard of X11 too. The list could go on, there is a big amount of legacy in our technology, some would just keep it that way. But some argue for changes thus discussing (and criticizing) those legacy, why it fails on some points and what to do/build from that.
So right now if you’re a desktop user, I don’t see why you would bother indeed. This discussion are still interesting to some devs, for instance here I learned about dinit, and it’s code is damn small and clean, hence it was informative and I will definitely try it.


Yes and no, I said “devs” and you come saying “actually […]” but really people “integrating” software “usually” are developpers. If you want to start a web server you will have to deal with systemd. If you want to check logs, you will also. If you need to debug an application that crashed (in C at least) in a production/test environment (not in “my machine”) you might want to get into core dumps.
Really? In what universe are you living? Any piece of software I built, professionally or not, had to run on debian-based or arch-based linux hence systemd. Did I choose or any fellow developers of my time? No, maybe people 20 years ago, maybe… That really reminds me of conservative views on “social contract” like we all chose the society we are living in.