this post was submitted on 24 Feb 2026
93 points (95.1% liked)
Programmer Humor
41127 readers
215 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Well, you can still decide how much of the TOML features you actually use in your specific application. For example, I'm currently involved in two projects at $DAYJOB where we read TOML configurations and we don't make use of the inline tables that OP memes about in either of them.
Ultimately, the big advantage of TOML over INI is that it standardizes all kinds of small INI extensions that folks have come up with over the decades. As such, it has a formal specification and in particular only one specification.
You can assume that you can read the same TOML file from two different programming languages, which you cannot just assume for INI.
I can't really decide what extensions my users will face, once they are supported. Therefore too many extensions seems bad to me.
We just document that this is how you write the config file:
And that seems straightforward enough. Yeah, technically users can opt to use inline tables or raw strings or whatever, but they don't have to.