GUI is just sequence of events (mouseclicks, scrolls, keypresses) on top of semantic tree (if we can call div class soup as "semantics"). But we can record it s

GUI is just sequence of events (mouseclicks, scrolls, keypresses) on top of semantic tree (if we can call div class soup as "semantics"). But we can record it since long time ago and simply compress/remove noise. TUI is better since it usually operates on keyboard, it's good for visualizing 1d/2d data (which is most of GUIs btw). CLI is least interactive of them all I'd say and it limits what you can do. Either you have a solved problem that you can trigger with a button push, or you have to input tons of flags to configure behavior, or write a config file and re-use it. To me this seems sub-optimal. I'd rather use voice activation + NLP to let LLM figure out what I want to do, present me with a quick "are you sure? + exact CLI command" and then I can press it. Forgive me for lengthy text, I was just thinking outloud whether my assumptions about TUI/CLI make sense. Do you agree?