https://sqlite.org/copyright.html https://sqlite.org/copyright.html Public domain. No "copyleft" license needed Being written in a small, fast, "old and bori

https://sqlite.org/copyright.html https://sqlite.org/copyright.html Public domain. No "copyleft" license needed Being written in a small, fast, "old and boring" language may be part of what makes SQLite apealing. Another (related) part may be the thoughtfulness and carefulness of its author, e.g., "time, attention and testing" The former, i.e., the author's "time, attention and testing", may matter more than the later, i.e., the author's language choice As suggested by the top comment, in effect the author's language choice, by itself, may not matter with respect to the issue of "safety". If true, then even an "unsafe language" may not reduce the "safety" of SQLite^1 djb's software is also public domain and written in an "unsafe language", mostly the same "old and boring" one as used to write SQLite. Like SQLite it is appealing to many people and is found in many places^2 1. But the thoughtlessness and carelessness of an author, no matter what language they choose, is still relevant to "safety". In sum, "safety" is partly a function of human effort, e.g., "time, attention and testing", not simply the result of a language choice. Perhaps "safe" and "unsafe" are adjectives that can apply to authors as well as languages 2. https://ianix.com https://ianix.com