Jeena@jemmy.jeena.net to Programmer Humor@programming.devEnglish · 1 year agoA lot of YAMLjemmy.jeena.netimagemessage-square87fedilinkarrow-up11.04Karrow-down126cross-posted to: [email protected]
arrow-up11.01Karrow-down1imageA lot of YAMLjemmy.jeena.netJeena@jemmy.jeena.net to Programmer Humor@programming.devEnglish · 1 year agomessage-square87fedilinkcross-posted to: [email protected]
minus-squareThe Giant Korean@lemmy.worldlinkfedilinkEnglisharrow-up5·1 year agoThe fact that it allows comments is really, really handy. I used to be a JSON advocate until I realized this one useful piece of info.
minus-squarebellsDoSing@lemm.eelinkfedilinkarrow-up2·1 year agoYeah, such a simple, but still killer feature. Really sad that JSON doesn’t support them.
minus-squareThe Giant Korean@lemmy.worldlinkfedilinkEnglisharrow-up1·1 year agoI wonder how you’d even implement that. Like maybe {! At the beginning.
minus-squareGTG3000@programming.devlinkfedilinkarrow-up1·1 year agoMost comment-aware JSON parsers I’ve seen just use standard // to delineate comment lines.
The fact that it allows comments is really, really handy. I used to be a JSON advocate until I realized this one useful piece of info.
Yeah, such a simple, but still killer feature. Really sad that JSON doesn’t support them.
I wonder how you’d even implement that. Like maybe {! At the beginning.
Most comment-aware JSON parsers I’ve seen just use standard // to delineate comment lines.
They make sense.