I like this. Definitely going to be implementing into my hobby projects
comments
TIL: I am wrath
Greed versioning: 1.2.3_Patreon
Envy versioning: (Competitor version number plus one)
v1.0.0 final v3 retry fixed (1) (1)
Oh my company uses a system manufacturer who uses this
Sloth Versioning: YYYYMMDDhhmm
Wrath Versioning: _new_final_newer_latest_newest

Look, 1984 is when I got my first circumcision.
I got my second one at Dismey Wards..
This feels so true for stuff that isn't just dates lmao
AWS: 1.12.797
Does 1.5B count?
"Example: fall detection" Sure buddy, that's what this was intended for
Acknowledgments: Based on some research somehow maybe by some guy I guess…
Same. Everything about that description sounded really dystopian.
Have you tried asking OpenClaw to get it to compile for you? /s
Based on the description, I'm glad it doesn't work....
"Production-ready"
I totally believe it's ready for production at Microslop Corporation. They need a larger % of code written by AI, of course.
Oh, I definitely agree that meaningful whitespace can be a pain, and I'm not a very big fan in general (although I prefer meaningful whitespace like in Python to terribly indented code with regards to readability). I guess my point was just that if you're having a lot of failures due to incorrect indentation, it sounds like a systemic issue somewhere. While meaningful indentation can be annoying, I think it sounds like symptom of something more if it's responsible for most of your production failures.
I think the bottom line for me is that if a config file regularly causes errors because of incorrect indentation, it should probably be refactored, since it's clearly not easy enough to read that those errors are caught.
In yaml a mistake in indentation can easily result in a business error without config becoming invalid.
Writing too much complex configs in files is a problem too ofc, we ended up moving a lot of stuff like that to a DB lately.
I'm not a fan of indentation being logically meaningful not just in yaml. If you mess up indentation in python you can also get a technically valid code that's wrong logically.
Whitespace being part of semantics is always a bad design decision. You're not alone in this. I wish this was more widely accepted. But alas, it's not. For a configuration language I can accept it a bit more. But for a programming language it's a big faux pas in my opinion (looking at you python).
I can understand the sentiment and would 100% agree for programming languages.
But personally I actually like that it encourages a flat structure, because you do not want to be yakshaving the structure of your config file. Too much nesting means you will sooner or later run into configuration keys being nested under the wrong category, because your project context changed over time.
And well, as I've argued in a few other comments already, I think non-techie users have a disproportionally simpler time when no nesting is used. They understand the concept of a heading and then just adding a line underneath the appropriate heading is really intuitive.
You can just tell them to add the line certificate="/tmp/cert.crt" under [network.tls] and they will find a line in their config file which actually reads [network.tls] and they can just paste that line as-is.
With nesting, they'd need to add it under here:
network: {
tls: {
certificate: "/tmp/cert.crt"
}
}
Which means:
- You need some awkward explanation where they should nest it, or an explanation that e.g. "network.tls" translates to nesting.
- They will ask whether they should indent the line you sent them.
- Well, and it's also surprisingly difficult to explain between which braces they should put the text, and that's at the end of the braces, but not after the braces etc., if you're talking to them on a call.
It's not even that I'm completely enamored with TOML, but this aspect is certainly growing on me...

To me, that makes it sound like you're writing too much and too complex yaml files manually, and/or that you don't have good enough CI to catch invalid configurations. Unless, of course, you have very few prod failures overall, and the few that happen are due to yaml indentation, which I still think is a bit weird, since an invalid config caused by incorrect indentation should ideally be caught at compile time (if you're generating code from the yaml) or by some linter or something (if you're using it for config).
That actually doesn't sound bad or unreasonable
I'll agree that significant whitespace can be a PITA (one of the reasons I prefer json over yaml), but at the same time I think improper or lacking indentation hurts readability even more than significant whitespace. Toml basically encourages a completely flat structure, where objects and sub-objects are defined all over the place. At that point, I much prefer an enforced structure with whitespace.