you are viewing a single comment's thread
view the rest of the comments
[–] 28 points 2 years ago (2 children)

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.

  • source
  • parent
  • hideshow 4 child comments
  • [+] 21 points 2 years ago* (last edited 2 years ago) (2 children)
  • [–] 4 points 2 years ago (2 children)

    The amount of config.jsons I've had to mess with...

    Yeah, json is not a good config format. As much as xml is not. Please use something like YAML or TOML.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 2 years ago

    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.

  • source
  • parent
  • [–] 1 point 2 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 2 years ago (1 child)

    We were using XML for that before JSON.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 2 years ago (1 child)

    Yes and it is a good thing we don't anymore.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 16 points 2 years ago (2 children)

    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.

  • source
  • parent
  • hideshow 4 child comments