"Event driven" is also known as "message based". This architecture is really meant for distributed systems. Some variation thereof is about the only practical way to allocate a sub-task to a non-local computing device.

Multi-tasking can be thought of a local inverse of a distributed system. Instead of distributing tasks, it's finite computing capacity that is being distributed to multiple, concurrent tasks.

OOP is yet another case where event driven/message based architecture often pops up. Basically, this is often a mis-guided attempt at simplification by way of sub-task distribution among arbitrary, artificial "objects".

It should be intuitively obvious that event driven architecture is a complication (not a simplification) which should only be applied when there is no better, more practical alternative.