Event driven vs sequential programming

Two different methods to support two different needs. If you have a problem driven by events, then you should use an event-driven methodology. If you need to perform procedures on defined data, but you’re not worried about what’s happening elsewhere, then obviously you want to use a more “sequential” style.

Note that typically, these two things are combined. A program’s startup, shutdown, and maybe a main processing loop (say, a filter processor in an image app) will be largely sequential, while its UI layer and component interactions are event-driven.

Leave a Comment