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
•silverwizard likes this.
Quincy
•silverwizard likes this.
silverwizard
That kind of violation of postel's law makes it a giant pain for humans
Quincy
•silverwizard likes this.
Quincy
•silverwizard likes this.
silverwizard
Hypolite Petovan likes this.
zhenech
•clacke: exhausted pixie dream boy πΈπͺππ°ππ likes this.
clacke: exhausted pixie dream boy πΈπͺππ°ππ
•Johan WΓ€rlander π¦
•rhalina
•Bruno Ranieri
•Menno Deij - van Rijswijk π³οΈβπ
•silverwizard
1) XML is not as bad as JSON
2) who cares about XML, it's not 2001
silverwizard
XML is criticized for being too verbose
silverwizard
To be clear - if you run JS a lot, JSON makes a lot more sense, but that's an unrelated crime
mimi_vx
•