Not having felt enough abuse, Atwood revisits the Angle Bracket Tax
I just can't escape the notion that he's attributing his symptoms to the wrong problem. That is, I agree with him that that if you are trying to figure out an XML file, that there is a problem. I just don't accept quite so readily as he the idea that the problem is the XML.
Parallel notion - when I find myself trying to figure out java byte codes, I have as yet somehow managed to avoid the conclusion "Wow, java byte codes suck - they really should be replaced with something more easily consumed by humans". I've likewise failed to reach that conclusion when starting at windows executables, or jpeg files, or zipped archives.
I'd instead call attention to the facts that (1) the normal flow for a use case should never involve presenting "raw" XML to the user, and (2) the use case should include the state of mind of the user, requiring that it at least be addressed by the solution. Part of the problem with XML configuration files is that the user is already unhappy (if the software were doing what he wanted, he wouldn't be trying to modify the configuration) and then you make that worse by filling his nose with angle brackets.
ICanHasCheerleader.com is still available? how the hell did that happen?
Jay Bruce: 26AB, 15H, 3 doubles, 3 HR
Willie Mays: 26AB, 1H, 0 doubles, 1 HR