It is alos why CUI bet GUI everyday, except in one category. That one category, is ease of use, but fact is lost on most a GUI programers. They go for scaling text when it gets focus or scroll bars showing it working, but forget the teaching part so the user learn.
One though project I did was GUI interface provide the learning and CUI functionality for SPEED typists up to 100 words a minute. Design was CUI interface with GUI presentation, better know as screen scraping. This even allowed for it run over 19k baud modem with the same response times as they had directly connected to network, because a screen change was 2k of characters with lots of blanks, so was compressible and transfers in sub-second response time. Drop down boxes for the mouse generation worked just like you expect a drop down but shwed two columns the text form like you expect and second column showing the speed codes. The a speed typist use the speed codes based on the codes they had been using for 20 years, with a / as the lead/shift character.
This is what I learned too. For fast (data) typists you should still use a CUi. There is no GUi that is fast enough to keep pace of a fast typist. Even a CUI in a windowed environment will still be faster then any GUI form.
"If I do not want others to quote me, I do not speak." -- Phil Wayne