Suitability of Event Driven Languages

Suitability of Event Driven Languages

Even driven can refer to any type of event, it is not necessary that it always thought to be linked to the programming side. Every day objects use event driven, particularly those products or objects which need to handle responses or requests. There are many non-graphical applications which use event driven programs. An example it a air conditioner. A air conditioner uses event driven programs because it has sensors. When it is hot they you may turn on the conditioners an supply cold air likewise when it's too cold you will turn it off. You also have an option to set the temperature when you do this and want to confirm it you will press a button and an event will be triggered where the conditioner will take the input and will output the cold air through the heater inside. Another example is a fire alarm. An fire alarm will sound off when it detects smoke, When it detects smoke an event is triggered and in response an alarm is sounded, This is one of the more important products which use event driven programs. As you can see the answer to the question is that Event driven programs are most definitely suitable for non-graphical applications. Lastly my last example is the fuel tanks in a car, When you are running low on fuel and even is triggered and a light flashes on your dashboard indicating this, This makes life a lot more easier as you will know when to fill up your fuel and when your running low. In a nutshell Event driven programs are most suitable for non-graphical applications. However for non-graphical applications you could use procedural programming, but event driven is now used in everyday products and its the way forward.