I bet a lot of my programmer friends are going, "why didn't you just use JSON and serialize settings that way?" Y'all, I did consider good ol JSON, because yes, it does have a faster compute time, but before the phoneme editor and NVDA driver settings, JSON would have been a lot less human-readable. YAML does suck for indents, I agree, but so does Python, if you are thinking on those lines, and good code indenting is honestly just good code hygiene if you think about it, why not keep that alive.
I read them on a Braille display a lot, I recognize not all people do, but poorly indented code in Braille VS well-indented is the difference from knowing quickly where functions begin VS trudging code as though it were a thick foggy swamp. And I don't like that feelin'.
I read them on a Braille display a lot, I recognize not all people do, but poorly indented code in Braille VS well-indented is the difference from knowing quickly where functions begin VS trudging code as though it were a thick foggy swamp. And I don't like that feelin'.
Alex Hall
in reply to Tamas G • • •I don't hate YAML entirely. What bugs me about it are:
* either my IDE defaults to two spaces, or that's the expected indent, because I can't use my normal tabs with it
* I still don't know when to put a hyphen before something
* I can't skip sections by using jump to matching symbol commands
* to me, it feels more fragile and harder to lint
I'm getting used to it, because Gitlab runners, Docker Compose, and other tools demand it. But I still don't really like it. JMO.