Yet another systemd fiasco
Yet another systemd fiasco
Posted Nov 19, 2014 12:38 UTC (Wed) by hunger (subscriber, #36242)In reply to: Yet another systemd fiasco by alankila
Parent article: Russ Allbery leaves the Debian technical committee
I seriously doubt that the free software community can agree to something complex as an API for an entire init system. That works if somebody steps ahead and just does something, like the systemd developers did.
Sitting down and discussing the issue and then trying to shoehorn sysv-init and systemd into the same API will never work. So either people fight through the push-back or we stick with sysv-init. That lasted as long as it did because nobody wanted to do the fighting.
Kudos to Lennart for pushing ahead of the status-quo where many have given up before him.
Posted Nov 19, 2014 15:21 UTC (Wed)
by ebassi (subscriber, #54855)
[Link]
we did agree to a protocol, unless I dreamed about this whole specification, and the discussion that led to it. to be fair, my life would be happier if that specification did not exist in the first place, because it has brought nothing but abuse — in terms of user interaction; toolkit API; and actual abuse from developers and users alike. what both KDE and GNOME could not agree on was a new specification to supersede the one that is currently existing, and (mostly, barely) working.
Did you take a look at KDE/Gnome? They can't agree on really basic things like how to embed a systray icon!
Yet another systemd fiasco