121 karma · joined August 26, 2025
Pity the fool who can't taste the difference between any of these.
I maintain my own private fork with some small modifications which I started polishing up this week to release it for a talk that I'm preparing.
The project I'm using this on is an ecommerce site [0] written in 100% Ur/Web with a hand-rolled backend ERP system written in PHP (not by me) which I am slowly replacing bits of with new Ur/Web code. As of today, we have 22223 lines of Ur/Web code, weighing in at 701 KiB.
I think this is a great policy by the Zig team.
Yes, I am someone who, when my branch code-wise is ready to be merged, I will still take however long it needs to clean the history into a coherent, bisectable set of patches.
To be fair, Fossil is kinda cool in many ways, but it's a downgrade for my dev UX. Also the configuration interface for access controls and suchlike to the repo server, issue tracker, etc. is... eccentric. I wouldn't be surprised to find some incorrectly/unsafely configured repos in the wild.
> [...] would be roughly proportional to the strength of the friend network connecting them.
> Not sure if tools and technologies can solve accidental complexity.
... and then say
> For me, consistent systematic naming and prefixes/suffixes to make names unique are a hint that a person is thinking about this or has experience with maintaining old systems. This has a huge effect on how well you can search, analyze, find usages, understand, replace, change.
I have battle scars from refactoring legacy systems where my predecessors did _not_ consistently or uniquely name things and I would not have seen it through without my sidekick, the type checker!
Also, why would you have billions of open transactions? That is the implication I got from the article as someone who doesn't know anything about Postgres.
(I use SQLite and perhaps I have Stockholm syndrome, but I like how it pushes you towards a design with small transactions, ideally entirely database-side.)
EDIT: Yeah, gptzero says AI with 100% confidence.
Such as that very website? ;)
<quote> Machine learning decode: building on our previous work23, here we apply machine-learning-based decode (see section ‘Reading and decoding data’) to account for noise and inter-voxel cross-talk. </quote>
but also
> Claude Code works great out of the box, so I personally don't customize it much.
Am I the only one to notice the irony of this juxtaposition?
1. doesn't (and won't) munge personal data
2. will be available in 2035
?
> Show me the incentive and I'll show you the outcome.