I wonder what that means -- I looked around the docs but didn't see that it interacts with other clients. I thought maybe it would show a generated curl command or something along those lines. But perhaps it's just a typo for HTTP servers?
Genuine question, why do people use YAML? I've been using it a little bit recently (reading existing documents, not writing my own), and it just seems like a more overcomplicated and less human-readable version of JSON? With potential security vulnerabilities?
Please provide an example, how YAML can be less readable than JSON. I struggle to think of any.
Also I really don't like the hyphen notation... This is very unreadable to me:
- a
- b: c
- - dBecause people LOVE overcomplicated shit. You see it happen everywhere.
You can also try out Voiden : https://voiden.md/ which has a different approach to this.
Also YAML is a interesting choice - any reasons for this.
PS : I am associated with Voiden.
But it looks very cool!
(plus custom theme customize-able & much less work for the devs to build & maintain, and way less dependencies)
Even X had a separate application called xterm 42 years ago: the complete X system was not to my knowledge called a terminal system, except perhaps when discussing the dedicated client devices, such as VT1300. Also the term "virtual terminal" as far as I know has always referred to a the kind of interface this application is making use of.
So I think we can just accept that the term is overloaded such that "terminal" refers to both of these situations, as there is no historical precedent to have it exclude the other situation, and the term "terminal-based application" is completely clear to a rational listener.