add one more type a tuple with parens. Pretty please.

[RichardHightower]

Add to table, int, float, date, one more type... tuple.

You have table which is a k/v map.
You have array which all items have to be on type.

Add a list.

(1, "foo", 1979-05-27T07:32:00Z)

Sometimes things make sense in tuples. Disparate types are good for expressing many concepts.

Boon will have the 6th TOML implementation for Java.
I am writing a lot of config files, and I find JSON aggravating.
And I agree YAML has jumped the shark.

Off topic:
Boon will have tuple.
I tend to marshal JSON arrays instead of JSON objects to reduce the footprint of the JSON feed, which matters when you have a 10,000,000 user app.
I can see using toml in places where I normally might use JSON, not just config.

[RichardHightower]

More info about the parser I wrote.

http://rick-hightower.blogspot.com/2014/04/groovy-and-boon-provide-fastest-json.html

I also wrote a JSON loose, and an ASCII PLIST (Json-ish) parser.

The loose format allows comments. /* */, // and #.
The PLIST format allows plist style.
Then I have several strict JSON parser to parse direct from bytes or char[] or a char[] stream for really large files.

It is about 4x faster than common variants. (I was aiming for parity and I overshot).

The idea of the JSON loose and the PLIST is very similar to TOML.
YAML seemed overkill for what I wanted to do with config.

PLIST seemed more inline. I did not know about TOML.

http://en.wikipedia.org/wiki/Property_list

TOML and PLIST are similar.

TOML looks like ASCII PLIST and Windows INI files had a baby.

http://en.wikipedia.org/wiki/INI_file

[RichardHightower]

http://rick-hightower.blogspot.com/2014/04/toml-what-if-plist-json-and-windows-ini.html

[BurntSushi]

This looks like a duplicate of #154.

[BurntSushi]

I am closing this because it's a dupe of #154.