5 ms·
> But it's also common to use "CLI" to include "TUI" programs [...]. It is indeed common, and (IMO) it is harmful, as TUI programs are just GUI programs in dis
by rollcat 4y ago
> But it's also common to use "CLI" to include "TUI" programs [...].
It is indeed common, and (IMO) it is harmful, as TUI programs are just GUI programs in disguise. They do have two unique strengths: readily accessible over a serial console or an SSH session; and being the lowest common denominator of GUI programming. But they don't share any of the typical (desirable) qualities of CLI programs; typically, any CLI features (if present at all) are an afterthought.
$ ls | vim
Vim: Warning: Input is not from a terminal
- deleted 4y ago[deleted]
- tomrod 4y agoDenotatively, you're 100% correct. Connotatively, I have no concerns and won't revisit the comment, but will keep the distinction in mind when addressing a technical audience.
- bee_rider 4y agoThe other way around, vim | ls Is a 100% foolproof and very “loud” sign that today is a scatterbrained day and I should write off the idea of being productive. Or I should have another cup of coffee.
- ajolly 4y agoThank you for drawing this distinction. I had not mentally realized the difference before, this makes me interested in trying TUI programs. Will go check lynx out today.