Human interacts with objects and these interactions are rooted in intention. Intention becomes a plan, and finally that would be a process. Looking familiar structure truely depends on how to do alike as we do. This paradigm invokes a great development environment: Event-based development.
Traditional programming process has its entry point, like main() function in C and the structure adopts the one way, imperative design. But life is not that simple for many events occur in every second. It is the reality, and traditional model is not proper solution for complicated world nowadays. That is the point that event-driven programming can be a solution. In the context, each event makes its entry point and may call the handler procedures.
Event is a sort of interaction and process is the thing which does something intended and planned in advance. The role of programmer is just to plan the structure and to connect events to pertinent procedures. Limited input devices are prevailing that it is so lucky to developers that they don’t need to concern matters out of the range.
A good example of event-driven development environment is web. Server application listens to any request and do something for client who wants response expected. It is not a kind of new thinking but does a great role in even a cloud computing technology and other new coming edges. Believe it or not, I convince that this model would survive more than 20 years for it is the very simility to human nature. The change would be in how to weave the abstraction and how to capsulate the inner model and contents.
High expectation yields abundancy in the reality. And you know what? Expectation is a kind of event as well. Service and experience is a looming keyword in the 21st centuries industry going through the main stream now. It is the era of interaction and it accords with new trend like SaaS and PaaS. No one-way, broadcasting level communication anymore.
