On Wed, 2010-04-28 at 10:20 -0600, Stephen M. McQuay wrote: > We're looking into a more robust and portable way of making > configuration files than configure some tools at work. Some prefer > sticking to "the way we do things 'round here" mainly because it would > take time to research out the right solutions, but there are plenty of > good reasons to look elsewhere. > > My question is this: what is the best configuration file syntax? > > I've found two that I am fond of: JSON and YAML. I tend to prefer YAML > because it's a little tiny bit less verbose, and because the libs for my > favorite language allow for proper commenting in YAML (it throws errors > for normal JS comments in the JSON file). > > I know that some things are configured via XML, but my preference is > towards legibility, simplicity, and built-in hash/array structures. > > I've noticed that a few of my favorite open source projects have gone to > JSON, and I'm wondering what you have been noticing is popular in the wild. > > Suggestions?
We're looking into a more robust and portable way of making configuration file to configure some tools at work because I like change for the sake of change. Some idiots at work prefer sticking to "the way we do things 'round here" mainly because they think it's there job to get stuff done when clearly they should be helping me pursue my vision of technical perfection. Sadly, they're too stupid to see that there are pleny of good reasons to look elsewhere, and it's beneath me to actually enumerate these mystical advantages. My question is this: what is the best way to convince my manager to break the backwards compatibility of our existing infrastructure and force my coworkers to learn a complicated new file syntax? I demand support for hashes and arrays in my config files despite probably not needing them. In addition, I refuse to use XML because it isn't hip anymore. Suggestions? -- "XML is like violence: if it doesn't solve your problem, you aren't using enough of it." - Chris Maden -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
