It doesn’t necessarily follow that because Postgres is “fully utilised” it is hitting “hardware maximum”, or even that it’s not bottlenecked on contention.
As an example, spinlocks can push CPU usage very high whilst being an obvious symptom of contention.
> I've invoked it in my job mostly to explain to younger developers why learning vim keybindings+terminal git usage
Interesting - I see it as the opposite: learning the git CLI is pointless. It’s slow, clunky and it doesn’t teach you any of the very interesting inner-workings of Git.
There are much better things to spend time learning, especially if your editor has a native git integration.
US card fraud rate is significantly higher than in the EU. In 2015 it was about 0.042% in the EU, vs 0.1388% for the US. The 2021 rates for the EU fell to ~0.028%.
You get nervous about giving your card to a waiter because you’re in a foreign place with a nonsense payment system worst than most developing countries and it’s not something you’re ever asked to do anywhere else.
> New user registration was stopped on June 11 and then re-enabled after the project added Anubis to try to foil the attacker's mass account registrations. That did not work
This confuses me - why would a proof-of-work anti-scraping system like Anubis prevent registrations?
> As a discussion regarding if it’s ethical to ignore restrictions progresses, the probability of someone bringing up a famous case where someone ignored unethical restrictions approaches one
Seems reasonable to me. Substitute Rosa parks with another example of unethical restrictions if you wish - there are many.
Was Rosa Parks unethical for sitting down on a bus?
The point is that the context matters: both the users context and the context of the restriction. It’s not as clear cut as “ignoring restrictions = bad”.
The restriction itself can be unethical, in the same way that bypassing a restriction can be unethical.
I wrote something similar with go, but MacOS only.
Creating a worktree became instant, but the bottleneck shifted from that to git needing to build its index. Claude code runs `git status` in the background, meaning any speed gains are instantly gone.
> The caveat is that Litestream replication is asynchronous. A restore can miss the newest local writes if the SQLite volume disappears before they are copied. That is fine for many AI and experimentation workflows
In short: SQLite is not all you need, unless you’re just experimenting don’t actually care about durability, in which case you also need litestream + object storage.
As an example, spinlocks can push CPU usage very high whilst being an obvious symptom of contention.