I think a happier medium/compromise might be to have a way to parse command-line parameters for any tool you want to run, and let the GUI show explicit options you can turn on for any program. To me, having to know the parameters ahead of time is not far enough removed from the command-line experience to make a usable GUI.
Honestly, I wouldn't want to have a dependency on NodeJS and NPM, of all things, just to write a shell script, with limited command support to boot. I'd much rather use vim and shellcheck, and have all of Unix at my command.
The hustle is real: https://hn.algolia.com/?query=guish&type=comment
I was skeptical, but they've been submitting to HN for over a month, ew.
I think a happier medium/compromise might be to have a way to parse command-line parameters for any tool you want to run, and let the GUI show explicit options you can turn on for any program. To me, having to know the parameters ahead of time is not far enough removed from the command-line experience to make a usable GUI.
Honestly, I wouldn't want to have a dependency on NodeJS and NPM, of all things, just to write a shell script, with limited command support to boot. I'd much rather use vim and shellcheck, and have all of Unix at my command.
But I already have a shell.