Make a TUI look pretty enough, throw in enough features from a GUI, and it becomes a GUI (sort of). No reason why one couldn't mix & match features as desired.

Make a TUI look pretty enough, throw in enough features from a GUI, and it becomes a GUI (sort of). No reason why one couldn't mix & match features as desired. Compared to a commandline, both TUIs & GUIs add discoverability: no need to remember commands or -switches, just navigate through menus & see what's there. I think all these are best regarded as different 'views' on the same underlying machinery. What works best depends on user preference / workflows. Resource requirements obviously depend on the feature set & implementation.