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:
- 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.
- 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, criticism and/or practice:
“A friend of mine spoke of books that are dedicated like this: “To my wife, by whose helpful criticism ...” and so on. He said the dedication should really read: “To my wife. If it had not been for her continual criticism and persistent nagging doubt as to my ability, this book would have appeared in Harper’s instead of The Hardware Age.””
—Brenda Ueland (1891–1985)
“A bad short story or novel or poem leaves one comparatively calm because it does not exist, unless it gets a fake prestige through being mistaken for good work. It is essentially negative, it is something that has not come through. But over bad criticism one has a sense of real calamity.”
—Rebecca West (1892–1983)
“The practice of S/M is the creation of pleasure.... And that’s why S/M is really a subculture. It’s a process of invention. S/M is the use of a strategic relationship as a source of pleasure.”
—Michel Foucault (1926–1984)