▲ 1233 ▼ AI's take on XML (lemmy.world) submitted 2 years ago by renzev@lemmy.world to c/programmerhumor@lemmy.ml 132 comments fedilink hide all child comments
[+] skullgiver@popplesburger.hilciferous.nl 21 points 2 years ago* (last edited 2 years ago) (2 children) [deleted] permalink fedilink source parent hideshow 4 child comments replies: [–] MonkderVierte@lemmy.ml 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. permalink fedilink source parent hideshow 4 child comments replies: [–] sysop@lemmy.world 7 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] reinei@lemmy.world 2 points 2 years ago* 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.) permalink fedilink source parent [–] toastal@lemmy.ml 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. permalink fedilink source parent [–] schnurrito@discuss.tchncs.de 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. permalink fedilink source parent hideshow 2 child comments replies: [+] skullgiver@popplesburger.hilciferous.nl 9 points 2 years ago* (last edited 2 years ago) [deleted] permalink fedilink source parent
[–] MonkderVierte@lemmy.ml 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. permalink fedilink source parent hideshow 4 child comments replies: [–] sysop@lemmy.world 7 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] reinei@lemmy.world 2 points 2 years ago* 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.) permalink fedilink source parent [–] toastal@lemmy.ml 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. permalink fedilink source parent
[–] sysop@lemmy.world 7 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] reinei@lemmy.world 2 points 2 years ago* 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.) permalink fedilink source parent
[–] reinei@lemmy.world 2 points 2 years ago* 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.) permalink fedilink source parent
[–] toastal@lemmy.ml 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. permalink fedilink source parent
[–] schnurrito@discuss.tchncs.de 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. permalink fedilink source parent hideshow 2 child comments replies: [+] skullgiver@popplesburger.hilciferous.nl 9 points 2 years ago* (last edited 2 years ago) [deleted] permalink fedilink source parent
[+] skullgiver@popplesburger.hilciferous.nl 9 points 2 years ago* (last edited 2 years ago) [deleted] permalink fedilink source parent
