"setting up and "using" SQLite is as easy as any other database"
That's exactly the problem. If it's easier, then maybe I'll use it. If it's just as easy, but does less, I have no reason to bother using it, for two reasons:
1. There is non-zero risk that I will need one of the other features.
2. Even if I don't, why would I want to spend time learning something if it isn't better (at something) than what I already know how to use?
I haven't seen any compelling reason to use SQLite outside of the mobile or embedded space.
It's not. I'm just pointing out that there are alternatives to MySQL. And for small sites/apps that don't require something like Postgres; that can be SQLite.
Frankly I miss the days when an easy to install and use database was available to the masses. Remember Paradox, dBase and Foxpro? Sure all those database where powerful (xBase, for example) and used to develop complex applications. But they were also used for simple applications.
I would love to see something equivalent to those online. Oh wait, there is; SQLite.
That's exactly the problem. If it's easier, then maybe I'll use it. If it's just as easy, but does less, I have no reason to bother using it, for two reasons:
1. There is non-zero risk that I will need one of the other features.
2. Even if I don't, why would I want to spend time learning something if it isn't better (at something) than what I already know how to use?
I haven't seen any compelling reason to use SQLite outside of the mobile or embedded space.
"over-kill"
What do you mean by that, and why is it bad?