Reminds me of
this post was submitted on 12 Nov 2023
1034 points (97.6% liked)
Programmer Humor
19623 readers
1 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
Friendly reminder if you prefer dealing with JSON - YAML is a superset of JSON, so any valid JSON is also valid YAML.
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.
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.
One big thing of JSON I hate is that sometimes is used for config files or similar and it doesn't supports comments which sucks.
JSONC does support comments but it wouldn't be interoperable with anything expecting pure JSON. But still useful for local configs.
load more comments
(1 replies)
What's the original?
A bit underwhelming.
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.
load more comments
(36 replies)
i thought the original onewas about flashlights
The Future: More of the Present by Jake Likes Onions
https://jakelikesonions.com/post/158707858999/the-future-more-of-the-present
Home Assistant back in 2019..
It's been satisfying watching my configuration.yaml file shrink over the years as more and more things get handled by the UI.
Is Yaml bad ?
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
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?
load more comments
(2 replies)
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.
Also JSON has no comments. Which is great for me because I hate documenting my work, but it's still annoying.
load more comments
(3 replies)
I think yaml’s need for indentation alone makes it chaotic evil. I’ve seen so many people struggle with the indentation than they really need to it’s not fun. Especially problematic with large configuration files.
JSON is easy to unpack with tools like jq or whatever.
load more comments
(2 replies)
load more comments
(1 replies)
TOML is my bestie
load more comments
(2 replies)
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.
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
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.
There’s a lot of foot guns in YAML. The specification is way more complicated with hidden obscurities. JSON specification is just 5 diagrams. YAML speciation on the other hand is an 86 page pdf, so there’s more room for nasty surprises (which is not a thing you want in configuration files).
I’ve also seen many people struggle more than they need to with the yaml indentation.
I think the only upside to yaml is that it allows for comments, but other than that JSON all the way.
https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
The fact that it allows comments is really, really handy. I used to be a JSON advocate until I realized this one useful piece of info.
load more comments
(4 replies)
load more comments
(1 replies)
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.
I'll answer your question with a question. Why does YAML support sexagesimal? (that's base 60)
ports:
- 22:22
Becomes
{
"ports": [1342]
}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 🤷
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.
load more comments
(1 replies)
load more comments
(3 replies)
I like YAML.
That's okay, not everyone can be right :)
view more: next ›