Exactly! I mean, who in their right mind would use anything else than deeply nested XML, with liberal use of attributes, namespaces, and unordered serialization when updating it after in-app changes are made?
@silverwizard @quincy @farseen wholesome agree with you, JSON is for machine write/read, yaml is somewhat human readable and TOML +- usable also for human writing
Quincy
in reply to zhenech • • •silverwizard likes this.
Quincy
Unknown parent • • •silverwizard likes this.
silverwizard
Unknown parent • •The list syntax mandating ,s on all list items, except the last
That kind of violation of postel's law makes it a giant pain for humans
Quincy
in reply to silverwizard • • •silverwizard likes this.
Quincy
Unknown parent • • •silverwizard likes this.
silverwizard
Unknown parent • •like this
Hypolite Petovan likes this.
zhenech
Unknown parent • • •clacke: exhausted pixie dream boy 🇸🇪🇭🇰💙💛 likes this.
clacke: exhausted pixie dream boy 🇸🇪🇭🇰💙💛
Unknown parent • • •Johan Wärlander 🦀
in reply to zhenech • • •rhalina
in reply to zhenech • • •Bruno Ranieri
in reply to zhenech • • •Menno Deij - van Rijswijk 🏳️🌈
in reply to zhenech • • •silverwizard
in reply to Menno Deij - van Rijswijk 🏳️🌈 • •People who like JSON are obsessed with the idea that XML is bad which is the most annoying thing
1) XML is not as bad as JSON
2) who cares about XML, it's not 2001
silverwizard
Unknown parent • •JSON is designed to not be readable at a glance and resist quick updates
XML is criticized for being too verbose
silverwizard
Unknown parent • •Nah, when it is a {,[, or (, and how do you add a thing to a list? What if it's in the middle? What if at the end?
To be clear - if you run JS a lot, JSON makes a lot more sense, but that's an unrelated crime
mimi_vx
in reply to silverwizard • • •