>Reactive programming frameworks that execute callbacks in response to events can cause really weird bugs if the callback mutates state somewhere
What's the point of a callback that doesn't mutate state somewhere?
What's the point of a callback that doesn't mutate state somewhere?
The framework or runtime calls your function, and the return value tells it what to do next.
Prominent examples include React and Excel.