(* Some of the programmers at our company HQ like to make everything event-driven *)
Even for batch-oriented processes? Event driven is great for interactive stuff, but to use it for batch-like processes is asking for complexity that does not need to be there IMO.
(* But this can lead to a a game of ping-pong trying figure out what's going on *)
What is really fun is recursive events, especially with long chains between each loop, not just self-calling-self.
Is it still called recursion if there are multiple callers in between? Or just "circular"?
Simple recursion is like:
ABBBBBBBBBBBBBB....
(Where each letter represents a routine/method.)
But event-triggered recursion can be like:
ABCDEFGCDEFGCDEFGCDEFG....
Makes debugging nasty.