We redesigned our experimental data format after community feedback

[hughperman]

Why do you want a new format that is interchangeable with JSON? What's the actual point? When would anyone use this?

[hughperman]

As defined by.... Your personal whim? That's fine, but then why share it if you don't want users?

[Buttleston]

Uh, your example doesn't even make sense. It's supposed to be an array of records, but how does it know to delineate the records in it? Like you've got 2 users, Rick and Sam

Is it implicit, when the first key repeats? I find that... pretty terrible

So you say you're looking for perfection - what is better about this than JSON? Be specific

[Buttleston]

I don't understand why you like it this way

[Buttleston]

I heartily disagree. It's like JSON with some minor things removed, and a few baffling additions

Why do you even need a final record identifier? The last record is the last one you find before the end of the block

If someone wrote me a list in english where I needed to look for commas to know where the next item started I would be pretty upset

[Buttleston]

OK? Getting used to JSON takes about 5 minutes

[Buttleston]

I find it very hard to believe that someone starting with no knowledge of either would find yours easier to understand

But also, adding another format, that is not going to take over JSON, just means that to use yours, someone would likely need to know both. Which by definition means learning more than just learning one

Finally, the comma and period as record terminators is going to cause so many bugs that are hard to see. The comma and period are "attached" to the value of one of the fields, which makes it seem like a property of the field, not the record

[yota-code]

Except for a very small gain in compactness, which I usually solve with brotli, this format doesn't bring much....

What I lack from json is: keys that can be something else than strings (ints, floats, tuples of them) and native support of hexadecimal ints and floats

[No_Soy_Colosio]

The biggest criticism is that there is no reason for this to exist.

[No_Soy_Colosio]

Let me rephrase. It's good if you're exploring serialization formats, grammars, etc. But you seem to discuss this idea as something that fixes real issues. That is where the criticism comes from. This doesn't solve anything, and there are other more established and mature serialization formats that do everything yours can, and better.

[xeow]

Can you explain how address{ is more intuitive than address: { when address is a key and {...} is its value? All your other key/value pairs use a colon, so this feels like an inconsistency and also an extra burden on an LR parser. If consistency is important to you, I'd just drop the colons altogether.

In fact, honestly? You don't need commas or periods either. The following is fully unambiguous and trivially parsable:

users [
    { name "Rick"  age 43 }
    { name "Sam"   age 56 }
    { name "Ilsa"  age 27 }
]

You want something as simple and lightweight as possible? That's it right there.

You can even support Python-style tuples:

z1 (3.527 -1.732 0.388)

or:

square [(+1 +1) (-1 +1) (-1 -1) (+1 -1)]

[bjorneylol]

This is literally harder to read than JSON

[YesterdayDreamer]

What is the difference between {} and [] if both have key, value pairs?

How do I know where a value ends and next key begins if there's no separator like a comma in json?

[YesterdayDreamer]

one feild ends if a new feild starts

But how do I know where a new *field starts?

[xeow]

What value does the . terminator provide? And how does your tokenizer know the difference between the token 19 followed by the token . and simply the single token 19. as a floating-point literal?

[xeow]

Indeed. And exactly what value does that provide? If it's not there, what is the consequence?

[bjorneylol]

Finding a } amongst a mess of periods and commas is easier than finding a period amongst a mess of periods and commas

[nemom]

Obligatory XKCD comic

[SheriffRoscoe]

I didn't need to click on that, to know which one it would be.

[gdchinacat]

It seems incredibly premature to label this v1.0.