21–30 of 82 posts
I’m curious, is the prevalence of SQLite similar to how PHP is widely used because it’s behind many WordPress sites?
Couple of major companies like Adobe, Apple, Google, Mozilla use it in their products. That would add up quick. https://www.sqlite.org/famous.html
For niche uses of database I am sure this is true. But if you are not in that niche, then Postgresql is usually a much better choice. For example Firefox uses SQLite, because it wants to store lots of application specific data. It is good for that. Personally, I find the tooling, documentation, familiarity and quality of Postgresql makes it my choice even in situations where SQLite might work.
For niche uses of database I am sure this is true. But if you are not in that niche, then Postgresql is usually a much better choice. For example Firefox uses SQLite, because it wants to store lots of application specific data. It is good for that. Personally, I find the tooling, documentation, familiarity and quality of Postgresql makes it my choice even in situations where SQLite might work.
In terms of installations, sure. In terms of total data, probably not. In terms of important data, 100% not. Important data needs guarantees, and its privacy is second to its longevity. Server side and centralized beats client side decentralized for all but sensitive consumer data.
> In terms of important data, 100% not.
Choosing not to focus upon quantity or quality is likely the reason why SQLite is so popular. It is a lot easier to manage and develop for SQLite than it is to do the same for large databases that require high availability and reliability under heavy loads. There are many more applications for small databases that contain data that is important to the end user even though that data may not be important to anyone else.
Unfortunately, I wish there were multiple implementations of it, and that the file format was documented and stable.
In terms of installations, sure. In terms of total data, probably not. In terms of important data, 100% not. Important data needs guarantees, and its privacy is second to its longevity. Server side and centralized beats client side decentralized for all but sensitive consumer data.
i find it ironic one of the most gatekeepy, closed, walled garden companies in the history of the planet, Bloomberg, is a sponsor of one of the most free most open piece of software ever.
For niche uses of database I am sure this is true. But if you are not in that niche, then Postgresql is usually a much better choice. For example Firefox uses SQLite, because it wants to store lots of application specific data. It is good for that. Personally, I find the tooling, documentation, familiarity and quality of Postgresql makes it my choice even in situations where SQLite might work.
(cf. Daniel Stenberg getting angry emails because everybody and their dog embeds libcurl, sometimes multiple times in the same app)
For niche uses of database I am sure this is true. But if you are not in that niche, then Postgresql is usually a much better choice. For example Firefox uses SQLite, because it wants to store lots of application specific data. It is good for that. Personally, I find the tooling, documentation, familiarity and quality of Postgresql makes it my choice even in situations where SQLite might work.