Nonsense. For read heavy content sites Sqlite will obviously perform better.

That depends on the read patterns. Sqlite doesn't even support some features that will make very simple aggregations much faster on postgres, even with the same indexes.

For purely sequential reads of data from disk, sure.

> it only needs like 16mb of ram by default

TIL. Thank you very much.

I always wanted to invest more time in postgres, but I just find the Windows environment to be clunky when working with it. Like psql isn't supported in a windows environment (last time I check few months ago), and setting up the postgres environment on WSL was quite annoying as you have to figure out port forwarding.

I know setting up a postgres on a local machine directly or even without docker may not be a mature decision, but that is the hacky reason, why I keep going back to sqlite, as it is the easiest solution to get started with a database.

If you're using an IDE, many have DB browsers built right in (all jetbrains IDEs for ex).

But hey, nothing wrong with easy, usually. :)

I honestly started with CSV files and google sheets as my database! People think I am joking but Google Sheet is a zero setup always on database and the API is friendly for basic operation. Also you have built-in version control.

Once I started to feel limited by google sheets, I upgraded to SQLite. I will invest in postgres once I hit the ceilling with SQLite.