Suitability of Event Driven Languages for Non-Graphical Applications

Event-driven languages are very suitable for non-graphical applications. They are also very suitable for graphical applications also but in this blog I am going to explain why they are suitable for non-graphical applications. There alot of electrical systems that everyone uses and could be classed as an event-driven program.

For example, a microwave can be classed as an event driven system; you press a button or turn the timer-knob and the microwave starts heating up your food. This is an example of event-driven application as you get an action from an event. As this event driven system, is fully functional and does the necessary requirements then this makes event driven languages suitable for non-graphical applications.

Another example of why event driven languages are suitable for non-graphical applications are electric/touch hobs. An electric touch hob needs the user to touch the buttons on the hob for the hob to change temperatures. Once the button is touched, the application running the hob would need to make an action happen, due to the event created by the user.

So even though event driven languages are usually used to code graphical programs, such as windows forms or PC operating systems, event-driven languages can be used to create non-graphical applications like a microwave and a hob in the examples above.