3 ms·
> But the one thing that still really pisses me off about systemd-the-project was the fact that they ate udev-the-project. In my view, that decision was unneces
by Blikkentrekker 5y ago
> But the one thing that still really pisses me off about systemd-the-project was the fact that they ate udev-the-project. In my view, that decision was unnecessary and was done for purely anti-competitive reasons.
Such are all the common criticisms on systemd.
It was never a technical objection; it was a political objection to the fact that systemd unnecessarily coupled things that could and should be separated, but were coupled not for technical reasons, but for anticompetitive ones, and this goes beyond systemd.
Many Red Hat projects have a way of finding themselves to be dependent on one another in ways that are often hard to justify from a technical standpoint, and often even use unstable, undocumented interfaces that they make available for one another.
- kaba0 5y agoHow about the technical standpoint of having loose coupling everywhere is bug prone and hard to maintain? Will you create a public API that you will break at each update? That’s not too different to what is the state now. Should you carry around 10 years old baggage APIs or what exactly would you propose?
- regularfry 5y agoUnnecessary coupling of components is a technical objection. It's poor engineering, and that criticism was framed by systemd supporters as political.
- Blikkentrekker 5y agoBy that argument, all criticism of software is technical. The argument is that it's not done due to incompetence, but commercial strategies.