| Dependencies may be becoming less properties of software, and more so properties of the distro's systemd wiring. More and more software will assimilate systemd features. Free distros will patch, shim, emulate, flounder. Or in GPT parlance "Dependencies are no longer intrinsic properties of software; they are emergent properties of a distribution's systemd orchestration layer" Meanwhile, gripes, fears etc, 'Linux' becomes interpreted vs inspectable. Requires superfluous new literacy Convolutes logs, tools
Obscures causality Centralized control above Unix process model Fair well ps aux, hello systemctl, cgtop, gls KILL (less lethalized) superceded, replaced by service stop and mask Surrender chains for events, ie buggy debugging or complexity accretion General obfuscation beneath the hood Centralized ... indexed, logs vs text streams And.... Upstream assumes systemd Some resist Costs rise Optional becomes expected Accidental incompatibility And... systemd ingurgitates one by one, policy, supervision, logging, identity, dependency management and the rest of the world... digests it, and from the aether emerges a sweet smiley face, disgorging forth a monolithic mutant avatar, with Linux features. I'll be quiet happy to be wrong about everything. Feel free to slaughter everything I've written. I don't even oppose systemd - I simply perceive it as a singularity that's drawing everything around me towards it. Wrong would definitely be good, so please don't hold back. I won't seek pardon for the rant though, because true or false, it's honest. Edit: I was reading through my threads and thought the parent was asking me, though wasn't. I've unintentionally barged in here, but I'll leave the comment anyway, as it references a very big concern of mine. |