A blog post makes the case that GnuCash's database schema is not a technical decision — it's a historical inheritance.
The post frames GnuCash's data model as a path-dependency story: accounting conventions established by Spanish merchants got baked into the assumptions of modern bookkeeping software, and nobody questioned them because they always worked well enough. The argument borrows the structure of the "horse's ass" origin story — the folk claim that Roman chariot widths eventually determined railway gauge standards — applying it to open-source accounting instead of civil engineering. It made a small but engaged dent in developer circles, drawing 30 upvotes and 18 comments.
Path-dependency arguments in software usually target APIs or file formats. Turning the lens on accounting primitives is a less common move, and it matters because the fix is harder. A bad API can be versioned away; a data model embedded in decades of double-entry bookkeeping convention is closer to load-bearing infrastructure. If the argument holds, GnuCash's schema isn't a design flaw — it's a fossil.
GnuCash has been in active development since 1998 and remains one of the few serious open-source personal finance options. Whether or not medieval Spanish merchants deserve credit or blame, the broader point is hard to argue: accounting software is among the most convention-bound categories in tech, and open-source projects rarely get the luxury of starting from first principles.