3 ms·
Please keep your patronizing comment to yourself, or add some arguments to it. JSON's spec is simpler, and the data are more compact. There are a ton of extrem
by linkdd 5y ago
Please keep your patronizing comment to yourself, or add some arguments to it.
JSON's spec is simpler, and the data are more compact. There are a ton of extremely fast parsers, as well as stream parsers. Many languages support JSON natively making it extra easy for interoperability.
- willseth 5y agoReally? Try querying JSON, or transforming it, or validating it. There are fast JSON parsers? Cool, there are fast XML parsers too (that stream). JSON's spec is simpler, it's also more limited. I don't know what your point is. OP claimed XML was "worse" than JSON for large, deeply nested data, and his most compelling argument was "Haha nope." But sure, I'm patronizing. Go police someone else's comments.
- kbenson 5y ago> his most compelling argument was "Haha nope." Pretty sure that was in response to you making assumptions about their experience, not as an answer to the question about what specifically makes them think that, which you only asked afterwards. This whole chain of comments is a good example of why responding with a dismissive short comment isn't a good idea, even if it feels good to send in the moment.
- willseth 5y ago> This whole chain of comments is a good example of why responding with a dismissive short comment isn't a good idea This is simply inevitable as long as commenters are willing to make broad generalizations about complex topics. And it's hardly unfair to make assumptions about someone's experience when they do not include it along with their highly reductive comment supposedly based on such experience!