5 ms·
This is an external audit. Why would Linux activity make a difference here? Are you theorizing that the churn causes bugs?
by ori_b 2mo ago
This is an external audit. Why would Linux activity make a difference here? Are you theorizing that the churn causes bugs?
- tosti 2mo agoWhen more code is written, more bugs are written. Or, if the act of debugging is removing the bugs from software, then the act of programming is to put the bugs in the software.
- gnoack 2mo agoYes, "en-bugging" :)
- ssl-3 2mo agoI think "embuggening" has better cromulence. Use it as a verb, like embiggening. :)
- Gud 2mo agoNot necessarily. Depends on the quality of the code being written. Quality*Quantity
- Brian_K_White 2mo agoYes necessarily. Always. You need to invoke Nasa and fighter jets to find anything coming close, and they only manage to do any better by massive brute overkill in standards & procedures.
- t-3 2mo agoThere's no plausible level of quality that reduces bugs to zero. More lines being written means more bugs being written, that's a statistical fact.
- throw-qqqqq 2mo agoThe Linux kernel is generally much larger than OpenBSD which is quite minimal. But I do agree with you - not directly related to activity.
- dcrazy 2mo agoAs another commenter said, number of bugs increases with lines of code changed.
- throw-qqqqq 2mo agoI completely agree with that
- rootnod3 2mo agoAnd some code is absolutely unnecessary. Look at the yes command. GNU version is optimized to death for no reason at all[1]. OpenBSD's version is as simple as it gets[2]. [1]: https://github.com/coreutils/coreutils/blob/master/src/yes.c https://github.com/coreutils/coreutils/blob/master/src/yes.c [2]: https://github.com/openbsd/src/blob/master/usr.bin/yes/yes.c https://github.com/openbsd/src/blob/master/usr.bin/yes/yes.c
- ptx 2mo agoJust as another point of comparison, FreeBSD's version seems somewhere in-between. It also enables a Capsicum sandbox before processing any data, akin to what the OpenBSD version does with pledge. [1] https://github.com/freebsd/freebsd-src/blob/main/usr.bin/yes/yes.c https://github.com/freebsd/freebsd-src/blob/main/usr.bin/yes...
- rootnod3 2mo agoDifference is that capsicum is after the fact and mostly about file descriptors. You need to open them in advance and _then_ call capsicum. But it does nothing about syscalls. Capsicum is really nice if you plan ahead, but pledge/unveil is easy to drop into any existing code base.
- dwroberts 2mo agoLinux is a much larger project receiving changes to tons of systems from lots of different sources. The combined behaviour of those things working together is massively harder to understand and test. Copyfail being introduced by an optimization made to some random crypto module is a good example of this.
- asveikau 2mo ago> Are you theorizing that the churn causes bugs? Seems to be the case. How many times do you see a bug investigation and it's determined when the bug was introduced? Do you ever look at the diff that introduced it to understand what was going on in the project at the time? Often, it's in service to a new feature. Sometimes the original change is questionable when you consider you traded it for a severe bug.
- ImJamal 2mo agoIf you add 5 new pieces of hardware support in Linux vs 1 new in OpenBSD, I would expect more issues in Linux.