I prefer JSON as it is really simple
I prefer JSON as there are libraries for it on every platform and for every language I've needed it.
New better alterative to XML, JSON and YAML
11–20 of 148 posts
Re: New better alterative to XML, JSON and YAML
#12This is not better than XML or JSON. Anything is better than YAML, but this is not great.
Re: New better alterative to XML, JSON and YAML
#13I prefer JSON as it is really simple
I prefer jq.
Re: New better alterative to XML, JSON and YAML
#14> Readable multiple line indented text.
Then
> Fascinating. Of interest. Worth reading.
Does that look readable to anyone?!
Re: New better alterative to XML, JSON and YAML
#15A new better alternative definition of Terse:
The act of proclaiming a “new standard” without any user community to speak of.
Re: New better alterative to XML, JSON and YAML
#16I feel like I've seen countless attempts at this, and this design doesn't seem any better than usual. There's not much in here to justify the design decisions, nor any indication that a parser implementation exists or is even being actively worked on. For something meant to be "Efficient to write by hand", the insistence on tag-like syntax but with "tags" that consist entirely of a single punctuation character, or wh…
Both a C# and JavaScript implementations exist.
The terse “single punctuation character”, e.g. make it efficient to write, more efficient than JSON.
There is no “extra open bracket”?
There is a overview of how the indenting operates.
Mode-less, means the tokeneizer does not require modes, unlike those required for XML. The parser has state.
Have the top level document named allows one to see what the document is, e.g. or .
Re: New better alterative to XML, JSON and YAML
#17> Xenon is the best way to represent information: terse The best would be to remove all the unneeded unergonomic shift-requiring from here, you already have = symbol with whitespace and $ that separate all you need
The example you give is valid xᴇɴᴏɴ. The key and value may contain whitespace and must be delineated? s are that that made XML and HTML good.
Re: New better alterative to XML, JSON and YAML
#18This seems a bit like XML light. Doesn't look enjoyable to read/write.
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 XENON provide?
Re: New better alterative to XML, JSON and YAML
#19Funnily enough, I've been working on solving the same problem concurrently. Though in my _very_ biased opinion; I think CONL is easier to read and write:
https://github.com/ConradIrwin/conl
value = example
map
a = b
list
= 1
= 2
multiline_value = """bash
#!/usr/bin/bash
echo "hello world"Re: New better alterative to XML, JSON and YAML
#20> 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.