5 Aug 2003 mwh   » (Master)

chromatic: While I see your point about not using XML for config files, I like the fact that for just about *any* application on Mac OS X you can just type "open /path/to/pref.plist" and hack about in Property List Editor. I don't want to have to remember what silly adhoc format any given application has chosen to use.

Actually *looking* at the XML is right out -- but that should always be the case, no?

Some of the talks at EuroPython made me a little bit more interested in XML. People obsess a bit about the angle brackets, which is missing the point. AFAICS, the right viewpoint is that it's a standard for structured data. On one level, it's not much more exciting than ASCII.

(Edit: and of course, if you're a command line junkie, there's defaults(1)).

(Edit^2: etrepum: yes, I knew that. I'm not sure what your point is. *My* point, if it wasn't clear, was that having a structured format for config files is nice, and that an XML format is a reasonable way of doing that. NeXT plists would be fine, too).

(Edit^3: retract a silly bit of Edit^2)

Latest blog entries     Older blog entries

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!