I read the article. Parent's comment about automation is spot on. TFA didn't describe any GUI interaction in detail, or even suggest that there was a way to achieve these goals without needing a meatbag to physically interact with the computer (and capture its output in /dev/meatbrain).

But at least TFA wrote up the criticism in text, even transcribing some of the screenshots.

More easily maybe, but the CLI command is deterministic and works as long as the user can successfully paste it to a terminal and run it.

For UI you need to figure out different locales, OS versions, etc.

theshrike79 was talking about automating. Automating using an UI requires you to have a program which can simulate click events and a Display server which allows this. It's also really brittle, because you are not actually depending on the action you want to invoke, but on the UI location this action is exposed at.

Automating terminal commands is easy, because that is how the OS works anyways. All programs invoke each other by issuing (arrays of) strings to the OS and telling it to exec this.

I’ll paraphrase a user named Bear from Usenet a few decades back: if all you know how to do is point at what you want, you’re operating at the level of a preverbal child.