@[email protected] to Programmer [email protected] • 1 year agoYes, I program in HTMLlemmy.mlimagemessage-square39fedilinkarrow-up1417arrow-down125
arrow-up1392arrow-down1imageYes, I program in HTMLlemmy.ml@[email protected] to Programmer [email protected] • 1 year agomessage-square39fedilink
minus-square@[email protected]linkfedilink21•1 year agoThis reminds me of Apple plist files, which appear to have been invented by someone that doesn’t know how XML works.
minus-square@[email protected]linkfedilink8•1 year agoWhich is true for the majority of all XML files I’ve ever come across in the wild.
minus-square@[email protected]linkfedilink3•1 year agoI think XML only makes sense if your data is heavily tree-like
minus-square@[email protected]linkfedilink1•1 year agobecause you have a thing against solutions that are both beter and easier
minus-square@[email protected]linkfedilink1•edit-21 year agoJSON spreads out tree nodes vertically (with all the attributes), whereas in XML it’s usually one node per line, ie. more compact I suppose. This is just my very niche opinion though
This reminds me of Apple plist files, which appear to have been invented by someone that doesn’t know how XML works.
Which is true for the majority of all XML files I’ve ever come across in the wild.
I think XML only makes sense if your data is heavily tree-like
In that case, why not use JSON?
because you have a thing against solutions that are both beter and easier
JSON spreads out tree nodes vertically (with all the attributes), whereas in XML it’s usually one node per line, ie. more compact I suppose. This is just my very niche opinion though
What even are those?