Hacker News new | past | comments | ask | show | jobs | submit login

> Both stores use TUI interfaces for their instore service apps, and boy are they fast with them. They reserve GUI things for the self service point of sale systems and keep the TUI for cases where speed matters.

What magic makes TUI faster than GUI?

TUI just use glyphs to render the interface. AFAIK that's not faster that a proper graphics engine.

Keyboard shortcuts are not exclusive to TUI.

Maybe if we would stop hyping UI gimmicks and put more focus on fundamentals, there wouldn't be so many bad GUI apps.




It's not keyboard shortcuts, it's pure keyboard input; an important distinction to make, as with modern GUI interfaces, keyboard input is often an afterthought.


Just like TUIs can accept mouse input, GUIs can be operated without one.

The only difference is that TUIs are worse at displaying... text (and graphics)


I fully agree. I made a TUI client/server framework loosely modeled around the concepts of CSS/HTML. One of my core design decisions was keyboard only input.


I agree. I wish there was a common way to toggle keyboard navigation hints in GUIs. Like F1 is often help, F2 rename etc.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: