It has been 40+ years of graphical interfaces (58 if you include that Stanford Research Institute "mother of all demos" video). It's been about 10-20 years more for ttys, and TUIs in the form of screen editors go back to the mid-60s IIUC. Shells w/ tty interfaces go back to the mid-60s also.
So TUIs don't have that big a lead over GUIs, and clearly people take well to GUIs.
So maybe -just maybe- there is something about GUIs that makes them difficult to script.
IMO the bandwidth point is important, but not essential. Windows has had a high bandwidth local GUI since ~1990, and we've had RDP and such things be practical for remote access for about 20 years (i.e., since we started getting high-bandwidth networking to homes). In that entire time Microsoft and its developer ecosystem failed utterly to produce any sort of realistically useful and used GUI scripting or even just macro environment -- that stuff never materialized. There have been _attempts_, but none successful.
I believe the issue is a lot like web scraping vs. APIs. If you provide APIs, you can script those, no browser or GUI needed. But APIs are in short supply because:
- GUIs come first
- APIs require backwards-compatibility
(which is a pain for the vendor)
- [web-specific] APIs steal engagement
(which is a problem for sites that
depend on advertising)
That is a perennial problem for GUIs and BUIs, and it seems like it might be inherent to them, for how else to explain that this problem is never fixed? And yeah, scraping is not a good answer.That's my 5-minute thesis. Expect the TUI to remain king for a while now that it's been reinvigorated.