Event-driven Programming - Criticism and Best Practice

Criticism and Best Practice

Event-driven programming is widely used in graphical user interfaces because it has been adopted by most commercial widget toolkits as the model for interaction. The design of those toolkits has been criticized for promoting an over-simplified model of event-action, leading programmers to create error prone, difficult to extend and excessively complex application code:

Such an approach is fertile ground for bugs for at least two reasons:

  1. It can lead to writing code within the event handler for each possible value of various values in the program, making the source code hard to understand.
  2. In places where the event code changes variables shared throughout the program, it can require the programmer to write convoluted algorithms to avoid unwanted ripple effects.

Read more about this topic:  Event-driven Programming

Famous quotes containing the words criticism and/or practice:

    “In criticism I will be bold, and as sternly, absolutely just with friend and foe. From this purpose nothing shall turn me.”
    —Edgar Allan Poe (1809–1845)

    “As an example of just how useless these philosophers are for any practice in life there is Socrates himself, the one and only wise man, according to the Delphic Oracle. Whenever he tried to do anything in public he had to break off amid general laughter. While he was philosophizing about clouds and ideas, measuring a flea’s foot and marveling at a midge’s humming, he learned nothing about the affairs of ordinary life.”
    —Desiderius Erasmus (c. 1466–1536)