Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You've actually got it backwards.

There's a reason that mice and keyboards are faster and more accurate than touchscreens, and it's that there is a physical+visual feedback occurring that our brains are used to processing when handling other physical objects. Touchscreens have no haptic component (or they have a vibration that is disconnected from the action that you're actually doing on the screen), so you're relying entirely on visual cues. It's slower and less accurate. Compare max WPM on physical vs touch keyboards, for instance.

Moving to AR/VR is even worse, because the lag time is much larger than on a touchscreen, and in the case of VR, your hands are completely hidden.



Keyboards may be more efficient, but do you see people using blackberries today? If your theory was correct, we wouldn’t all be using touchscreens.


> we wouldn’t all be using touchscreens

We're not, for tasks that require speed and accuracy (like typing). We're mostly using keyboards and mice/ trackpads. Touchscreens are used on low-impact, secondary devices like phones or tablets.

I've never once seen someone, whose work is digital, replace their computer with a phone as their primary work device.


Sure, but where did I say that work computers would be replaced by VR/AR? In my original comment I specially said phones might seem anachronistic. And the usage of phones (computing devices) almost certainly dwarfs usage of standalone computers.

You are somewhat arguing against a straw man here. I was talking about phones being unnatural and thus replaced by AR/VR.


I was arguing against what seemed in your comment like you were saying that touchscreen keyboards were a progression from physical ones, and then from touchscreen ones a progression to AR/VR.

I agree that pane-of-glass, non-reactive and non-tactile input is unnatural, but AR and VR are literally that turned up to 1000. Doing the zoom finger-pinch in midair is even less natural than doing it on a glass screen.




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

Search: