How did the entire industry fall for this meme?

I think XML is better for document markup (e.g., DocBook) than JSON. Lightweight markup (e.g., Markdown) is even better for simple documents, but for complex markup there's not really any competition to XML.

JSON and JS are two different things.

Well i mean JSON is a topic that you will encounter eventually when learning JavaScript anyway.

Use a sax parser.

Javascriptfags should be rounded up and gassed.

Didn't know Bill only lasted 40 seconds.

>he doesn't know about point cloud csv's

>not wanting to compile 5 million lines of JSX to get Hello World
why even live

sax parsers are terrible

Attached: maxresdefault_6.jpg (1400x1050, 103K)

What's the point of XML when there were S-expressions before

at least it has fucking comments

I used to think xml is a meme, but when I looked into it, it's seriously powerful. Things like xml schemas, xpath make it much more powerful for exchanging and validating data than JSON, and c# especially has great tools where you can automatically generate a c# class corresponding to an xml schema.

I just wish it had better support in JS.

What about yaccity sax parsers?

Attached: 1345568602105.jpg (256x256, 91K)

Attached: 43184095_558730814540178_4832177222653575168_n.jpg (805x864, 51K)

java

Attached: 1541290285430.jpg (720x960, 121K)

I know very little JavaScript and use JSON on a regular basis in other languages.

Same way the industry fell for JSON. It took something everybody already knew and made a data format based on it.

>Implying that a file should have a maximum size
>Implying that any file that IS larger than 1.5GB should be split up for the arbitrary reason that you cannot comprehend working with data as large as your mum.
>Implying Jeebus

XML is great faggots, tell me ONE thing wrong about it

More angle brackets than lisp has parens. Non-standard flags. Options inside of flags.

Its powerful like lisp. Just dont use it wrong

It dares the devs to create a thousand layers of nested definitions. Combine that with the fact that the implementations of both writers and readers are fucking awful, and you get a gargantuan, godless shitfest on your hands when you need to write software that uses that data somehow through 3rd party libraries.

Thanks for paying your respects to Erik.
schnada.de/grapt/eriknaggum-xmlrant.html

the fact that you have to type each tag twice when you open and close it
the fact that it doesn't map to the standard programming data structures like json does
the fact that the spec is bloated as hell

How did the entire industry fall for this? *unzips pants*

You sound like you haven't tried namespaces. You don't know the true horror of xml until you try namespaces.

>zey are ze inferior formats and vill be exterminated!

namespaces? there's namespaces for a data definition format?

it's nice to have schema validation and a declarative transform language

There's schema validation for JSON.

it's nice for xml because it's such a poor fit for every other programming language that you *need* to invent new programming languages to do those things.

so you would use an imperative language to extract and combine hierarchical data and then present in a human readable format (like HTML or printable document)?

For data as complicated as the xml standard itself json would be an absolutely horrid abomination.
I can’t even imagine what something like COLLADA would look like if was json

Attached: 1480848089778.jpg (374x378, 15K)

It looks great when the alternative is SGML.
Learn to use a stream parser.
Waste of satanic trips. JSON itself is an abomination.
based and binarypilled