this post was submitted on 15 Aug 2023
40 points (95.5% liked)

Technology

59314 readers
5725 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

cross-posted from: https://programming.dev/post/1743099

.yaml, .toml, etc?

you are viewing a single comment's thread
view the rest of the comments
[–] atzanteol@sh.itjust.works 4 points 1 year ago (1 children)

XML is a bit verbose but otherwise easy to understand. JSON5 supports comments.

And neither requires me to explain weird formatting nuances to devops engineers.

YAML is a pain to read (lists of structures are very messy), can't be auto-formatted, and is full of weird "gotchas" (Norway, errant tabs, etc.) if you don't do things "the right way."

Requiring the use of whitespace in formatting is wrong. End of.

[–] schaeferpp@discuss.tchncs.de 0 points 1 year ago (1 children)

Somebody has to say it, so I'm taking on the duty:

If whitespace is a problem, you use the wrong editor.

[–] atzanteol@sh.itjust.works 6 points 1 year ago

Oh, yeah, nothing like telling a dba they're using the wrong editor when they're trying to configure something.

If your config format requires specific editors you're using the wrong format.