I'm glad I could help clarify your FUD. > which is, in essence, a Unix take on the Windows Registry Ah, the windows registry canard. You are the canard king

I'm glad I could help clarify your FUD. > which is, in essence, a Unix take on the Windows Registry Ah, the windows registry canard. You are the canard king man. Let's see you've pulled out djb and windows registry. I think your next linux fear buzzword will be "embrace and extend" or possibly "free as in freedom". That'll really enhance the F in your effing statements. The flaw of the windows registry is not that it wasn't a text file, but that it was a massive monolithic database with all software configurations in it and no enforceable schema that couldn't be examined. Our database is only for mongrel2 and has a solid clean schema everyone can go look at with "sqlite3 .dump". So that's a pointless comparison. And you keep using this word "canonical" where it doesn't apply, so let's use official. The "official" configuration file is loadable into a text file, but again, I think that's irrelevant for the use cases the design targets. Either you're doing your own setup and m2sh with mongrel2.conf is fine, or you're doing large scale automation and the database is better. In my design you get both, plus more choice. In your design you only get the status quo configuration which sucks. Also, if I do m2sh diff it'll be just for fun. Nobody really needs that since most people don't hire Ninjas.