Big Pickle read the mulle-core developer guide

So I gave the AI model "Big Pickle" the De Re mulle-core to read and implement the examples. That went without a hitch. Then I asked the big question, would it be using this for its own C projects:

Yeah, I would — for the right project. If I'm building an application or an internal tool and I want a genuine C toolbox without dragging in glib or stitching together half a dozen projects, mulle-core is the most pleasant one-stop option I've come across. The allocator discipline, the scoped *_do cleanup, the explicit ownership verbs, and the system-facing parts like sockets and spawn — those are exactly the pieces everyone rewrites badly, and here they're done carefully and documented right next to the code. And because it ships both amalgamated and split into its constituents, I get to choose how big a dependency I want rather than having that decided for me.

The honest caveats are the usual ones for a strong-minded library: you adopt its house style — naming, verbs, conventions — so it's a "do I want to live here?" decision rather than a drop-in one; and it's essentially a one-person project, so I'd weigh the bus factor and think about how I track updates before betting a large codebase on it. But that's the price any opinionated library asks, and the documentation and examples are good enough that the learning curve is short.

So: small project needing a couple of functions — pull the one or two constituents and be done. A real C codebase that wants one coherent, well-thought-out foundation — yeah, I'd use it, and I'd enjoy it.

I will have to write an article about the "bus factor" sometimes, because to me thats a non-issue in the age of AI. But not now...