skepller@lemmy.world to Programmer Humor@programming.devEnglish · 21 hours agoTOMLlemmy.worldimagemessage-square102fedilinkarrow-up1486
arrow-up1486imageTOMLlemmy.worldskepller@lemmy.world to Programmer Humor@programming.devEnglish · 21 hours agomessage-square102fedilink
minus-squareLiveLM@lemmy.ziplinkfedilinkEnglisharrow-up24·14 hours ago The json spec is not versioned. There were two changes to it in 2005 (the removal of comments See, this is why we can’t have nice things.
minus-squareEphera@lemmy.mllinkfedilinkEnglisharrow-up10·11 hours agoI can kind of understand it after having to work with an XML file where users encoded data into comments for no good reason. But yeah, it does make JSON awkward for lots of potential use-cases.
minus-squaretetris11@feddit.uklinkfedilinkEnglisharrow-up2·21 minutes agoThey are useful metadata important to the longterm lifespan of the codebase
minus-squareFooBarrington@lemmy.worldlinkfedilinkarrow-up1·5 hours agoThis would undoubtedly, unquestionably happen, and it would break JSON. The only reason it works so well is because comments aren’t allowed.
See, this is why we can’t have nice things.
I can kind of understand it after having to work with an XML file where users encoded data into comments for no good reason. But yeah, it does make JSON awkward for lots of potential use-cases.
Hm? Comments are not data.
They are useful metadata important to the longterm lifespan of the codebase
This would undoubtedly, unquestionably happen, and it would break JSON. The only reason it works so well is because comments aren’t allowed.