4 ms·
>A CLI or text only approach is going to take longer to learn and be comfortable with I disagree. I once worked on a telephone switchboard, using a old text ba
by mrob 10y ago
>A CLI or text only approach is going to take longer to learn and be comfortable with
I disagree. I once worked on a telephone switchboard, using a old text based interface and a specially designed keyboard with dedicated buttons for all the functions. It took a few minutes to learn what the buttons did. Everything was fast and responsive, and there were no distractions on screen.
I later worked there again after they had "upgraded" to a modern Windows based system. This was far more difficult and slower to use and it did nothing the old system couldn't. Training somebody to push a dedicated button is easier than training somebody to use a GUI. Look at the interfaces people use at fast food restaurants. There's a huge array of dedicated buttons, and it takes very little skill to operate. The only advantage of GUIs over dedicated hardware UIs is lower cost.
- drzaiusapelord 10y agoWell, the real advantage is the button can change or you can add more buttons trivially. Compare the on-screen dialer and keyboard of the iPhone to the old school 9-digit keypad. The former is superior for most use cases. Also you can abstract away your GUI interface with a hardware button if preferred. I'm using a hardware keyboard to type this for example, even though this computer has a touch screen. I have this flexibility and customization options that the old school approach didn't really have.
- digi_owl 10y agoDo haptic feedback mean nothing these days? I can't type shit on any OSK without looking at the keys, or being supported by some spellchecker. But i can type this without looking down because i know when i hit a key etc.