[dead]
Slumber a TUI HTTP Client
31–40 of 73 posts
Re: Slumber a TUI HTTP Client
#32> Slumber is a terminal-based HTTP client, built for interacting with REST and other HTTP clients 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 ?
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...
Re: Slumber a TUI HTTP Client
#33TUI stands for "Text User Interface" not "Terminal User Interface" considering that the point of TUI vs GUI is to distinguish text mode from graphical mode. The word "terminal" isn't really meant to imply text even if quite a few terminal emulators are, indeed, text mode; rather it typically means that the UI is drawn by some other machine than the one you're touching. For example, a very popular Windows Server featu…
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.
macOS also call their log viewer "Console" for what I'm sure are obvious reasons to some, but seemingly confuses every beginner developer at least initially, while "console" is what many have come to understand "Text-like entry system to run computer commands".
Re: Slumber a TUI HTTP Client
#34> "To that end, configuration is defined in a YAML file called the request collection" 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?
> less human-readable version of JSON Please provide an example, how YAML can be less readable than JSON. I struggle to think of any.
YAML:
- - "hello"
-
- "hello"
[
[
"hello"
]
]
[["hello"]]
Re: Slumber a TUI HTTP Client
#35TUI stands for "Text User Interface" not "Terminal User Interface" considering that the point of TUI vs GUI is to distinguish text mode from graphical mode. The word "terminal" isn't really meant to imply text even if quite a few terminal emulators are, indeed, text mode; rather it typically means that the UI is drawn by some other machine than the one you're touching. For example, a very popular Windows Server featu…
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)
Re: Slumber a TUI HTTP Client
#36TUI stands for "Text User Interface" not "Terminal User Interface" considering that the point of TUI vs GUI is to distinguish text mode from graphical mode. The word "terminal" isn't really meant to imply text even if quite a few terminal emulators are, indeed, text mode; rather it typically means that the UI is drawn by some other machine than the one you're touching. For example, a very popular Windows Server featu…
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.
Re: Slumber a TUI HTTP Client
#37> built for interacting with REST
I just tried it to verify that claim, but the software does not follow a hyperlink. How did you manage to screw up such a basic feature?
Re: Slumber a TUI HTTP Client
#38looks very polished and neat. Alas for me 10-20ish lines for the json response is really, really not enough
Re: Slumber a TUI HTTP Client
#39Earlier quoted context omitted.
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.
macOS also call their log viewer "Console" for what I'm sure are obvious reasons to some, but seemingly confuses every beginner developer at least initially, while "console" is what many have come to understand "Text-like entry system to run computer commands".
Unix has a dedicated console concept which is the system output. This is more likely to be the hardware console (and maybe synonyms). I think there’s a lot of steps to get to a log viewer named console, though.
Re: Slumber a TUI HTTP Client
#40Earlier quoted context omitted.
> less human-readable version of JSON Please provide an example, how YAML can be less readable than JSON. I struggle to think of any.
YAML: - - "hello" YAML expanded: - - "hello" JSON (typical formatting): [ [ "hello" ] ] And EDN for good measure: [["hello"]] I know which one I prefer :) Silly example perhaps, but once you have X lists nested in Y lists, it does become a lot easier to see why some prefer a bit more visually hierarchically stronger syntaxes
I still prefer ini files for configuration. Easier to grep and sed.