From 7e60eb3508d1a592bb5c6d4fa6756891b609e524 Mon Sep 17 00:00:00 2001 From: Antonio Yang Date: Thu, 4 Dec 2025 14:10:12 +0800 Subject: [PATCH 1/5] update readme --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 7c87fa5..231e032 100644 --- a/README.md +++ b/README.md @@ -250,6 +250,15 @@ c = "third" ``` +## Why TOML is good for programe configure file +There are serveral common config file solution: INI, JSON, YAML, TOML. +- INI is legacy and no nesting support, and the comment char is not designed at first, so some parser will use `;` or `#`. +- JSON is not support document, it is efficient for data exchange, but there should be documentation in configure, so it not good for this using case. +- YAML is too greedy on covering derserialize issue, so it is too complex for a confiture and vulnerable, for example: + - `y` ambiguously stand for "y" or true + - [CVE-2019-11253](https://github.com/kubernetes/kubernetes/issues/83253) +- TOML is good for now, and easy to write and read for humman, that is a real need for confiture file. + [crates-badge]: https://img.shields.io/crates/v/toml-example.svg [crate-url]: https://crates.io/crates/toml-example [mit-badge]: https://img.shields.io/badge/license-MIT-blue.svg From 76e266cdabf2b482710063598bffff6ba13a63b0 Mon Sep 17 00:00:00 2001 From: Antonio Yang Date: Thu, 4 Dec 2025 14:14:59 +0800 Subject: [PATCH 2/5] Update README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 231e032..cfcf665 100644 --- a/README.md +++ b/README.md @@ -250,7 +250,7 @@ c = "third" ``` -## Why TOML is good for programe configure file +## Why TOML is good for program configuration file There are serveral common config file solution: INI, JSON, YAML, TOML. - INI is legacy and no nesting support, and the comment char is not designed at first, so some parser will use `;` or `#`. - JSON is not support document, it is efficient for data exchange, but there should be documentation in configure, so it not good for this using case. From 20af0853b556df31c60c497890f00dcfcd409192 Mon Sep 17 00:00:00 2001 From: Antonio Yang Date: Thu, 4 Dec 2025 14:15:09 +0800 Subject: [PATCH 3/5] Update README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index cfcf665..ad9bc19 100644 --- a/README.md +++ b/README.md @@ -253,7 +253,7 @@ c = "third" ## Why TOML is good for program configuration file There are serveral common config file solution: INI, JSON, YAML, TOML. - INI is legacy and no nesting support, and the comment char is not designed at first, so some parser will use `;` or `#`. -- JSON is not support document, it is efficient for data exchange, but there should be documentation in configure, so it not good for this using case. +- JSON does not support documentation. It is efficient for data exchange, but configuration files should include documentation, so it is not good for this use case. - YAML is too greedy on covering derserialize issue, so it is too complex for a confiture and vulnerable, for example: - `y` ambiguously stand for "y" or true - [CVE-2019-11253](https://github.com/kubernetes/kubernetes/issues/83253) From b6250f9a5e66bdf5e4ead937a120634257df93a6 Mon Sep 17 00:00:00 2001 From: Antonio Yang Date: Thu, 4 Dec 2025 14:15:17 +0800 Subject: [PATCH 4/5] Update README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ad9bc19..c5b21fe 100644 --- a/README.md +++ b/README.md @@ -251,7 +251,7 @@ c = "third" ``` ## Why TOML is good for program configuration file -There are serveral common config file solution: INI, JSON, YAML, TOML. +There are several common config file solutions: INI, JSON, YAML, TOML. - INI is legacy and no nesting support, and the comment char is not designed at first, so some parser will use `;` or `#`. - JSON does not support documentation. It is efficient for data exchange, but configuration files should include documentation, so it is not good for this use case. - YAML is too greedy on covering derserialize issue, so it is too complex for a confiture and vulnerable, for example: From 06d4c4d7fcd3c992407989c61cb9e1aff46dd8f9 Mon Sep 17 00:00:00 2001 From: Antonio Yang Date: Thu, 4 Dec 2025 14:15:25 +0800 Subject: [PATCH 5/5] Update README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c5b21fe..a0562eb 100644 --- a/README.md +++ b/README.md @@ -254,10 +254,10 @@ c = "third" There are several common config file solutions: INI, JSON, YAML, TOML. - INI is legacy and no nesting support, and the comment char is not designed at first, so some parser will use `;` or `#`. - JSON does not support documentation. It is efficient for data exchange, but configuration files should include documentation, so it is not good for this use case. -- YAML is too greedy on covering derserialize issue, so it is too complex for a confiture and vulnerable, for example: +- YAML is too greedy on covering derserialize issue, so it is too complex for a configuration and vulnerable, for example: - `y` ambiguously stand for "y" or true - [CVE-2019-11253](https://github.com/kubernetes/kubernetes/issues/83253) -- TOML is good for now, and easy to write and read for humman, that is a real need for confiture file. +- TOML is good for now, and easy to write and read for human, that is a real need for configuration file. [crates-badge]: https://img.shields.io/crates/v/toml-example.svg [crate-url]: https://crates.io/crates/toml-example