3 ms·
I know it’s one data point but I never developed muscle memory for remotes the same way as, let’s say, Emacs. I always stumble and press the wrong keys. More im
by 8ytecoder 7y ago
I know it’s one data point but I never developed muscle memory for remotes the same way as, let’s say, Emacs. I always stumble and press the wrong keys. More importantly the interface on the TV is convoluted. I don’t want next channel - I usually want to go to a specific channel. With, say, Apple TV it means scrolling through a bunch of apps - much faster. Or YouTube tv via chrome cast - scrolling through the guide on the touch screen.
- klodolph 7y agoSame here. Except for one or two functions, I would always end up squinting at a remote in the dark to try and read the labels. I like remotes like the Apple TV remote and the Roku remote (except for the fact that the Roku remote is a piece of utter garbage and I want to have strong words with the designer) because they focus on the essentials and let you do everything else through menus. (The Roku remote is an utter piece of trash for a couple reasons. First, it chews through AA batteries like it’s going out of style. Second, it is not responsive—there is a agonizing delay between when you press a button for the first time and when the action takes effect. My guess is that these defects are because it uses WiFi to communicate with the device, and I can’t understand why anybody thought that was a reasonable technology to choose.)