Re:Why Bloat Is Still Software's Biggest Vulnerability
by Ygg2 on Monday February 12, 2024 @01:48AM
(#39342207)
Here are my underlying assumptions:
- Some set of libraries are fully audited.
- Some libraries can't be fully specced and audited because their specs are in flux (e.g. games, GUIs, webapps)
- Those libraries/apps will limit their maintenance burden by using audited ones
- Package managers are useful.
As long as the set of audited libraries is large or tends to grow large, or the audited libraries build upon each other, or the non-audited libraries depend on many other libraries, the "deeply nested" (I don't think it's deeply nested as much as many dependencies) hierarchy will be replicated.
Re:Why Bloat Is Still Software's Biggest Vulnerability
by whstl on Tuesday February 13, 2024 @08:09AM
(#39357251)
I'm fine with people using single-function libraries if they're audited. The problem is that those are the ones who historically are not cared at all :/
- Some set of libraries are fully audited.
- Some libraries can't be fully specced and audited because their specs are in flux (e.g. games, GUIs, webapps)
- Those libraries/apps will limit their maintenance burden by using audited ones
- Package managers are useful.
As long as the set of audited libraries is large or tends to grow large, or the audited libraries build upon each other, or the non-audited libraries depend on many other libraries, the "deeply nested" (I don't think it's deeply nested as much as many dependencies) hierarchy will be replicated.