I thought it was clear that I was talking about the hitboxes and hurtboxes . None of the jabs hit anywhere behind the character , even behind their center point . Or even reaching the center point . They ' re all just attacking forwards , which can easily make contact with the hurtboxes of a character who ' s on the other side . So the effective behavior is landing a hit on a character that ' s behind . That doesn ' t mean the attacks are hitting backwards in the sense of targeting areas behind the character . <| sep |> he was a marine for nearly 3 years , too . That genuinely surprises me . I don ' t mean to say he ' s a slouch , but he sure as fuck doesn ' t look like an exMarine . <| sep |> If you want to run full desktop applications you don ' t even need to do it locally thanks thanks to RemoteApp and the like . You certainly don ' t need to connect car battery to be remotely executing software on hardware powerful enough to weld the wheel nuts on your car . You don ' t even need to be constrained to any particular architecture . That ' s just not an issue . Where things get funky is where developers start designing to a lowest common denominator across disparate paradigms for usage scenarios that are simply different . That ' s when you get awkward hybrid paradigms which Windows is currently under . Accept the limitations and advantages of each form factor and build to their strengths . Cross over at the data point if you want continuity . Separate out the core logic from the user interface for write once sell anywhere really isn ' t that interesting from the customer perspective . There ' s much better way to approach edge cases like users wanting to run large factor applications on small factor handheld devices that don ' t require sacrificing everything to the generic lowest common denominator .