4 ms·

In other words, SQLite is clear evidence that using “modern” tools, “best” practices etc. is not necessary to creating world class software. And other projects

In other words, SQLite is clear evidence that using “modern” tools, “best” practices etc. is not necessary to creating world class software. And other projects clearly demonstrate that using “modern” tools and “best” practices often still result in really bad low quality software. So in conclusion: “modern” tools and “best” practices are empirically proven to not be important when it comes to creating world class software.

dathinab 4y ago
but SQLite IS using modern tools, you could say their VCS is more modern then git. It is just not compatible with a lot of git work flows due to being focused on workflow not working well with git. It is also following modern best practice like: - use the best tool for the job (i.e. not git or GitHub) - consider upfront how the project can long term be maintained (i.e. realize that you don't have resources to manage/moderate an public issue tracker/PRs and that you don't want to delegate this work to 3rd parties you barely know) - keep things simple, i.e. no global exclusive write lock and serialized isolation level (instead of subtle race condition and/or fork the work handling etc.) - test a lot, use fuzzing etc. - limit features to you targeted use-cases to keep complexity in check (maintainability, bug avoidance) - opinionated code style, formatting - clear cut well defined dev/contribution flow (for the few which can contribute directly) I.e. if we ignore superficial modern best practices like "use exactly this tool" I don't know which modern best practice it does not fulfill(). Through some are not fulfilled in the way people are used to. (): Ok, maybe they don't keep to: Prefer languages with more guard rails as far as possible. Through due to their targeted compatibility/portability C is kinda the only option.

dathinab 4y ago

but SQLite IS using modern tools, you could say their VCS is more modern then git. It is just not compatible with a lot of git work flows due to being focused on workflow not working well with git. It is also following modern best practice like: - use the best tool for the job (i.e. not git or GitHub) - consider upfront how the project can long term be maintained (i.e. realize that you don't have resources to manage/moderate an public issue tracker/PRs and that you don't want to delegate this work to 3rd parties you barely know) - keep things simple, i.e. no global exclusive write lock and serialized isolation level (instead of subtle race condition and/or fork the work handling etc.) - test a lot, use fuzzing etc. - limit features to you targeted use-cases to keep complexity in check (maintainability, bug avoidance) - opinionated code style, formatting - clear cut well defined dev/contribution flow (for the few which can contribute directly) I.e. if we ignore superficial modern best practices like "use exactly this tool" I don't know which modern best practice it does not fulfill(). Through some are not fulfilled in the way people are used to. (): Ok, maybe they don't keep to: Prefer languages with more guard rails as far as possible. Through due to their targeted compatibility/portability C is kinda the only option.