You still need similar memorisation when using a GUI.
You don’t give the GUI process a second thought as you’re used to the steps, similar to those using the terminal.
For example, in Windows to create a new text file, save it, and copy it.
You need to know the name of the application (notepad), how to find and open it from the Start menu, the steps within notepad to save the file and the path to save to (file -> save -> navigate to path), the name of the file explorer (Windows Explorer) and how to find and open it, how to navigate to the file, the steps to copying a file (right click copy or ctrl-c), and pasting the file (right click paste or ctrl-v).
On the terminal, it’s a case of remembering commands/switches:
vim document.txt
:wq (write quit)
cp document.txt documentnew.txt
rm document.txt
Both processes require memorisation of specific sequence of steps which overtime you’ll become accustom to and not have to actively think about when repeating a similar process.
My preference is the terminal as it is quicker and simpler in most instances and without the clutter of everything that comes with a GUI application.
You’re misunderstanding the point of my comment.
It wasn’t competition of how quick it is to complete that specific task in the terminal vs GUI.
That way suites you as you’ve learned it, you’re used to it, and is part of your workflow. It’s efficient for you, that’s great. The terminal suites me as I live and breath it, in and outside of work.
There may be things I do on the command line that would be quicker using a GUI, yet I do it anyway as it is simpler.