frippa@lemmy.ml to Programmer Humor@lemmy.ml · 2 years agoYes, I program in HTMLlemmy.mlimagemessage-square39fedilinkarrow-up1425arrow-down125
arrow-up1400arrow-down1imageYes, I program in HTMLlemmy.mlfrippa@lemmy.ml to Programmer Humor@lemmy.ml · 2 years agomessage-square39fedilink
minus-squaredanAlinkfedilinkarrow-up26arrow-down1·2 years 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·2 years agoWhich is true for the majority of all XML files I’ve ever come across in the wild.
minus-squareSubArcticTundra@lemmy.mllinkfedilinkarrow-up4·2 years agoI think XML only makes sense if your data is heavily tree-like
minus-squareSubArcticTundra@lemmy.mllinkfedilinkarrow-up1·edit-22 years 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
minus-squareJoe_0237@lemmy.mllinkfedilinkarrow-up1·2 years agobecause you have a thing against solutions that are both beter and easier
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?
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
because you have a thing against solutions that are both beter and easier
What even are those?