I think he ' s trying to say that these complicated decks require people to map out their gameplan in the early game , hence they ' d spend more time in the earlier turns deciding what they ' re gonna do later on . <| sep |> This is a great tip in theory , but in practice , browsers have weird quirks that have nothing to do with whether they support a feature , and everything to do with the shortcuts and optimizations they make and the bugs they have . If you think it ' s possible to avoid device detection across the board , you simply haven ' t worked on projects demanding enough to realize the opposite . Especially if said projects make heavy use of animation , and you don ' t have the infinite budget to spend on trying to figure out the perfect refactor to your entire codebase that works glitchlessly in every device browser OS that you have to support . Yes , you should try to use feature detection whenever possible . Yes , that will be enough most of the time . And for the times that it ' s not , you should find good ways to figure out what device the user is using , so you can ship a relatively bugfree product and move on with your life .