skepller@lemmy.world to Programmer Humor@programming.devEnglish · 7 hours agoTOMLlemmy.worldimagemessage-square40fedilinkarrow-up1225arrow-down14
arrow-up1221arrow-down1imageTOMLlemmy.worldskepller@lemmy.world to Programmer Humor@programming.devEnglish · 7 hours agomessage-square40fedilink
minus-squareartifex@piefed.sociallinkfedilinkEnglisharrow-up97·7 hours agoJSON is like the carcinization of programming
minus-squarepet the cat, walk the dog@lemmy.worldlinkfedilinkarrow-up14·4 hours agoWhat’s it called when people try to reinvent Lisp for the hundredth time?
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up13·5 hours agoWell… It’s name-value pairs, with groups denoted by balanced brackets. It’s close to as good as you can get for one kind of data serialization. What is impressive is how many problems people manage to fit in something so small.
minus-squareValmond@lemmy.dbzer0.comlinkfedilinkarrow-up26arrow-down1·7 hours agoChuck in comments and I’m on board.
minus-squarepanda_abyss@lemmy.calinkfedilinkarrow-up40·7 hours agoIf we’re adding comments to json, can we add canonical support for trailing commas?
minus-squarepanda_abyss@lemmy.calinkfedilinkarrow-up14·6 hours agoOh, a trailing comma? That’s a tuple.
minus-squareValmond@lemmy.dbzer0.comlinkfedilinkarrow-up5·6 hours agoYeah when the call_func((a,)) is the way to go it is a newbie pain for sure. Remember banging my head on that one.
minus-squarepanda_abyss@lemmy.calinkfedilinkarrow-up1·6 hours agoI’ve spent hours on that, and debugging missing commas between string literals. Even on separate lines you’re not safe from implicit concatenation.
minus-squareAnafabula@discuss.tchncs.delinkfedilinkEnglisharrow-up4·4 hours agoJust make JSON5 the new official version and I would be ok
minus-squaredohpaz42@lemmy.worldlinkfedilinkEnglisharrow-up9arrow-down1·6 hours agoThat’s not JSON. Note the use of equal signs for the property names. That’s something else.
minus-squareunmagical@lemmy.mllinkfedilinkarrow-up11·5 hours agoCarcinisation is the phenomenon of non crabs to evolve crab like characteristics. It is not the process of non crabs becoming true crabs. In this case the language is trending toward JSON syntax, but it doesn’t have to actually be JSON for carcinisation to be an applicable analogy.
minus-squaredohpaz42@lemmy.worldlinkfedilinkEnglisharrow-up1·14 minutes agoSo, you can say, it’s something else? 🤔
minus-squareulterno@programming.devlinkfedilinkEnglisharrow-up10arrow-down1·edit-26 hours agoEquals schmequals. It could be a ⇨ and it would be the same as JSON because it is still a single symbol used as a separator. a distinction without a difference Now, if it took multiple separators, each giving some specific different meaning, then it would be a something else.
minus-squaredohpaz42@lemmy.worldlinkfedilinkEnglisharrow-up1·15 minutes agoNone of what you said makes any sense. This is the equivalent of an anti-vaxxer denouncing vaccines because they feel that their herbs are close enough to real medicine. 🤦♂️ Don’t do that. Syntax absolutely matters.
JSON is like the carcinization of programming
What’s it called when people try to reinvent Lisp for the hundredth time?
carthinazation
Well…
It’s name-value pairs, with groups denoted by balanced brackets. It’s close to as good as you can get for one kind of data serialization.
What is impressive is how many problems people manage to fit in something so small.
Chuck in comments and I’m on board.
If we’re adding comments to json, can we add canonical support for trailing commas?
Found the python guy!
Oh, a trailing comma? That’s a tuple.
Yeah when the call_func((a,)) is the way to go it is a newbie pain for sure. Remember banging my head on that one.
I’ve spent hours on that, and debugging missing commas between string literals. Even on separate lines you’re not safe from implicit concatenation.
Just make JSON5 the new official version and I would be ok
That’s not JSON. Note the use of equal signs for the property names. That’s something else.
Carcinisation is the phenomenon of non crabs to evolve crab like characteristics. It is not the process of non crabs becoming true crabs.
In this case the language is trending toward JSON syntax, but it doesn’t have to actually be JSON for carcinisation to be an applicable analogy.
So, you can say, it’s something else? 🤔
Equals schmequals.
It could be a
⇨and it would be the same as JSON because it is still a single symbol used as a separator.Now, if it took multiple separators, each giving some specific different meaning, then it would be a something else.
None of what you said makes any sense.
This is the equivalent of an anti-vaxxer denouncing vaccines because they feel that their herbs are close enough to real medicine. 🤦♂️
Don’t do that. Syntax absolutely matters.