3 ms·
That's because you (and many others) are drinking the static typing koolaid Now try serializing things in XML instead of JSON. But not one type of message, mul
by raverbashing 7y ago
That's because you (and many others) are drinking the static typing koolaid
Now try serializing things in XML instead of JSON. But not one type of message, multiple types, with flexible formats.
"Oh but this never happens" except it does.
Not to mention the iteration speed whenever you need to fix something.
- walshemj 7y ago?? sorry what do you mean, I was happily reading multiple types of logs with multiple different format records for a Billing system using statically typed PL/1G in the 80's Apart from both json and XML are a PITA to work with in the first place
- ptx 7y agoJSON is wonderfully simple to work with - in a dynamic language. Having to map it to a statically known schema, as you would in a statically typed language, loses that simplicity and can be, as you say, a PITA.
- Gibbon1 7y agoI think that's a defect of JSON not statically typed languages.
- raverbashing 7y ago"defect of JSON" while it could be better, it has some type definitions and as I said, people are too deep in the static world to see outside of it