the difference between fumbling around a GUI file manager looking for the correctly named file and using one of the many solutions the terminal offers is night and day. GUI's are clumsy and prone to extremely odd failures where the only solution is to exit and reset. Greyed out buttons when they shouldnt be etc... The terminal doesn't have these problems, if something fails you can see the error, its immediately responsive always, its composable and scriptable. Consider cutting up audio clips in audacity, doing it by hand can take ages and the GUI can crash and screw you over. With the terminal you can just take 2 minutes to write a burner script and use it and be done in seconds. Its really hard to describe the positives of the terminal over a GUI because they are radically different things, and new users are going to have a tough time setting up a friendly environment, but if you can get past that its extremely easy to see why they handle certain tasks a million times more efficient and resiliently.
So in a good Windows file manager here is how you can fumble around looking for the correctly named file:
press a single key
enter part of a name
get a fuzzy match for any file on your system in a separate tab (which you can return to later if needed)
sort by path/size/image width to filter further
press a key to preview file content or copy a file or delete it
All that with immediate visual feedback
What's your terminal day solution to this?
> if something fails you can see the error,
Or you can't, it just silently deleted the wrong files and you're non the wiser since you don't even see that your filter mismatched
> With the terminal you can just take 2 minutes to write a burner script and use it and be done in seconds.
How would you pick the audio times? In audacity you can easily play on cut thresholds to hear that they're correct, what's your "seconds" solution to that?
