11–20 of 82 posts
Have an mvp you’re not sure you’ll ever have more that 2 users - yep.
Storing a little data for an application on the disk and don’t want to write your own schema.
Want to teach someone how databases work without setting up a sever - sure.
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.
It also happens to be a SQLlite3 database. And the same is true for a slew of other applications that (quite rightly) use SQLite databases as their file format.
You might be thinking of things like financial transactions, or medical records, but that's not the only kind of important data there is.
Once that is said, does OSS move forward? Not an inch, good luck getting any change upstream
I’m curious, is the prevalence of SQLite similar to how PHP is widely used because it’s behind many WordPress sites?
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.
This irony has layers. Like an onion.
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.
Amazying piece of code whatever you look at it.
I'd also probably win test to code ratio contest.
I’m curious, is the prevalence of SQLite similar to how PHP is widely used because it’s behind many WordPress sites?
So it's hard to understand which similarity you're asking about, but SQLite is popular because it does one thing, and does that one thing really well, and that thing also happens to be a perfect fit for complex file formats.
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.
Huge SQL for servers is just a different use case.
Someone's temporary browser data or settings for my android alarm app could be just as important and sensitive as an average record on those big servers.
Fortunatelly, SQL fits the role of a small transactional engine very well to support those small use cases for a large number of applications. It deserves the good reputation.
Once that is said, does OSS move forward? Not an inch, good luck getting any change upstream
It's still OSS, you're allowed to fork and maintain Sqlite if you don't like the upstream merge requirements.
https://www.sqlite.org/th3.html see bottom
Personally, I find the tooling, documentation, familiarity and quality of Postgresql makes it my choice even in situations where SQLite might work.