OTOH, it eliminated discussions/arguments about what format to use. In a corporate environment, that can be a significant win in and of itself. (Yes, "win" should be in quotes.)
Your "combinations of grep, sed, awk, perl" will corrupt your data if your file happens to contain any CDATA, entities, unexpected formatting, processing instructions, etc.
Don't get me wrong, sometimes a quick hack is worth the risk. But it's certainly no reason to defend XML, which is what put you in the position where a quick hack was your best option.
So the impression he gets is, XML is going to add value to everything it touches. Most developers like me have no say in that at all, we have to just use it.
I prefer the hack to get it just done. But agree with you, none of that is a permanent solution.
This is better than spending next 5 hours writing a Java program to do it. Its not a permanent solution, but either way that Java program and the shell hack are both going to do the very same.
I would rather use the shell and do it, rather than spend the next 5 hours with Java and eclipse.