Comment on A lot of YAML
uid0gid0@lemmy.world 1 year agoI 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.
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.
There are 6 different combinations of “interpret multiline whitespace” character patterns. There are three types of single-line strings, and if you use “Yes” or “No” the data gets type cast.
Yaml is chaotic.
Just because there are a lot of rules doesn’t make something chaotic in this system. The lawful-chaotic axis is a spectrum of how much of a stickler for the rules you are. YAML’s “one whitespace out of place and your whole config is fucked” attitude puts it squarely into lawful territory. JSON by contrast gives no shits about your file structure as long as your curly braces match.
Oh this is a good point - the syntax error on line one has ruined several productive days.
Of course the tool would happily prettify it for me, but it has to be valid json. Which I think would make it more enjoyable if it said in that message “Good luck, we’re counting on you.”
Socsa@sh.itjust.works 1 year ago
Also JSON has no comments. Which is great for me because I hate documenting my work, but it’s still annoying.
EmergMemeHologram@startrek.website 1 year ago
Just create an attribute for your comments!
sloppy_diffuser@sh.itjust.works 1 year ago
I just learned yesterday you can do this, lol. You can use “//”: ‘’ once at the root level of a package.json file.
Had to put an override to block a dependency of a dependency from installing (@types/* stubs when the package now has native type defs that conflicted with the no longer maintained stubs).
I put in a comment as to why its there.