3 ms·
Since when you can extend CLI and TUIs, when not given access to source code?
by pjmlp 2y ago
Since when you can extend CLI and TUIs, when not given access to source code?
- johnisgood 2y agoA hell lot of CLI and TUIs are open-source, whereas GUIs are more often (than CLI tools) closed source, though, so it is mainly an issue with GUIs.
- pjmlp 2y agoNot true for MS-DOS CLI and TUIs. Also not true for FreeBSD and GNU/Linux GUIs.
- johnisgood 2y agoHave you found it to be easier to configure GUI than CLI?
- hnlmorg 2y agoVia piping. Unfortunately doing the same kind macros in GUI is a great deal more error prone. As for CLI vs GUI, both have their places. I wouldn’t say I preferred on over the other except for when talking about specific tasks. I’ve also been careful not to state “TUI”. Frankly I don’t see much value making a distinction between GUI and TUI in this type of conversation because they’re ostensibly the same paradigm.
- johnisgood 2y agoThere is also "expect" for automation.