> What features postgres offers over sqlite in the context of running on a single machine with a monolithic app
The same thing SQL itself buys you: flexibility for unforeseen use cases and growth.
Your SQLite benchmark is based in having just one write connection for SQLite but all eight writable connections for Postgres. Even in the context of a single app, not everyone wants to be tied down that way, particularly when thinking how it might evolve.
If we know our app would not need to evolve we could really maximize performance and use a bespoke database instead of an rdbms.
It seems a little aggressive for you to jump on a comment about how it’s reasonable to run Postgres sometimes with “SQLite smokes it in performance.” That’s true, when you can accept its serious constraints.
As a wise man once said, “Postgres is great and there's nothing wrong with using it!”
I did Ctrl-F on "proof-of-work" in this thread to see if anyone had tried this, you seem to be the only one. Seems like a good precaution before sending even a verification email.
Did you have to roll your own or was there some proof of work library you were able to use?
Your pubs kindly return the favor when we order whiskey. As Hunter S Thompson is reported to have quipped in a bar your side of the Atlantic: "What is this, a sample?"
Personally I'd have us use what the Royal Navy used to serve its rum ration in, the half-gill. This is 1/8 of a British pint or 71 millilitres, and the rum would have been a minimum of 54%!
Fractional gills were the pre-metric shot measure in the UK, but they were still pretty stingy. 1/6 gill in England, 1/5 or 1/4 gill in Scotland, and 1/4 gill in Northern Ireland.
The place where I bought my knife offered a sharpening class and sold stones. It’s meditative to sharpen, keeps your knife in good condition (vs mechanized commercial sharpeners) and saves money (vs outsourcing it). But I don’t see these classes offered much. There are good tutorials on YouTube, if that works for you.
I’ll also say, “big” is not so important past a certain point. I have a 10 and am generally very happy with it but you do need to clear more space /above/ your cutting board the longer your blade is.
And if someone is buying their first chefs knife they generally (as you correctly note!) will want a larger cutting board than they likely have now. So having a super sized blade (vs a more reasonable 8) amplifies the extent you will need to learn to tidy up and clear space before and while prepping (chopping).
Despite the tech layoffs and rise of AI, programmer hubris is alive and well, that is heartening.
Here we see three engineers writing — at length! — about a hugely complicated matter of law.
No one outside your bubble cares what you think. You are unqualified and your opinions irrelevant. You might as well be debating open heart surgery techniques.
> they have to couch it in language clarifying that they would love to support war, actually,
Yes they do because they are trying to sell to the Department of War.
No one made Anthropic try to be a military contractor. It’s pretty much the definition of being a military contractor that your product helps to kill people.
The same thing SQL itself buys you: flexibility for unforeseen use cases and growth.
Your SQLite benchmark is based in having just one write connection for SQLite but all eight writable connections for Postgres. Even in the context of a single app, not everyone wants to be tied down that way, particularly when thinking how it might evolve.
If we know our app would not need to evolve we could really maximize performance and use a bespoke database instead of an rdbms.
It seems a little aggressive for you to jump on a comment about how it’s reasonable to run Postgres sometimes with “SQLite smokes it in performance.” That’s true, when you can accept its serious constraints.
As a wise man once said, “Postgres is great and there's nothing wrong with using it!”
reply