Making Sense of Why Systemd Created in the First Place
The real worry here is that Free Software has proved itself vulnerable to Embrace, Extend Extinguish techniques. That’s all Poettering and Red Hat have done, and it’s working.
You know, I’ve been thinking a lot about that, these days. That RH is pulling a Microsoft on the Free Software community, their “Open Source” won, and the Free Software is being kicked to oblivion.
And, something that was born as a counter, to the dog-eat-dog world of proprietary software, is becoming the same thing it was created to fight against…
How many times have we seen the argument that for Linux to succeed on the desktop it should all be consolidated into one unified distro, with everyone working for a common goal, rather than have the fragmentation that currently exists. The argument always comes from short term Linux users, or non Linux users, that have no grasp of the historical reasons for, and methods used, to maintain freedom of choice within the Linux community. All their experience, and thus their opinions, are based on the MS/Apple corporate models; these being the only ones most of them have actually encountered. These are the same folks that welcome systemd with open arms. It is the magic app that will bring about distro consolidation. The fact that their version of a “common goal” is a rather communistic approach that hampers individual freedom of choice, which is certainly not the “common goal” of those wishing to maintain their freedom, seems to completely escape their grasp.
Thanks to Ubuntu, those of us who were already long time Linux users long before Canonical raised its ugly face, are now outnumbered by those that haven’t the knowledge or experience to grasp, or begin to comprehend, the danger that forced consolidation of this type brings. Put systemd on all the various distros and they all effectively become Red Hat clones, regardless of the packaging systems they may each employ.
KDE Will Depend on ‘logind’ and ‘timedated’ in 6 Months | PCLInuxOS forum