You can do that with many websites that have ids in their SEO slugs, this is usually not an issue as it's still standardized in a way that the string is just split into the id and the rest and you can look it up with both parts.
If you don't allow anyone to stop at a certain level of abstraction then nobody knows "what a computer actually is". I'd wager you don't know all the details of your computer's branch predictor and reorder buffer and whatnot... and if you do do you know about rebuffering and setup times and ...
Even though I immediately see how my comment could be considered to be gatekeeping, I won't apologize for it, as I mostly mean to explain what I think was the meaning of the grandparent: that writing YAML for a living means you're a business user, not a software engineer. Just as you'd have to squint real hard to label a pro excel user as a software engineer. If everything is easy, you're not learning transferable skills.
And I hate YAML with a passion, too, an opinion which I feel I'm entitled to.
> And I hate YAML with a passion, too, an opinion which I feel I'm entitled to.
Can't disagree with you there! Though I do struggle to find something else to recommend.
JSON5 is probably my favoured format - JSON is very clear and simple but the lack of comments is a catastrophic flaw. Unfortunately JSON5 has pretty poor adoption in the ecosystem (IDE support, libraries etc).
Out of spite and because I could, I deleted all the text in the noyaml site and then clicked "save". Sorry if you were too slow to read it. Might find it in the waybackmachine?
clickable:
https://pillser.com/supplements/vitamin-1973-omg-i-can-type-...