It's actually commonly used in production for certain types of databases. SQLite is not a replacement for something such as postgresql but it certainly has it's use cases.
The use case for SQLite isn't high traffic public facing webpages. Here is their own list of 'famous' users: https://www.sqlite.org/famous.html
Every iPhone, and Android phone have SQLite running on them, which easily makes it the most used production database. It's use case is typically very low traffic websites or as client side storage.
Maybe I'm missing something but is Mongo in use on the client side in that same way? If not then SQLlite is being shoehorned into the discussion and the context in which production was used should be clear. I feel like people are trying to be technically right instead of following the actual discussion. I never meant client side software and definitely didn't mean someone's micro traffic blog, where a toy database could be used.
It is interesting how much penetration SQLlite has on the client, though.
At any rate, I know better than to not be extremely specific so I brought this on myself.
It seems like there have just been some assumptions going both ways.
This all started when someone trashed RDBMS for being "heavy", implying that Mongo is good because it's light.
Why would you care how heavy a DB is if it's not on the client side? The kind of memory and storage you need for even the heaviest popular RDBMS (MySQL?) is still low enough that's nearly free to create a small app.