4 ms·
Readable is not a proposition, its a spectrum. The beauty of JSON is that you can convert it to a more readable state. For example, an unjustify would force th
by Fnoord 5y ago
Readable is not a proposition, its a spectrum.
The beauty of JSON is that you can convert it to a more readable state. For example, an unjustify would force the correct enters, already improving readability (I still find it unreadable, but OK). Converting it to YAML would, in my opinion, increase the readability even further, but YMMV.
With the binary word processors, we had a vendor lock-in. Never again! If we got open standards, we can convert to/from another document format, including the Markdown language of your choice.
- 8note 5y agoReadable to me is that you don't need to convert it to another format to be able to read or make edits. A textbox input on a webpage is sufficient for me to read and and write markdown. And when you read my comment, you don't even have to know that it's markdown to be able to read it. The moment you add a structure to it, you need to worry about having compatible parsers or it's going to forget to pull out some of your paragraphs and the like, and if there's a missing curly brace, your parser will throw an error. You'll still be looking at the obfuscated source data Html is already the open standard, but people like markdown instead
- Fnoord 5y agoWell, I have a somewhat fresh take on it, as complex algebra (and therefore mathematics and programming) yields me migraine-like symptoms. Sadly, if I might add. So I am def. in game for the most simple markup language (JSON isn't it, I know that much, its was convenient to pick up hype because people who work with web design already knew JavaScript which was and is popular among web designers or frontend devs as its called nowadays). In the end, its all structured. Even a letter is structured, but just with language and courtesy rules (grammar, for example). There's different levels of quality and complexity in that field, too. There's only so much you can do with ASCII characters to make text more structured. You quickly descent into the world of adding programming syntax to it (one asterisk for bullet point or two asterisks for bold are already). You can keep it very simple, you still gotta know the markup rules, as simple as they are. In gaming, there's an adagio: easy to learn, hard to master. I believe a good language holds true to that. Mathematics certainly does (with exceptions). With regards to JSON though, when you unjustify it, and you use syntax highlighting, is it really that bad? I find the only annoying thing is when you add an entry, you have to ensure the comma is correctly there (or not), but syntax highlighting and habit helps there.