frippa@lemmy.ml to Programmer Humor@lemmy.ml · 1 year agoYes, I program in HTMLlemmy.mlimagemessage-square39fedilinkarrow-up1422arrow-down125
arrow-up1397arrow-down1imageYes, I program in HTMLlemmy.mlfrippa@lemmy.ml to Programmer Humor@lemmy.ml · 1 year agomessage-square39fedilink
minus-squaredan@upvote.aulinkfedilinkarrow-up24arrow-down1·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-squareDiplomjodler@feddit.delinkfedilinkarrow-up9·1 year agoWhich is true for the majority of all XML files I’ve ever come across in the wild.
minus-squareSubArcticTundra@lemmy.mllinkfedilinkarrow-up4·1 year agoI think XML only makes sense if your data is heavily tree-like
minus-squareJoe_0237@lemmy.mllinkfedilinkarrow-up1·1 year agobecause you have a thing against solutions that are both beter and easier
minus-squareSubArcticTundra@lemmy.mllinkfedilinkarrow-up1·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?