6 ms·
This article reeks of being written by someone with maybe a year or two of experience that's read someone else's ill-informed rants about JSON and is rehashing
by Sohcahtoa82 2y ago
This article reeks of being written by someone with maybe a year or two of experience that's read someone else's ill-informed rants about JSON and is rehashing it.
IMO, the only valid complaint is that the JSON spec can't handle Inf or NaN, but I'd argue that if you're finding yourself dealing with Inf or NaN, then you likely have a bug elsewhere, and JSON is merely exposing it.
If you're storing credit card numbers, license keys, barcode IDs, etc. as integers, you're already doing it wrong, and what serialization format you're using is completely irrelevant.
- CRConrad 2y agoTotally concur with your last paragraph. But, considering that the author is apparently one of the people behind the competing format mentioned, protobuf, your first paragraph feels way off.
- nijave 2y agoYeah, I like the "if you can't do math on it, it probably shouldn't be a numeric data type" rule of thumb i.e. applying an average to a list of credit card numbers doesn't make any sense nor does adding commas