It's a shame JSON parsers usually default to performance rather than correctness, by using bignums for numbers.
> This specification allows implementations to set limits on the range and precision of numbers accepted
JSON is a terrible interoperability standard.
if it's known and acceptable that LLMs can hallucinate arguments to an API then i don't see how this isn't perfectly acceptable behavior either.
Converting that text to _any_ kind of numerical value is outside the scope of the specification. (At least the JSON.org specification, the RFC tries to say more.)
As a textural format, when you use it for data interchange between different platforms, you should ensure that the endpoints agree on the _interpretation_, otherwise they won't see the same data.
Again outside of the scope of the JSON specification.
Similarly to a "schema-less" DBMS -- you will still have a schema, it will just be in your application code, not enforced by the DBMS.
JSON is a nice balance between convenience and restrictions, but it's still a compromise.
That sentence has four negations and I honestly can't figure out what it means.
(It seems this claim is not true, but at least that’s what the sentence means.)
>That sentence has four negations and I honestly can't figure out what it means.
This example is halfway as bad as the one Orwell gives in my favorite essay, "Politics the the English Language"¹.
Compare and contrast:
>I am not, indeed, sure whether it is not true to say that the Milton who once seemed not unlike a seventeenth-century Shelley had not become, out of an experience ever more bitter in each year, more alien (sic) to the founder of that Jesuit sect which nothing could induce him to tolerate.
Orwell has much to say about either.
_____
¹https://www.orwellfoundation.com/the-orwell-foundation/orwel...
I am not, indeed, sure*,* whether it is not true to say that the Milton *(*who once seemed not unlike a seventeenth-century Shelley*)* had not become *-* out of an experience *-* ever more bitter in each year, more alien (sic) to the founder of that Jesuit sect*,* which nothing could induce him to tolerate.
{X} = JSON parsers technically [are] not following the standard if {reason}
{reason} = [JSON parsers] don't reliably store a number that {what kind of number?}
{what kind of number} = number that is not representable by a IEEE754 double precision float
seems simple