This is a good reply. I want to clarify why I excluded SQLite in that list: It is not a database server (all of the others are); it is an embedded database. I say that with zero disrespect. I am 110% a SQLite fanboi. Honestly, I have no experience with PosgreSQL, but I have heard a lot of good things about it. The community looks amazing.
> I want to clarify why I excluded SQLite in that list: It is not a database server (all of the others are); it is an embedded database.
Agree. The confusion probably comes from the fact, the SQLite programming language interfaces still have the "connection" abstraction.
Also, it would be great if there was a simple way to simply "load this entire database into memory". Its not too difficult to manually copy tables, but its much slower than it could be. Even a smallish ~250 MB database was taking like 30 seconds to copy row-by-row.
What you're saying (and what the author is saying) however is clashing with the reality of so many developers using sqlite and being happy with it.
I'd suggest to rewrite it another way:
> Bazillion of developers think they'll need a full-fledged database for their new project while sqlite will cover most of their needs.