Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New better alterative to XML, JSON and YAML

xenondata.org

Post reply on HN
Print view View original

21–30 of 148 posts

Re: New better alterative to XML, JSON and YAML

#21

Post by Solomoriah »

GeneThomas wrote: post #20
Oras wrote: post #14

> Readable multiple line indented text. Then > Fascinating. Of interest. Worth reading. Does that look readable to anyone?!

The “readable indented text” refers to https://xenondata.org/#scalars where multiple lines of text can be indented and extracted as expected. One can argue that JSON is not readable due to requiring escaping (\n) for multiple line strings.

This is not enough of an improvement over JSON to justify choosing another format, given that the new format is (A) not recognized and (B) uses even more special characters. (By "not recognized" I actually mean there are no implementations given for any languages, much less accepted standard implementations.)

Re: New better alterative to XML, JSON and YAML

#22

Post by GeneThomas »

necovek wrote: post #4

Obligatory XKCD: https://xkcd.com/927/ That page does not support the topic title at all: why is this a "better alternative" to XML, JSON or YAML?

Grudgingly ha ha. As per https://xenondata.org Xᴇɴᴏɴ is more terse than even ᴊꜱᴏɴ and has the advantages listed in first paragraph.

Re: New better alterative to XML, JSON and YAML

#24

Post by GeneThomas »

Solomoriah wrote: post #18
GeneThomas wrote: post #9

Earlier quoted context omitted.

There is less typing than JSON.

There are characters, which are awkward on a good day. Yeah, we use them in HTML but the editor helps with that. And there are a bunch of special characters and "objects" that require interpretation. JSON has what? Quotes, square brackets, colons, and commas, used the way they are used in most programming languages, and thus familiar to most of us. Outside of terseness, which is overrated, what real advantages does X…

See the opening paragraph.

Re: New better alterative to XML, JSON and YAML

#25

Post by trustinmenowpls »

CableNinja wrote: post #5

Its like you took xml and made a drunken bastardized baby with json. This is ugly and id rather read untabbed json than this hot mess

This is needlessly rude and dismissive, consider that the author of this spec is in the comments responding to people. If he had presented this at a conference would you come up to him after and say this to his face?

Try to have a little more decorum when giving feedback

Re: New better alterative to XML, JSON and YAML

#26

Post by hinkley »

CableNinja wrote: post #5

Its like you took xml and made a drunken bastardized baby with json. This is ugly and id rather read untabbed json than this hot mess

I don't want to dogpile on making fun of someone on hacker news. So I'm just going to mention Dunning-Kruger and then close this tab.

Re: New better alterative to XML, JSON and YAML

#29

Post by trustinmenowpls »

I know people are hating on it, because who likes a new thing? Especially something that looks kinda like xml.

But I personally really liked the structure that xml forced, I just found it to be way to verbose. I find json and yaml and their depedancies on tabs to be confusing and the specs are often abused in ways that make them nearly as hard to parse for a human as xml.

This feels like a good middle ground, I hope it receives more support

Re: New better alterative to XML, JSON and YAML

#30

Post by satvikpendem »

trustinmenowpls wrote: post #25
CableNinja wrote: post #5

Its like you took xml and made a drunken bastardized baby with json. This is ugly and id rather read untabbed json than this hot mess

This is needlessly rude and dismissive, consider that the author of this spec is in the comments responding to people. If he had presented this at a conference would you come up to him after and say this to his face? Try to have a little more decorum when giving feedback

Yep, I flagged that comment for not being civil, it's simply unnecessary to be so rude.
Post reply on HN