| ▲ | srvmshr an hour ago | |
Pardon my ignorance about formats, but between XML & JSON, what would have made them choose XML? As I understand there is lot more tooling, standards & existing software examples around JSON for project & records management (e.g. VSCode's records as settings.json for example). Wasn't XML spearheaded by Microsoft but mostly used by Microsoft today? | ||
| ▲ | cozzyd an hour ago | parent | next [-] | |
json's only advantage is it's easier to write by hand, but that's not really a consideration here. XML has schema support and much more tooling available. | ||
| ▲ | lelanthran 43 minutes ago | parent | prev | next [-] | |
> As I understand there is lot more tooling, standards & existing software examples around JSON for project & records management I don't understand why that is relevant; as long as there is a minimum level of tooling, libraries and support for their choice, what benefit would JSON bring over XML? I don't see a clear reason for one over the other. Honestly, I'd have the same question if they chose JSON and someone asked why did they choose JSON over XML - Why wouldn't they? | ||
| ▲ | actionfromafar 41 minutes ago | parent | prev [-] | |
JSON made me not hate XML. YAML made me not hate JSON. | ||