Quote:
Originally Posted by JSWolf
The reason there is no need is that you can do everything with the touch screen that you can with the buttons. That's why there is no need. Need and prefer/want is different. While you may want and prefer buttons, there's really no need.
|
As I wrote, you have completely disregarded my conclusion and its example: «Try for example scrolling web pages through swipe on EPD using software that is optimal on fast screens. It depends on what you are doing». I stated that - for example - some software only offers "swipe" on touch, not "pg-up and pg-down", and the latter are only implemented through key events.
In such case (just for example), in a C-R-B, in the "have-option" branch the device may cost less than three dollars more (or three cents, depending on production size), in the "I-find-that-the-option-is-not" branch, people die. I see the two outcomes heavily biased towards the extra three dollars|cents expense.
AND back to the principle, even when
strict need of a feature
to get a specific function is not there, "having the option" is superior. That is freedom.