2 ms·
CLI tools exist for composibility. How many lines non-ignored lines are in my git worktree? git ls-files -coz --exclude-standard | xargs -0 cat 2>/dev/null
by paulddraper 7y ago
CLI tools exist for composibility.
How many lines non-ignored lines are in my git worktree?
git ls-files -coz --exclude-standard | xargs -0 cat 2>/dev/null -- | wc -l --
How would you ever create a GUI with that much flexibility?
- ken 7y agoAny ETL tool can do tasks like this. It probably has a terrible user interface, but they're enterprise tools and enterprise tools tend to be terrible, regardless of the style or task. You're right that most GUIs don't tend to be composable -- but that's a function of how they're written, not an inherent limitation of GUIs. There's nothing fundamental about the VT100-style interface that makes it optimal for composition. And GUIs potentially offer some huge benefits, like not having to guess at what's flowing through the pipelines, or having a less painful way to deal with quoting/escaping, or offering an alternative to cryptic flags for configuring operations. Screen editors used to get the same scorn. You probably haven't heard the term "screen editor" in a few decades because every editor today is a screen editor. Once they acquired most of the flexibility of line editors, it turned out that nobody actually preferred line editors. People want composability, and you can do that in a screen editor better than a line editor -- and a GUI better than a terminal. You just have to have designers who care about it.
- alexashka 7y agoHow would I add functionality to add a button that runs that exact command you just typed? By adding an 'add button' with a text field where you type your bash script. All I have to do to make a GUI superior to your terminal is to add some GUI to an existing terminal that people find useful...