In this case I might be able to get away with just update, I'll need to dive into the actual implementation of update more to verify assumptions I am making, but my understanding is that if we were to rely on update for Maps then we would be creating new instances of the Map rather than sharing/mutating the same underlying Map in memory - which is why I am using the createNotifier pattern which facilitates mutating something and then notifying of that mutation. The old mutate method served the role of mutating an existing value and notifying rather than returning a new value like update. But again, I could be making some incorrect or outdated assumptions here.
