JS JSON vs XML

const json = { name: "Sam", age: 30 };
const xml = "<person><name>Sam</name><age>30</age></person>";
console.log(JSON.stringify(json));
console.log(xml);

const obj = JSON.parse('{"name": "Sam"}');
console.log(obj.name); // one call

const doc = new DOMParser().parseFromString("<name>Sam</name>", "text/xml");
console.log(doc.querySelector("name").textContent); // several steps

const doc = new DOMParser().parseFromString('<book id="42">Title</book>', "text/xml");
console.log(doc.querySelector("book").getAttribute("id")); // no JSON equivalent

console.log(JSON.stringify({ name: "Sam" }).length);
console.log("<person><name>Sam</name></person>".length);

const doc = new DOMParser().parseFromString("<rss><item>News</item></rss>", "text/xml");
console.log(doc.querySelector("item").textContent);

1. Assuming XML is simply worse or obsolete -- it remains genuinely well-suited for certain use cases, like documents with rich structural markup (similar to HTML) or systems with strict, formal schema validation needs.
2. Choosing XML for a brand-new project purely out of unfamiliarity with JSON, when JSON is almost always the simpler, more appropriate default choice today.
3. Forgetting that converting between JSON and XML is not always a clean one-to-one mapping, since XML supports concepts (like attributes vs. elements) that JSON has no direct equivalent for.

• JSON is generally more compact, maps directly onto native JavaScript objects/arrays, and requires no separate parsing library.
• XML supports richer structural features (attributes, namespaces, mixed content) and has mature schema validation tooling (XSD, DTD).
• Most modern web APIs default to JSON; XML remains common in specific domains like enterprise systems, SOAP-based APIs, and document-centric formats.

JSON.parse()/stringify() and DOMParser (for XML) are both natively supported in every modern browser, so working with either format requires no external library.