I don't want to be dismissive, but this article talks about the graphics APIs and the hardware architecture (x86) yet fails to address the elephant in the room there: Cider ports. That is, macOS games which are actually Windows games running atop the the WINE-based proprietary middleware known as Cider.

Cider has both been a great boon to Mac gaming — it makes it cheap and quick to port Windows-only titles to the Mac without having to make them internally cross-platform — and also a great detriment: its Windows translation layer imposes a performance penalty and prevents true native feel, and crucially, many such games are using Cider's slow Direct3D-to-OpenGL translator, which is not only slower than real Direct3D (thus why such games will always run better under Windows in Boot Camp on the same hardware), and limits you to the Direct3D 9 featureset, but it is also translating to a graphics API Apple basically don't care about now (OpenGL).

The good news is that more and more games are using commodity engines, and those engines usually have proper native macOS support, and ideally Metal support. Nonetheless, Cider ports are very much a thing that must still be contended with.

For a recent high-profile case of Cider causing trouble, Square Enix went the cheap route when they ported their MMORPG, Final Fantasy XIV: A Realm Reborn, to the Mac, and used Cider. The result was infamously bad and they had to pull it from the shelves. They did of course fix it up and re-release it, but even then, the resulting port is slower than and graphically inferior to simply running the game under Windows, because it's stuck with fake Direct3D 9. On Windows you get to choose between Direct3D 9 and Direct3D 11.