What you're saying is technically true, but only because the XML classes are historically also (unfortunately) DOM classes. It's too bad that XML DOM can't be

What you're saying is technically true, but only because the XML classes are historically also (unfortunately) DOM classes. It's too bad that XML DOM can't be made into Transferrables (losing their DOM'iness) in modern browsers and thus usable in Web Workers. I suppose XML isn't that widely used in the browser, so that would never happen. Read the history of XHR and you'll get a fascinating look at how clever teams can slip real innovation into products just by tickling the right business folks' ears. http://www.alexhopmann.com/story-of-xmlhttp/ http://www.alexhopmann.com/story-of-xmlhttp/ > Which is the real explanation of where the name XMLHTTP comes from- the thing is mostly about HTTP and doesn’t have any specific tie to XML other than that was the easiest excuse for shipping it so I needed to cram XML into the name (plus- XML was the hot technology at the time and it seemed like some good marketing for the component).