> We do not mean function calls, callbacks, event loops, or other forms of method dispatch. Those are all events that you might need to keep track of in some c

> We do not mean function calls, callbacks, event loops, or other forms of method dispatch. Those are all events that you might need to keep track of in some contexts (editors for example or debuggers). So there is nothing that will never be represented as events. The fact that somebody issued a command is an event that you might need to keep track of in some systems. An example is fraud or security pattern matching. In other words, an event is anything that has happened that you need to keep track of. It can be the fact that a single bit has changed, all the way up to high level system wide events. It all (as per usual) depends on your specific context and business requirements. So any attempt to nail down what is an event and what isn’t independently of context is a waste of time. A key press might be an event we care about in one context and not at all in another.