Yes, they could've just used JSON. Totally pointless waste of time.
this post was submitted on 06 Sep 2024
61 points (73.6% liked)
Programming
17672 readers
267 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
Somehow it’s clunky to use.
huh?
I find developing GitHub CI in YAML clunky.
I don't find configuring a simple service via YAML config, with a preset showing me and explaining what I can do clunky.
It's docs are garbage, but the language is quite simple and human readable even for non-techies. I think it's a bit too easy at times, resulting in people just kinda winging it
cradles yaml in her hands and coos don't you talk to my baby like that! she has potential !
Yaml is fundamentally the same as the json and xml it has mostly replaced (and the toml that didn't manage to replace yaml)... it's a data serialization format and just doesn't have any facility for making abstractions, which are the main tool we human use to deal with complexity.
Abstractions aren't concrete and all of these standards you're referring to are concrete data serialisations. You may be interested in CUE which captures this concept in its design.
load more comments
(2 replies)
If YAML and JSON were gripping my hands for dear life, dangling off of a cliff...
I would let both drop into the abyss so I could spend more time with INI.