I am not sure why debian needs to force replace sysvinit, can't they have systemd-debian distro that will have all the shiny stuff in it? and maybe have it grow and if it won't go down with their userbase then they can discontinue it? Everyone moving to systemd seems a bit fishy. C is very insecure for daemon coding with all other options why no use go for example? There might be some influence on behalf interested governmental parties giving a push to systemd. I don't have a problem with systemd its just I think it should have been an option not a default for server setups.
C programs if they are not really carefully coded can be easily hacked by stack smashers, race condition inducers etc.
I am not sure why debian needs to force replace sysvinit, can't they have systemd-debian distro that will have all the shiny stuff in it? and maybe have it grow and if it won't go down with their userbase then they can discontinue it?
Go read the arguments, there are many reasons why they decided to switch. A big part of it is that Gnome/KDE and other upstream software is already dependent on systemd, so keeping SysV means extra effort to fix that.
C is very insecure for daemon coding with all other options why no use go for example?
What do you think the current init system is written in? That's not a reason to keep sysv.
https://www.youtube.com/watch?v=fwcl17Q0bpk