“Basically” is the key word here, because the details can well differ.[b]Basically all distributions have the same needs
I don’t and luckily Gentoo does not force me to.I don't know how hard the dependencies on the kernel version are, but typically, I am using a recent version anyway - whatever Gentoo declares stable.
Here systemd adds restrictions which aren’t in Gentoo. It even requires me to add selected kernel features which I would not need otherwise - and I would not be able to opt out, because leaving them out would not just cost me some pretty graphics or cause some flickering. It would stop my system from booting at all. That’s a real hard blocker. And this moves in lockstep with features they provide which some other program might depend upon - even though the other program does not require that kernel feature by itself, so not updating systemd would stop me from updating bigger and bigger parts of my system.
You already got into that situation yourself with Gnome dependencies on systemd. Now imagine what happens if systemd requires something you really do not want.
And as I quoted Lennart in my blog, they actually state publicly that their intention is to “gently push everybody” - in this case to use the kernel versions and configurations they want.
Can you trust a central, single source of control?
Since the systemd developers claim themselves that what they do requires Linux, it is likely very hard to untangle systemd from Linux. Also they would be coding against a moving target, because the systemd developers do not care about other kernels - and coding against a moving target is a recipe for disaster.Then, nobody stops people from porting systemd to other kernels, keeping the APIs intact.
Wouldn’t it be nice if one could reuse the knowledge about the package manager and the desktop when switching … uhm… the pretty logo?Wouldn't it be nice if one could reuse the knowledge about init when switching distributions?*There is still package management and default desktops distributions can argue about