Slumber a TUI HTTP Client

TUI also means terminal user interface.

But this is wrong:

> it typically means that the UI is drawn by some other machine than the one you're touching

I guess you're conflating thin-client terminal in the networking sense vs vt100 hardware terminal lineage (where "terminal" comes from here), but it means a text mode interface that runs in the terminal emulator and uses, say, ansi escape sequences.

Rather, when you see TUI, it just means the app runs in one of your kitty panes.

Btw, your "Terminal Services" example doesn't show that "terminal" implies remote drawing. It shows Microsoft extended the word to cover remote GUI sessions, which is a later, broader usage.

On the other hand, there are many elements in the user interface that are not text. In fact, I think it would be quite understandable if one even separated REPLs like bash or octave to be "text user interfaces" while applications that make use of character placement and border special characters "terminal user interfaces", because they use means beyond text stream to communicate with the user. One might even render straight up graphics to a terminal [emulator application].

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.

I would argue that a local only session with terminal.app is still a real terminal session because the app is just a terminal for the connection to the MacOS version of getty. In principle, this is not different from having a serial cable between the host and an old-style terminal or encapsulating that connection over a different network like with SSH and telnet etc.

Very much agree - "Text User Interface" is also a much clearer descriptor for non-technical users to understand. Normal people have an immediate idea of 'text' but not of that 'strange nerdy terminal thing' - and that's important because often times a good 'Text User Interface' is all that even regular people need !

(plus custom theme customize-able & much less work for the devs to build & maintain, and way less dependencies)

If it is just an acronym, they can define it as they wish in my opinion.

As long as they defines it first (and they did)

Maybe it's referring to the CLI, since you could pipe to/from it? There's an example relating to curl: https://slumber.lucaspickering.me/user_guide/cli/subcommands...

I used to write Python scripts with Requests or run from terminal. It has a nicer syntax, all LLMs know it, and we all used Python in the backend.

https://docs.python-requests.org/en/latest/index.html

If not using any esoteric features, it's more human readable (imo), easier to write, can have comments and has some useful features like different kind of multi-line values. JSON is valid YAML, by the way.

> less human-readable version of JSON

Please provide an example, how YAML can be less readable than JSON. I struggle to think of any.

People use YAML because a bunch of other people use YAML. Whatever its warts, there's no use resisting it.

> it just seems like a more overcomplicated

Because people LOVE overcomplicated shit. You see it happen everywhere.

There’s lots of overengineered features in YAML that are problematic, but at a high level, it’s much, much more human-friendly than JSON. And if you love JSON, good news: it’s 100% valid YAML.

Because as long as you stay away from anchors and inline JSON, YAML is a perfectly workable, structured, human-readable format that supports comments.

This is awesome! OpenAPI integration is a great feature.