When it comes to the anti-XML discussion — readability is an opinion, not a fact. A lot of what programmers claim are facts are just opinions.
I am sorry you dislike XML. I remain unconvinced that using JSON or YAML over it is anything other than a personal preference born out of your chosen programming community’s tribalism.
@grmpyprogrammer I find the AI models do extremely well with json and you can additionally cram a bunch of different data into the same json file and still completely utilize it esp in AI environments. Obvious reason is that the field name is attached to every data field.
@grmpyprogrammer umm, probably thinking about one option for everything, not consodering the use case, the data structure, is a mistake. If you are transmitting ojects and programming variables, etc., Non critical data, between homogeneous layers, simple api calls JSon is great. If you are managing critical data, complex content or encoding complex configurations it is probably an xml case IMO. The readability also, xml may be more apropriate for complex content, mixed data, etc.
@grmpyprogrammer I'm not trying to change your mind; but if you added a Schema to JSON, would it be less bad? This is what @ocramius [of many Types] does.
@ravetracer_22@grmpyprogrammer@heiglandreas ye, and the NodeJS ecosystem has almost zero XML support as a legacy of what Grmpy said: irrational dislike of stable standards 🤷♀️
> I remain unconvinced that using JSON or YAML over it is anything other than a personal preference born out of your chosen programming community’s tribalism.
What sort of evidence might convince you, in either/any direction?
@grmpyprogrammer When you need to access data from both PHP and JS, then JSON is the only format that is natively consumable from both languages.
That is a fact.
I personally dislike JSON, but it does not mean in such cases I'm going to use XML or anything else and rely on userland 3rd party libs when parsing JSON is a native function away in both PHP and JSON.
Add comment