4 ms·
To me this means two things: SQLite's testing has been so effective that most remaining bugs are probably consolidated to a specific category, and yet SQLite is
by lifthrasiir 5y ago
To me this means two things: SQLite's testing has been so effective that most remaining bugs are probably consolidated to a specific category, and yet SQLite is not free from such bugs and C is to blame.
- Dockometer 5y agoThat seems accurate. A fair critique of C in sqlite would also question whether C is a key factor in sqlite's success. I don't know the answer to that, only that "X hinders" has to be weighed against "X helps".
- lifthrasiir 5y agoYes, I would say it was still an excellent choice for SQLite to use C. Still we are increasingly questioning the tradeoff offered by C and the case of SQLite gives one (strong) data point.
- CRConrad 5y ago> Still we are increasingly questioning the tradeoff offered by C and the case of SQLite gives one (strong) data point. If only we knew whether it is a strong data point pro or contra C.
- lonjil 5y agoNote also that the SQLite devs, chasing 1% perf improvements every year, continually rewrite huge chunks of the entire library, sometimes replacing entire components. Their comprehensive testing ensures that there's no API or ABI breakage, and of course the fuzz testing does catch many bugs, it also ensures that SQLite always has a constant flow of new bugs.