(Me not taking this seriously)

I personally find Postgres WAY easier than SQLite simply because of the deployment story. I do a lot of hotfixes and dangerous stuff on personal projects, and having two databases complicates that tremendously. I like being able to run hot code on prod.

For the record, this is not the same reason I like postgres for actual production code

▲

nasretdinov a day ago | parent [-]

Sorry can you please clarify what you mean by having two databases? You can share the same SQLite between applications if you really want

▲

kelnos a day ago | parent | next [-]

I think they mean that they actually do need Postgres for some of their projects, and it's easier to just use Postgres for everything, than to use Postgres for some things and SQLite for others.

	▲	nasretdinov a day ago \| parent [-]
		Yes, but on the other hand what I'm implying is that you might not actually need it :)

▲

sroerick a day ago | parent | prev [-]

Yeah, I mean I guess I could technically connect to the remote SQLite server on my production server. You're right. But I've never done that and that's just not the pattern people use on SQLite

	▲	nasretdinov a day ago \| parent [-]
		Well, no, I don't think you should be doing that :)