True for content that is available this way, and if you have a flatrate broadband connection.

That’s what they’re doing:

Recently digitalized bunch of DVDs and BluRays.

I never understood why people would say JSON is superior, and why XML seemed to be getting rarer, but the author explains it:

XML was not abandoned because it was inadequate; it was abandoned because JavaScript won.

I’ve been using it ever since I started using Linux because my favorite window manager uses it, and because of a long-running pet project that is almost just as old: first I used XML tools to parse web pages, later I switched to dedicated data providers that offered both XML and JSON formats, and stuck to what I knew.

I’m guessing that another reason devs - especially web devs - prefer JSON over XML is that the latter uses more bytes to transport the same amount of raw data. One XML file will be somewhat larger than one JSON file with the same content. That advantage is of course dwarved by all the other media and helper scripts - nay, frameworks, devs use to develop websites.

BTW, XML is very readable with syntax highlighting and easily editable if your code editor has some very basic completion for it. And it has comments!

What does it do? AFAICS the code is the java(pardon,type)script framework for the webpage itself?

Of course, that too can change. From the current README:

What Can Be Changed

Everything. Including these rules.

Top PRs:

But most error messages are in plain English first (plus some numbers and codes).
No, they see white (gray actually) blocky text on a black background, they think the machine is broken and go into panic mode. Instead of reading.
Which is kinda what you said.