4 ms·
If you apply validation, testing, document the protocol and use decent serialisation rather than string combinations, it's really not that bad. I'd even argue t
by jeroenhd 3y ago
If you apply validation, testing, document the protocol and use decent serialisation rather than string combinations, it's really not that bad. I'd even argue that it's better than JSON.
However, it was popular during a time when C++ (not C++11) was the language to go to, CI was a very manual process for most companies, CD was something only very small companies could do, and protocols were vague. Had we had JSON during the same time period, JSON would now be considered a terrible standard we should just abandon.
- moron4hire 3y agoWell, JSON would have never been created in C++. The moral equivalent in statically compiled language was dumping struct memory raw out to files. And many programs did that, it just wasn't platform independent. JSON happened because more software was being written in JavaScript and, like most interpreted scripting language, doesn't care what you do, so long as what you do succeeds.
- rewmie 3y ago> Well, JSON would have never been created in C++. Why? Marshalling is a common requirement that's not a monopoly of a single language, and there is no technical limitation on C++ that stops it from parsing any particular data interchange language. > The moral equivalent in statically compiled language was dumping struct memory raw out to files. If you've chosen to go the miopic path and focus on JSON's eval trick, you'd be missing the whole point of JSON. If you're focusing on marshalling languages, you're somehow pretending that things like Apache Avro, Protocol Buffers, Apache Thrift, etc don't exist. > And many programs did that, it just wasn't platform independent. I don't think this is true at all. See examples above.