5 ms·

toml is pretty much the best one I have seen so far. At least for small to medium size config files.

dnautics 5y ago
Toml has some hairy bits. Lists of objects, lists of lists of objects, objects of lists of objects. Complex objects with top level fields...
- chillfox 5y ago
  Yep, Although I do feel like there is a case to be made that if you need a Turing complete configuration language then in most cases you failed your users by pushing too many decisions on to them instead of deciding on sensible defaults. And if you are dealing with one of the rare cases where Turing complete configuration is desirable then maybe use Lua or something like that instead.
  - pc86 5y ago
    Even if you have sensible defaults don't you still need to be able to parse configured changes?
    - chillfox 5y ago
      Not always, sometimes all other options are just wrong. Or you can auto detect the correct setting.
  - dnautics 5y ago
    I'm not defending YAML. YAML is terrible. It's even worse with logic and/or templates (looking at you, Ansible). Toml is certainly better but I'm still baffled as to why we don't have a "better YAML". YAML could almost be okay.
    - vitiral 5y ago
      I'm curious what your thoughts are on a config language I'm working on. GitHub.com/vitiral/zoa It has both binary and textual representation (with the first byte being able to distinguish them), and the syntax is clean enough I'm planning on extending it into a markup language as well.
    - chillfox 5y ago
      Yeah, I think it's because nobody sat down and methodically created it. People create config languages that work for their use case and then it is just a happy accident if it works for other things. I don't think anyone has put serous effort into designing a configuration language. And by that I mean collect use cases, study how other config languages does things, make drafts, and test them. etc...
      - svieira 5y ago
        Dhall and Cue come to mind as ones that _feel_ more designed https://github.com/dhall-lang/dhall-lang https://github.com/dhall-lang/dhall-lang https://cuelang.org/docs/usecases/configuration/ https://cuelang.org/docs/usecases/configuration/
        chillfox 5y ago
        Interesting... Me, the programmer finds those kinda cool. And the sysadmin in me developed a dislike of both within 1 minute of looking at them. Honestly, I think a good configuration library should be more than a spec, it should come with a library that handles parsing/validation. See, there are two sides to configuration, the user and the program. Knowledge about the values, defaults and types should live on the program side and should be documented. Then the user side of configuration can be clean and easy to read/write and most important of all, allow the user to accomplish the most common configuration without having to learn a new config language on top of learning the application.
        BiteCode_dev 5y ago
- addaon 5y ago
  ... lack of a hex float representation ...
- mikepurvis 5y ago
  I understand the pragmatic reasons for it being the way it is, but I still wish TOML didn't require all strings to be quoted.
- ryukoposting 5y ago
  This is why I like INI. It doesn't have these problems, because it doesn't try to wrangle the notion of nested objects (or lists) in the first place. The lack of a formal spec is a problem, sure, but it such a basic format that it's kind of self-explanatory.
  - Dylan16807 5y ago
    When the problem is TOML not supporting easy nesting, a solution of "Don't nest." works just as well in TOML as it does in ini. It's not really an advantage of ini. Especially when a big factor in TOML not making it easy is that TOML uses the same kind of [section]\nkey=value formatting that ini does!
  - BiteCode_dev 5y ago
    You can use toml as a better ini by limiting yourself to the key / value schema. It still superior because: - it has a spec - it has other types than strings - you can always decide you actually need nested data, and add them later
    - withinboredom 5y ago
      > it has other types than strings But isn't the config file just a string?
      - chipsa 5y ago
        Everything gets serialized to a string of bytes. The point is that you can fail at parsing when the value doesn't make sense, rather than failing at some point in the future when you decide to use the value and it doesn't make sense. And if you have a defined schema, you can have your editor validate it against the schema when saving, so you don't accidentally have "FILENOTFOUND" in a Boolean.
    - ryukoposting 5y ago
      I wrote an INI parser that has numerical, boolean, timestamp, MAC address, and IP address types ;) "advantages" of not having a spec! Seriously: for application-specific config files, the lack of a formal spec can be kind of a nice thing. You can design your parser to the exact needs of your program, with data types that makes sense for your use case. Throw together a formal grammar for use in regression testing, and you're all set. Obviously a formal spec is essential for data interchange, but that's why JSON exists. To me, YAML is in a gray area that doesn't need to exist. The same thing goes for TOML, but to a far lesser extent.

Toml has some hairy bits. Lists of objects, lists of lists of objects, objects of lists of objects. Complex objects with top level fields...

chillfox 5y ago
Yep, Although I do feel like there is a case to be made that if you need a Turing complete configuration language then in most cases you failed your users by pushing too many decisions on to them instead of deciding on sensible defaults. And if you are dealing with one of the rare cases where Turing complete configuration is desirable then maybe use Lua or something like that instead.
- pc86 5y ago
  Even if you have sensible defaults don't you still need to be able to parse configured changes?
  - chillfox 5y ago
    Not always, sometimes all other options are just wrong. Or you can auto detect the correct setting.
- dnautics 5y ago
  I'm not defending YAML. YAML is terrible. It's even worse with logic and/or templates (looking at you, Ansible). Toml is certainly better but I'm still baffled as to why we don't have a "better YAML". YAML could almost be okay.
  - vitiral 5y ago
    I'm curious what your thoughts are on a config language I'm working on. GitHub.com/vitiral/zoa It has both binary and textual representation (with the first byte being able to distinguish them), and the syntax is clean enough I'm planning on extending it into a markup language as well.
  - chillfox 5y ago
    Yeah, I think it's because nobody sat down and methodically created it. People create config languages that work for their use case and then it is just a happy accident if it works for other things. I don't think anyone has put serous effort into designing a configuration language. And by that I mean collect use cases, study how other config languages does things, make drafts, and test them. etc...
    - svieira 5y ago
      Dhall and Cue come to mind as ones that _feel_ more designed https://github.com/dhall-lang/dhall-lang https://github.com/dhall-lang/dhall-lang https://cuelang.org/docs/usecases/configuration/ https://cuelang.org/docs/usecases/configuration/
      - chillfox 5y ago
        Interesting... Me, the programmer finds those kinda cool. And the sysadmin in me developed a dislike of both within 1 minute of looking at them. Honestly, I think a good configuration library should be more than a spec, it should come with a library that handles parsing/validation. See, there are two sides to configuration, the user and the program. Knowledge about the values, defaults and types should live on the program side and should be documented. Then the user side of configuration can be clean and easy to read/write and most important of all, allow the user to accomplish the most common configuration without having to learn a new config language on top of learning the application.
        BiteCode_dev 5y ago
addaon 5y ago
... lack of a hex float representation ...
mikepurvis 5y ago
I understand the pragmatic reasons for it being the way it is, but I still wish TOML didn't require all strings to be quoted.
ryukoposting 5y ago
This is why I like INI. It doesn't have these problems, because it doesn't try to wrangle the notion of nested objects (or lists) in the first place. The lack of a formal spec is a problem, sure, but it such a basic format that it's kind of self-explanatory.
- Dylan16807 5y ago
  When the problem is TOML not supporting easy nesting, a solution of "Don't nest." works just as well in TOML as it does in ini. It's not really an advantage of ini. Especially when a big factor in TOML not making it easy is that TOML uses the same kind of [section]\nkey=value formatting that ini does!
- BiteCode_dev 5y ago
  You can use toml as a better ini by limiting yourself to the key / value schema. It still superior because: - it has a spec - it has other types than strings - you can always decide you actually need nested data, and add them later
  - withinboredom 5y ago
    > it has other types than strings But isn't the config file just a string?
    - chipsa 5y ago
      Everything gets serialized to a string of bytes. The point is that you can fail at parsing when the value doesn't make sense, rather than failing at some point in the future when you decide to use the value and it doesn't make sense. And if you have a defined schema, you can have your editor validate it against the schema when saving, so you don't accidentally have "FILENOTFOUND" in a Boolean.
  - ryukoposting 5y ago
    I wrote an INI parser that has numerical, boolean, timestamp, MAC address, and IP address types ;) "advantages" of not having a spec! Seriously: for application-specific config files, the lack of a formal spec can be kind of a nice thing. You can design your parser to the exact needs of your program, with data types that makes sense for your use case. Throw together a formal grammar for use in regression testing, and you're all set. Obviously a formal spec is essential for data interchange, but that's why JSON exists. To me, YAML is in a gray area that doesn't need to exist. The same thing goes for TOML, but to a far lesser extent.