@sun @grillchen @lucy It's Go. I actually would have written it in C but it is easier to port Go programs from Plan 9 to Linux than it is to do the same for C programs and I've been doing the development on Plan 9; the binaries running on FSE/Screamshitter/Apotheosis/etc. were just built from the same mkfile on the Plan 9 machine. (It'd be "typedef PiDB struct" in C, and I'd be using lower-case letters because fuck CamelCase.)

(I think I'm already pushing it by calling the internal K/V store "the ID Index Orthogonality Table". If I am too whimsical the code will read like Honk's and I like Honk but it is sometimes not as easy to read when all of the words rhyme and differ in only one letter. There was a conlang where the guy had made related words share prefixes, and it turns out that this was a terrible thing: if you make the first syllable of your words for "fork" and "knife" and "spoon" the same, it makes it less fault-tolerant. No one hears "fork" and thinks you might have said "knife", they sound and look very different from all of the other words that might be used in their place in a given context. It's fine that a fork on the table and a fort on a hill sound similar enough to be easily confused because you do not usually use them in the same context, same reason "hashi" is "bridge" and "chopsticks" in Japanese. Like words have a local optimum for avoiding ambiguity. I think Honk's readability kind of suffers from zonking its donks throughout the codebase.)