Skip to content

Commit 8bcbdb7

Browse files
docs: enhance explanation for TOON format benefits (related to #49)
1 parent b8140ce commit 8bcbdb7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,9 @@ users[2]{id,name,role}:
5252
```
5353

5454
<details>
55-
<summary>Another reason</summary>
55+
<summary><strong>Why create a new format?</strong></summary>
5656

57-
[![xkcd: Standards](https://imgs.xkcd.com/comics/standards_2x.png)](https://xkcd.com/927/)
57+
For small payloads, JSON/CSV/YAML work fine. TOON's value emerges at scale: when you're making hundreds of LLM calls with uniform tabular data, eliminating repeated keys compounds savings significantly. If token costs matter to your use case, TOON reduces them. If not, stick with what works.
5858

5959
</details>
6060

0 commit comments

Comments
 (0)