>>110105325
Why care AI will fuck us all.

>>110105325
*TROON

now show what happens if id 102 doesn't have a rating

this has all been solved a long fucking time ago with EDN

{"reviews"
 [{"id" 101
   "customer" "Alex Rivera"
   "rating" 5
   "comment" "Excellent!"
   "verified" true}
  {"id" 102
   "customer" "Brij Pandey"
   "rating" 5
   "comment" "Game changer!"
   "verified" true}
  {"id" 103
   "customer" "Casey Lee"
   "rating" 3
   "comment" "Average"
   "verified" false}]}

a better schema would use keywords instead of strings as the keys, but whatever
also, EDN supports tagged literals `#some-tag :some-literal` so that you can actually support custom types without doing stupid shit

>>110105390
none or null? or nil if it's flavor of the month faggotry.

yes it's missing the r

>>110105419
nil has existed since Lisp, before C was even made you fucking bimbo

>>110105325
at that point why not just go CSV?
the point of JSON is that not all elements have the same fields

>>110105325
How does Toon handle nodes that might have less or more fields?

Lot of JSON request bodies need asymmetric fields

>>110105398
>ohhh but I want the shorthand syntax!!!!
ok bitch boy, add a custom type

{"reviews"
 #shorthand-maps
 [["id" "customer" "rating" "omment" "verified"]
  101 "Alex Rivera" 5 "Excellent!" true
  102 "Brij Pandey" 5 "Game changer!" true
  103 "Casey Lee" 3 "Average" false]}

>>110105325
Ask in NEON?

File: aa.png (31 KB, 759x304)

31 KB PNG

The json example on the website compresses to 1/3 of the original size, which every webserver already does

>>110105381
finally, a RUST competitor.

File: 1761835690044081.png (193 KB, 1545x869)

193 KB PNG

>>110105325
OOOOOOHHHHHH I'M TOONING OUT

>>110105325
How is this affecting Claude and his robotic friends?

>>110105453
231 is still larger than 171.

will anything ever match xml?

File: 7w0wa1f0dhvh1.png (1.7 MB, 1080x1447)

1.7 MB PNG

>>110105381
I'm sold

>>110105467
EDN

[:p
 {:class "some-paragraph"}
 "Omg look at this text "
 [:strong "Becky"]
 "!"]

https://github.com/weavejester/hiccup

>>110105325
TOON is hard to read

TOON doesn't even support sets. guess what does? EDN.

#{:order "doesn't" :matter/LMAO}

>>110105325
This is just CSV with extra steps and there's a reason CSV isn't used for this.

File: Robotnik.jpg (36 KB, 621x480)

36 KB JPG

>>110105325
but that's just csv

>>110105508
not only is it csv with extra steps but it is worse
it seems the root element must specify the array size, seemingly unnecessarily
what if it doesn't match the number of actual elements?
do we read less? do we read nulls? do we handle it as error?

The point of JSON is to be human readable and editable. If you want to pack data into a small space then use binary.

>>110105325
These data formats are very outdated for the agentic era. All you need is .md files for agent communication

>but what if we don't have one of the values????
EDN would solve this too. use nil, or, if you don't even want the key, then define a placeholder (either user-defined or by the custom type).

{"reviews"
 #shorthand-maps
 [_ ; the placeholder, did I mention that EDN supports comments?
  ["id" "customer" "rating" "omment" "verified"]
  101 "Alex Rivera" 5 "Excellent!" true
  102 "Brij Pandey" 5 _ true
  103 "Casey Lee" 3 _ false]}

>>110105543
know what binary format supports the exact same shit that EDN does? Nippy
https://github.com/taoensso/nippy

>>110105325
woah, nigga invented plain text

revolutionary

is this what vibeshitters do all day

>>110105612
Hell, you could just use bencoding.

>>110105398
this is just json but without colons or commas

>>110105325
So what happens if the object names vary between each entry?

>>110106046
that's illegal

>>110105325
toml exists. kys.

>>110105979
have you read any of my other posts in this thread?
show me your JSON doing

{[:a "vector" #{:as/a} key]
 "some value"}