Originally posted by aht0
View Post
The statistical correlation between LoC and bug count are based on older coding methods. More modern with correct test casing and auditing code the large code base can equal lower bugs. You have to have lines of code to put that stuff in.
Originally posted by aht0
View Post
There is a reason for glibc and its horrible. Linux kernel header files are not always libc netural. They are meant to be but they are not always. They are tested always with glibc.
Next is the quriks between the different libc.
So supporting more than glibc equals a lot more workload..
Originally posted by aht0
View Post
Choosing not to use glibc on the Linux kernel does bring some serous problems that need serous resources to address.
Originally posted by aht0
View Post
Originally posted by aht0
View Post
Originally posted by aht0
View Post
So there has been a very big problem for a long time of distributions kitchen sinking the init system. Yes systemd as a single package when it does not need to be is just another example of this on going problem.
Originally posted by aht0
View Post
Originally posted by aht0
View Post
Originally posted by aht0
View Post
You reminded me of this poster. Tradition "Just because you've always done it that way doesn't mean it's not incredibly stupid."
KISS Principle has come a Tradition. Sel4 code audit process broke that tradition and proved that by going more complex you could audit the code base faster and more exactly than a human could.
Originally posted by aht0
View Post
Originally posted by aht0
View Post
Originally posted by aht0
View Post
Originally posted by aht0
View Post
Originally posted by aht0
View Post
Big change that systemd does is making sandboxing around services the normal.
Insecure mess that sysvinit is with more parties running with high privilege than systemd was not good. Yes systemd is more complex but the complexity is what is required to address a KISS caused disaster of being too simple.
Originally posted by aht0
View Post
Leave a comment: