Not about SVG as such, but the XML nature of SVG.
I see JSON these days for everything including, for instance, savefiles for documents; templates in Azure, etc etc
I wonder if I will honestly, un-ironically, use XML in my next project for something where JSON could have done the job.
JSON is missing these small things make it very annoying (mainly comments, comma at end of last element not allowed, and the crappy ambiguities standard vs implementations about numbers, autoformatting of pretty printed JSON not standardized). Also not very readable as config format.
And YAML is human editing friendly but so horrible in other ways ( [US, GB, SE, DK, NO, ...])
I am sure there are lots of small competitors. But XML is already there, so well supported everywhere.
I see JSON these days for everything including, for instance, savefiles for documents; templates in Azure, etc etc
I wonder if I will honestly, un-ironically, use XML in my next project for something where JSON could have done the job.
JSON is missing these small things make it very annoying (mainly comments, comma at end of last element not allowed, and the crappy ambiguities standard vs implementations about numbers, autoformatting of pretty printed JSON not standardized). Also not very readable as config format.
And YAML is human editing friendly but so horrible in other ways ( [US, GB, SE, DK, NO, ...])
I am sure there are lots of small competitors. But XML is already there, so well supported everywhere.