DEV Community

Discussion on: TOON vs JSON: A Modern Data Format Showdown

View post
Collapse
 
elanatframework profile image
Elanat Framework •

In my opinion, INI is more powerful than JSON:

[core]
key = app
config = {"id":"coolapp","mode":"prod","lang":"en","threads":4}

[auth]
key = security
settings = {"oauth2":true,"token_ttl":3600,"jwt":"${ENV:JWT_SECRET}"}

[modules]
key = features
state = {"active":["analytics","cache"],"inactive":["debug"]}

[cache]
key = redis
connection = {"host":"127.0.0.1","port":6379,"ttl":300}
Enter fullscreen mode Exit fullscreen mode
Collapse
 
sreeni5018 profile image
Seenivasa Ramadurai •

Well, it’s kind of a yes and no. The .INI file format is definitely more familiar to Windows users, and it’s simple enough for basic configuration needs.

But that simplicity can be a double-edged sword .INI files can get messy and error-prone, especially when you try to handle complex or nested settings. That’s why most developers eventually moved on to XML, JSON, and YAML formats that are more structured, flexible, and platform-independent.

That said, if .INI fits your use case, go for it. But when it comes to AI or agentic applications, where efficiency and cost really matter, TOON is the smarter choice it’s lightweight and cost-effective.

Thanks,
Sreeni