3 ms·
> Instead of having a simple text format that is the configuration, he encourages everyone to write their own. Uh no, you obviously didn't read the article whe
by zedshaw 16y ago
> Instead of having a simple text format that is the configuration, he encourages everyone to write their own.
Uh no, you obviously didn't read the article where at the end I show you the default format we provide to you in m2sh. I think before you go waxing poetical about something you should learn more about it.
And it's not powerful, it's simple. Take a look at the code that loads the configuration in mongrel2 from sqlite, and compare that to similar C code (also written by me) in the m2sh source to just parse a config file. Code doesn't lie and in this case, parsing a config is a hell of a lot harder than just loading it out of a sqlite file.
- gaius 16y agoparsing a config is a hell of a lot harder than just loading it out of a sqlite file Is there really no library for that? </rhetorical> The usual INI file format has been unchanged since the 80s! [section1] param1=value1 param2=value2 ; this is a comment [section2] param3=value3 And the reason it's stuck around for so long, on every platform you can think of, is it works, it's bulletproof, and everyone understands it at a glance. Anyone can come up with their own scheme, then you end up how it is Javaland right now, where the "application" is just a runtime for the application written in a custom one-off language which is the 10,000-line XML configuration... Anyway, the people who get called at 3am when production is down won't thank you for introducing yet another config file format.
- tef_ 16y agoYou missed the bit where I said having a standard way of calling a script would be an improvement. (and The bits where I asked how you would deal with keeping them in sync) (and I missed the bit where you said m2sh was the default format, because I can't find that anywhere but in your comment here).