Crafting a high-performance TV user interface using React
Interface performance is one of the strangest problems to have in this age of crazy processing power but it is extremely common.<p>Some of the delay is just plain silly and avoidable, like having long and synchronous <i>opening</i> animations in response to an action, which only serve to waste the user’s time.  (Oh how I love being on a web site like AT&T and watching their JavaScript poorly zoom open a blank box from the center of the page for 2 whole seconds, when I KNOW they could just show me the damned page already.)<p>In other cases, the source of the slowdown is less clear.  Is a physical device just not delivering its signals any sooner?<p>I’ve played games where you have to walk to a <i>very</i> precise spot, hit a button, and wait literally <i>one whole second</i> before <i>ANY</i> response is visible onscreen or in audio.  (And if it turns out you didn’t really take the action you thought you did, you have to walk in circles to try a slightly different spot, and wait again).  Why should that ever be the case?  How can a super-fast console not immediately display <i>something</i> or play <i>some</i> sound to show that you took the action?