I wouldn't be so annoyed by this if a significant chunk of every meeting wasn't dedicated to the supposed benefits of JSON. Which usually rings hollow for me.
I don't particularly care about whether we use JSON, XML, or whatever. Talk about what aspects of JSON you think reads nicer, sure.
But personally I'd find it just as easy to support both! Don't presume "developers prefer JSON", I don't care. Can we move onto the datamodelling please?
@alcinnz I agree that the data modeling is way more important. And I think that if I were in a meeting with people who preferred XML, I wouldn't hold up the more important discussion over that issue. I haven't ever been in that situation though, and I'm surprised that XML versus JSON is still a contentious issue in actual standards discussions.
It's a nice idea, but my concern is that there's no coherent way to talk about 'actual data format'.
Even in a simple computer program, the same data is encoded differently at the physical level, the database level, the object level in application code, and the transport or syndication level. Once we start talking about the wider world of different database types and programming languages, this variability increases still. Which is the 'actual data format'? None!
For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).