in XML, every single non-empty tag needs both its opening and closing tag. that's at least seven characters.
Not only is it impractical, it is ugly and consists of a waste of space.
This has to change. Starting today you can begin using a proper programming-like syntax for your configuration files and any other need for a quick and easy-to-read markup protocol.
json has another purpose. yaml is indentation hell, just like toml (AKA "yaml is too mainstream for me")
Brandon Baker
we need more standards
Daniel Walker
...
Bentley Hall
0 1 2 3
vs.
{"array":[0,1,2,3]}
why this is even a question boggles my mind.
Lucas Watson
{"array":[0,1,2,3]} vs. [0,1,2,3] why this is even a question boggles my mind.
Kevin Phillips
I need compatibility. Are there libraries for my hipster language to process your hipster language?
Nathaniel Jackson
That's why JSON was invented, retard.
Caleb Garcia
>a proper programming-like syntax for your configuration files Or just plain use a proper programming language for them. Write your config files in an embedded scripting language like Tcl or Lua. Too fancy/too Turning complete for you? json5.org/
Gabriel King
>the project to give SGML a better look wew, lad >Starting today you can begin using a proper programming-like syntax for your configuration files I can already do that. >and any other need for a quick and That's what binary formats are for. >easy-to-read It's not easier to read than XML.
>JSON >configuration
Anthony Myers
I agree. XML was a horrible ida
Nathaniel Gray
I'm sorry mr. deeepaaa, but I find that syntax horrible.
Feel free to port it to your favorite programming language. With a parser generator it should only take a few hours. That said, your favorite programming language probably already has something like it implemented as a library. No. It's JSON with comments, tailing commas, etc.
Parker Myers
>that's at least seven characters. Oh boy...
There's nothing wrong with XML, saving a few bits of data is fucking stupid unless you're transferring huge amounts of data very quickly over limited bandwidth
Also what's the point of this? The code before it gets "converted" to XML looks very unreadable to me, sounds like you just figured out how interpreting and compiling work so decided to create another useless library that nobody needs.
I respect the effort, but I honestly see no value in this.
Grayson Sullivan
OP is a faggot
Eli Butler
>saving a few bits of data is fucking stupid unless you're transferring huge amounts of data very quickly over limited bandwidth
I've seen xml used for api call responses. If you have tens of thousands of customers making requests, the size difference between xml and json does matter, even if the data size is small to begin with.
Hudson Hughes
>I respect the effort, but I honestly see no value in this. /thread
Jonathan Nelson
>json has another purpose And this precludes me from using it to store data why?
Alexander Parker
Yeah, I've seen those too, I've developed API's that use XML (SOAP) and they worked just fine.
If you have thousands of customers making requests, the last of your concerns should be shaving off a couple of bits from the payload.
>Starting today you can begin using a proper programming-like syntax It already exists. Just use S-Expressions. (xml sucks) (array (0 1 2 3)) or '(0 1 2 3) or (list 0 1 2 3) etc.
Nicholas Sanders
Replacing XML usually isn't about saving bits. It's about readability for the user/programmer, which can prevent editing errors and help debugging. Better idea than OP's.