4 ms·
HN users pride themselves on finding the least capable tool for the job that only just works for the task but no more. It’s not about logic or practicality. It
by Gigachad 4y ago
HN users pride themselves on finding the least capable tool for the job that only just works for the task but no more.
It’s not about logic or practicality. It’s that they feel some kind of mental pain using Postgres as it is too “bloated”.
- doodlesdev 4y agoTo be fair, if you were to consider yourself an engineer (which I imagine many of HNers would) that's essentially your whole job, overall what you want is to get the requirements fulfilled with the least complexity, cost, time, etc. If deployment difficulty or hardware usage is a consideration in the requirements then it makes sense to try and use a lighter-weight "serverless" database (SQLite doesn't use a client-server model, so it's serverless, got it??? I'll see myself out).
- throwawaylinux 4y ago"Anybody can organize their data, but it takes an engineer to barely organize their data."
- russelg 4y agoOr maybe its because SQLite is just... easier to deploy? Cheaper? There are many reasons to choose it over a "fatter" solution.
- somsak2 4y agodefinitely not easier to deploy, at least if you're talking about how most people build software these days (what sqlite managed service are you familiar with? for mysql or postgres there's hundreds of companies offering this)