A REPL like bash already is not a pure text stream, since readline is used. Zsh, even less so.
But they are just convenience features, not in my opinion the defining property. They basically work just the same without them.
Try running plain sh / ash interactively without readline, and notice how much pain it is.
But I agree that having multiple windows, etc is a whole new step; it's just a limited GUI accessible easily via SSH. Could involve sixel graphics as well.
For those who are using Emacs, https://github.com/federicotdn/verb provides similar UX, I have been using it as a postman alternative for quite some time.
Postman has turned from something that's bad, that I put up with, to something that's god awful that I simply refuse to engage with. Now days, I just do everything with curl, shell functions and history
I ran from Postman to Insomnia. Then that was ruined. Now I am onto Bruno. We will see how long that lasts.
Postman has turned from something that's bad, that I put up with, to something that's god awful that I simply refuse to engage with. Now days, I just do everything with curl, shell functions and history
I ran from Postman to Insomnia. Then that was ruined. Now I am onto Bruno. We will see how long that lasts.
TUI 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…
Historically, “TUI” referred to “Text User Interface”, but language evolves and “Terminal User Interface” has been common usage in terminal-app/tooling communities for at least the last decade (probably more). The distinction we (Ratatui) draw is that the rendering surface is a terminal: historically sometimes a physical hardware terminal (someone got Ratatui running on a Minitel a while back), more commonly today a…
Thanks! As I think about terminals in quite different contexts (credit card terminal, battery terminal, train terminal, etc.) I'm realizing that it's really just any kind of endpoint at all, so pretty much any human interface device (HID) should probably be called a terminal. But when taken to that level, using the acronym TUI (in the "terminal" sense) to mean "not a GUI/CLI" (as if big old consoles or emulators/PTYs thereof are the only type of terminals) seems questionable.
TUI 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 s…
> 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.
They didn't. It implies remote drawing and that has at least occasionally included arbitrary graphics. See plan 9 for example.
Postman has turned from something that's bad, that I put up with, to something that's god awful that I simply refuse to engage with. Now days, I just do everything with curl, shell functions and history
I ran from Postman to Insomnia. Then that was ruined. Now I am onto Bruno. We will see how long that lasts.
Same except insert some insomnia forks/clones. Silver lining: if/when Bruno goes, I’ll finally be annoyed enough write my own.
But they are just convenience features, not in my opinion the defining property. They basically work just the same without them.
Try running plain sh / ash interactively without readline, and notice how much pain it is. But I agree that having multiple windows, etc is a whole new step; it's just a limited GUI accessible easily via SSH. Could involve sixel graphics as well.
Virtual terminal is surprisingly capable, it even has word delete feature! And shells have some nice history features which I'm sure would become even more familiar if one had to use them (as I suppose was the case a long time ago), such as !$ that expands to the last argument of previous entry.
TUI 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…
Historically, “TUI” referred to “Text User Interface”, but language evolves and “Terminal User Interface” has been common usage in terminal-app/tooling communities for at least the last decade (probably more). The distinction we (Ratatui) draw is that the rendering surface is a terminal: historically sometimes a physical hardware terminal (someone got Ratatui running on a Minitel a while back), more commonly today a…
Sixels are far from modern :) They were introduced in the VT240 (special purpose version of the 220) and became mainstream on DEC terminals with the 320.