Hacker News Reader

Hacker News

Comment by abraxas | Hacker News Reader

Parent Full thread

abraxas

3) set types, 4) optional schemas 5) multiline strings 6) consistent support for numeric types 7) streaming data

The litany is not short and I'm sure I've overlooked a couple.

View on HN

JSON is popular because it’s tiny. If you want to trade tiny for a litany of features and data types then just use XML.

You should try XML. You may like it.

That reminds me of my favourite XML quote: "XML is a lot like violence. If it isn't solving your problem, then you aren't using enough of it"

JAXB is at the same time awesome, and completely terrifying.

You can try json schema. Streaming data is also easy with json lines.

But if you add too many features, it may end up like XML.

yeah, you can do everything by imposing more topology on top of JSON just like as it happened with XML. The JSON advocates are slowly reinventing everything that their parents built into XML 20 years earlier. My hunch is that it will share its path in acquiring bloat.

From what I have seen, the excessive topological frameworks on top of JSON have never really take off. There have been many schema systems available for 10 years now but for some reason everyone seems to fall back to accepting basic JSON. There is a place for this stuff but only in very limited areas. Hopefully it does not go too far, for example like Microsoft did with SOAP. I still have nightmares from work decoding completely wrong XML generated by the native SOAP XML generators in old C# banking apps.

What do you mean by schema? JSON supports schema with libraries included in most popular languages nowadays. https://json-schema.org/

For numeric types, if you handle integer larger than 2 billions or floating numbers where the precision is critical (that's where json fails), these can and should be represented as string. I don't think there is any common format that guarantees large numbers and/or arbitrary precision to be encoded and decoded properly across languages and platforms.

8) date types

So basically EDN.

Right

> 4) optional schemas

Perhaps CDDL:

* https://tools.ietf.org/html/rfc8610

Reply on news.ycombinator.com