Distributors ponder a systemd change

Posted Jun 8, 2016 11:22 UTC (Wed) by niner (guest, #26151)
In reply to: Distributors ponder a systemd change by szbalint
Parent article: Distributors ponder a systemd change

If you feel that strongly about systemd's design decisions, feel free to find like minded people and start work on a replacement that's better engineered in your eyes. To stay with your examples: MySQL, despite it's huge success is now losing to PostgreSQL which in my eyes is a superior solution in nearly every regard. PHP is similarly no longer the rising star it used to be. So your own examples contradict your conclusion of lost opportunity.

However, what really will keep a superior solution from appearing, is if you never start building it.

to post comments

Distributors ponder a systemd change

Posted Jun 8, 2016 11:35 UTC (Wed) by szbalint (guest, #95343) [Link] (1 responses)

How long did it take for Postgres to displace MySQL? That's the opportunity cost.

(sidenote: I don't think the "why don't you do it better, then?" response is reasonable. Recognising that a situation is bad and being able to fix it are two different things.)

Distributors ponder a systemd change

Posted Jun 8, 2016 11:39 UTC (Wed) by niner (guest, #26151) [Link]

If you don't know what a better solution would even look like, how do you know that the current one is bad? How can you talk about "questionable design decisions", "borging stuff", "increasing the monolithic complexity", and things that "might start breaking pretty badly" if you don't know how to improve it?