Did you read it all the way to the end? It's coherent and does give real if debatable reasons for the claims it makes, I think it also does so quite clearly although if I'd written it the ordering of the sections would be different.

Here's an organically grown summary:

• TUIs suck because they are primitive, often buggy, hard to write and aren't accessible. Their existence isn't due to any real technical advantage but more because UNIX historically had a very bad UI toolkit (Motif) which established a 'culture' of TUIs.

• It's now easy (on macOS) to write native apps that use SwiftUI and give a much better GUI. You can just vibe code them.

• Some specific skills, features, templates etc are linked which look useful if you agree with this approach.

• You don't have to give up remote access because there's no reason the GUI has to run on the same machine as the thing it controls. A native GUI can just SSH in to a remote machine and run non-TUI CLI tools to control it. Lots of apps have worked this way and it functions fine.

• On the other hand, TUIs are portable (ish). The author concedes this may sometimes be useful.