| |||||||||||||
Remarks about the benchmarkRemarks about the benchmarkPosted Dec 4, 2012 14:06 UTC (Tue) by nix (subscriber, #2304)In reply to: Remarks about the benchmark by HelloWorld Parent article: Langasek: Upstart in Debian
You missed a bit: it's not just that sysvinit is small, it's also that it's almost maintenance-dead. Thus, it is highly unlikely that it contains significant unknown crash bugs. systemd is relatively new and rapidly changing, so its probability of containing unknown crash bugs is much higher.
I treat init like filesystems, and don't use inits that are still changing a lot or only a few years old for anything important. systemd still falls into both categories. In time, it will emerge from them and become mature (i.e. closer to dead :) ) and thus safe to use for real work in the view of paranoid maniacs like me.
(Log in to post comments)
Stable software Posted Dec 4, 2012 20:53 UTC (Tue) by man_ls (subscriber, #15091) [Link] Not just for paranoid maniacs. "Stable" has two meanings: "robust" and "unchanging", and both are highly correlated: software that changes tends to be brittle. When clients say that they want software to be "stable" while it is changing I tend to think to myself "Well, don't change it then".
Stable software Posted Dec 5, 2012 0:33 UTC (Wed) by nix (subscriber, #2304) [Link]
Oh yes. We want it stable! Give us $new_feature yesterday!
Stable software Posted Dec 5, 2012 1:03 UTC (Wed) by HelloWorld (guest, #56129) [Link]
> Not just for paranoid maniacs. "Stable" has two meanings: "robust" and "unchanging", and both are highly correlated: software that changes tends to be brittle.
I don't buy that. There are dozens of projects that prove that it's perfectly possible to develop new features while not introducing regressions all the time, such as Apache httpd, Postfix, PostgreSQL and many others.
Robustness is primarily a result of good design, developer competence, care and good development practices, not of age and lack of changes. Sendmail has had much more time to mature than Postfix, yet the latter has had far fewer vulnerabilities. And BIND 8 was so broken that they decided to throw it away and start over, resulting in the much more robust BIND 9.
Stable software Posted Dec 5, 2012 10:21 UTC (Wed) by man_ls (subscriber, #15091) [Link] I agree; I should have specified "software that changes too fast". In my opinion, stability is a result of developing at the right speed and using good practices.Is there a way to quantify the right speed? Allow me to link my own post about reversible software development. Rushed developments are highly irreversible and always result in instabilities.
|
|||||||||||||