I think part of the problem is that baffled, frustrated people who are just getting started with XML see something called XML::Simple and think it's the answer to all their prayers.

Hoping that something will be both simple and the "answer to all their prayers" is surely a bit naiive. Take for example LWP::Simple. It certainly provides a simple API for retrieving web-based objects but if the "answer to all your prayers" requires cookie, proxy and authentication support then you've just outgrown the simple API and you have to learn a whole new one. Similarly if/when you outgrow XML::Simple, you need to move up to something offering more fine-grained control, such as XML::LibXML.

Maybe I could/should suggest putting this one particular issue in the POD?

The most common complaint I get about the XML::Simple documentation is that there is too much of it. Seriously. People email me with a question that they strongly suspect is answered in the POD but there is so much POD that it's quicker to email me (or post on PM) than sit down and read it.

But you're right, I could improve the POD's coverage of round-tripping.

And you know what? I just clicked on the link to the XML::Simple::FAQ on search.cpan.org and it's a 404

That is odd. If I go to the main screen for the XML::Simple distribution then the link works. But that's a little bit of a red-herring - why search the web for documentation that's already on your hard drive? Especially when the one you find on the web might be for a different version than the software you have installed