On: What is wrong with TOML? (2019)

[lr4444lr]

I can't be the only person who thinks the monumental effort spent on config formats is bike-shedding.

JSON is good enough for anything I've done. Not perfect, but no serious flaw that can't be fixed by just adding a simple app-specific post-process step that I will inevitably do for any other format anyway. JSONSchema gives us some typing sanity.

Can we just move on already to more interesting problems? It's not like git fulfills every VCS wish I've ever had either, but I have to move on. Projects and libs that introduce new config formats that continually remake the wheel, whose quirks have to be learned, are not helping my net productivity.

</rant>

[ihateolives → lr4444lr]

> JSON is good enough for anything I've done.

I want comments in config files.

[ok_computer → ihateolives]

A horrible workaround I use is a blank redundant key and a leading // in my string to draw my eye to it. This only preserves the last comment in my python dictionary but I only use comments to work in the json file.

    {
        “”:”// comment here”,
        “Entry”:[-1,0,2],
        “”:”// next comment”,
        “Flag”:true
    }

[timmytokyo → ihateolives]

And trailing commas on final list elements and object properties.

[skrebbel → ihateolives]

JSONC is exactly that, JSON with comments. Works fine, eg typescript’s tsconfig file is JSONC and I’ve yet to find a problem with it.

[bobbylarrybobby → ihateolives]

https://json5.org

[hddqsb → lr4444lr]

I can relate. But after using JSON for a while (in files that I edit by hand), I found that I really want comments and trailing commas (which leads to https://nigeltao.github.io/blog/2021/json-with-commas-commen...). Next I'd probably want multiline strings (leading to https://github.com/json5/json5).

But if you use those extensions, all your tooling breaks.

(Aside: I think the real bike-shedding would start when you want to add some syntax for raw string literals, e.g. heredocs; it's one of those features that feels redundant, until the day when you really need it and you can't bear the pain of repeatedly escaping and unescaping.)

[rewmie → lr4444lr]

> JSON is good enough for anything I've done. Not perfect, but no serious flaw that can't be fixed by just adding a simple app-specific post-process step that I will inevitably do for any other format anyway.

If someone wants JSON with extra features like comments and typingz they are better off switching to Ion.

https://amazon-ion.github.io/ion-docs/docs/spec.html

[GuB-42 → lr4444lr]

  JSON is good enough for anything I've done.
  ...
  </rant>

Except for closing comments, for that, you need XML.

[eviks → lr4444lr]

Yeah, don't know why some people don't want to settle on bad formats without such basics of human economics like comments and keep improving

[mikece → lr4444lr]

Given how little I deal with config files compared to the rest of my work I prefer formats that are obvious, even if verbose, to those with sneaky syntax. I'll take JSON or even XML over TOML any day.