3 ms·
People severely underestimate the damage XML does. Example: <number>9012853</number> You just added a data overhead of 500% over using a 4-byte integer, and a
by tybris 17y ago
People severely underestimate the damage XML does. Example:
<number>9012853</number>
You just added a data overhead of 500% over using a 4-byte integer, and an even bigger parsing overhead. Let me guess, now you need to "scale"?
- jauco 17y agoSerialising a single number that way is indeed worthy of a dailywtf mention, however none of that has anything to do with xml, json: {number:9012853} Yaml: number: 9012853 It's bad code, no matter the language.
- jamesbritt 17y agoPick your tools for the task. If time and space constraints are critical, use ASN.1 or something terser. If you need Joe Tech to pop open a wire trace in Notepad and quickly check some value, maybe XML wins. If you want to view the results as an expandable tree in a some Web browser, perhaps apply a style sheet, maybe XML wins. If you want free, robust, off-the-shelf parsers with a well-documented API, maybe XML wins there, too. XML solves a certain set of problems. If those aren't your problems, maybe XML isn't the right choice.