this post was submitted on 08 Sep 2024
1236 points (98.3% liked)
Programmer Humor
32410 readers
355 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
IMHO: XML is a file format, JSON is a data transfer format. Reinventing things like RSS or SVG to use JSON wouldn't be helpful, but using XML to communicate between your app's frontend and backend wouldn't be either.
Yeah, json is not a good config format. As much as xml is not. Please use something like YAML or TOML.
I never moved away from ini I've just been sititng back watching you all re-invent the wheel over and over and over and over and over.
It's a wheel, it's supposed to turn over and over and over and infinitum!
/S (because it's big sarcasm instead of small.)
I wish more things used Nickel or Dhall for config. I don’t know why I wouldn’t want editor support for type information or the ability to make functions in my non-Turing-complete config to eliminate boilerplate on my end.
Of course you can use XML that way, but it is unnecessarily verbose and complex because you have to make decisions, like, whether to store things as attributes or as nested elements.
I stand by my statement that if you're saving things to a file you should probably use XML, if you're transferring data over a network you should probably use JSON.
We were using XML for that before JSON.
Yes and it is a good thing we don't anymore.
Why? JSON hasn't given us anything XML hasn't, except maybe a bit of terseness.
I do agree SOAP is a bit over engineered, though, but that's not the fault of XML.
XML is much more annoying to read/write by hand
As a pentester, if I see XML in HTTP I start crying.