12 mo. ago • 97%

A lot of YAML

homeassistant @lemmy.world A lot of YAML

88 comments

Reminds me of

97
Friendly reminder if you prefer dealing with JSON - YAML is a superset of JSON, so any valid JSON is also valid YAML.

52
- That’s more of a weakness of yaml. There’s so many ways to specify the exact same thing. Not exactly what you need for configuration files maintained by multiple people. It easily becomes an big incoherent mess.
  
  In JSON the default way is the only way. Nice and coherent.
  
  51
  
  I agree that YAML is painful and it really seems like it's had a lot of feature creep.
  
  JSON is painful in its own way too, though. There's a lot of syntax noise from things like braces, quotation marks, etc, so it's easy to make a mistake. Regular JSON doesn't allow trailing commas.
  
  YAML tried to solve some of that, and did succeed in some ways, but introduced its own issues.
  
  TOML seems great to me, but maybe it has its own issues. TOML actually has defined data formats for things like dates (both offset and local) and times, which is missing from both JSON and YAML so every app ends up doing it its own way.
  
  28
- Found out the hard way that no, it's not.. there are a few valid json files that most yaml parsers choke on
  
  4
What's the original?

30
- A bit underwhelming.
  
  97
  
  Interesting. I've apparently never seen the original. The best version I've seen, which I thought was the original, was porn. It just makes the guy's face in panel 4 that much better.
  
  78
  
  i thought the original onewas about flashlights
  
  4
- The Future: More of the Present by Jake Likes Onions
  
  https://jakelikesonions.com/post/158707858999/the-future-more-of-the-present
  
  17
  
  Permanently Deleted
  
  29
Home Assistant back in 2019..

23
- It's been satisfying watching my configuration.yaml file shrink over the years as more and more things get handled by the UI.
  
  5
Is Yaml bad ?

16
- Not always, but the second you use anchor/references you have sold your soul in a Faustian bargain of convenience.
  
  On the alignment chart of data/markup formats:
  
  lawful good: JSON
  
  lawful neutral: TOML
  
  lawful evil: XML
  
  neutral good: reStructuredText
  
  true neutral: HTML
  
  neutral evil: LaTeX
  
  chaotic good: YAML
  
  chaotic neutral: Markdown
  
  chaotic evil: xlsx/csv
  
  58
  
  Nah this chart needs fixing. Raw html is not neutral. And how is html neutral but xml evil. And who is writing restructured text outside of python?
  
  22
  
  I honestly think that JSON and YAML should be swapped due to YAML's strict indentation rules whereas you can just pack an entire JSON object on one line.
  
  20
  
  TOML is my bestie
  
  7
  
  I went straight from chaotic evil to lawful good.
  
  3
  
  good to know I'm on both the lawful good and the chaotic evil side
  
  1
- Yes, a bit. But that's not the problem.
  
  The problem is that the current fashion of devops is done through piles and piles of badly defined YAML. If it used any other configuration language, it would be just as bad.
  
  37
- It isn't "bad", as it does have a purpose. It's just fucking annoying to work with.
  
  https://docs.platform.sh/learn/overview/yaml/what-is-yaml.html
  
  28
  
  How's it annoying? It's easier to edit by hand than json as it allows for comments and there's no trailing comma errors. I prefer it any day over json.
  
  15
- There are plugins that go back and forth between JSON and YAML so as you might expect it's similar. Unlike JSON, spacing has semantic meaning, which can be a little annoying, especially when cutting and pasting. It's nice in that configs aren't cluttered up with open and close braces. It could be annoying AF if you're a tabs instead of spaces person but idk because I'm a spaces person.
  
  I like YAML for config over .config files but it's not a big deal either way. It just encourages better organization of settings because the hierarchical structure demands it while .config let's you just drop a setting anywhere in the file. But it's valid to have the opposite preference for the exact same reasons.
  
  8
- I'll answer your question with a question. Why does YAML support sexagesimal? (that's base 60)
  
  ports: - 22:22
  
  Becomes
  
  { "ports": [1342] }
  
  6
- not at all. it's used for configuration and stuff. having a lot of it can be a real bummer depending on the context. like a puppet config or perhaps a super weird docker compose setup. I've never heard anyone complain about the markup though. it's like blaming json for a crap api or something or idk blaming the coffee cup for burnt coffee 🤷
  
  4
  
  It's just another structured data format. It's used for a lot more than config. It's also how you define commands and etc for Ansible. Like how a Maven project is defined in XML or a NodeJS package has its JSON.
  
  Sure they're still "just" data formats on their own, but what they're used for is genuinely just as important as what it is. I really doubt XML would've held on like it has without HTML being the web.
  
  8
  
  For some little config it's fine, but it's horrible when used when you have thousands upon thousands of lines of it. Lots of DevOps tools tend to use it like a fully-blown turing-complete programming language, and each has a different DSL of doing variables, loops etc. And that becomes an abomination.
  
  3
- I learned the hard way that no is false in yaml. Took us a while to realize why our app failed to start in Norway. Too many ways to do something.
  
  3
  
  Even a 'no' is a 'false' ?
  
  1
I like YAML.

9
- That's okay, not everyone can be right :)
  
  22
Speaking of YAML, anybody seen the new PKL config language?

1
yaml > haml > everything else

1

You've viewed 88 comments.