• Event Driven
• Data Driven
• Standard, traditional game loop thingy
• Model-View-Controller

Thats not an either/or choice; you can:
Use a game loop so that you've got a (soft) real-time system, data-drive gameplay and content systems so that artists and designers can make changes without having to write code, add events to that so that level designers can have a door open when the player stands in a zone, and use MVC within the GUIs.
Don't pick up a screwdriver and declare it to be the one true tool to rule them all.