mutate

Client server is about having more than one consumer that needs to share and mutate the same data.

If two threads invoke methods which mutate (or read) the internal state, then inconsistencies can result if not properly synchronized.

The usual reason people give for believing this is the inability to mutate closed-over variables.

It actually feels wrong to be using immutable data within the stores since a store's primary job is to mutate data.

Or a Monsanto GMO crop that decided to mutate and completely destroy our planet.

Data binding is designed exactly to prevent the need to explicitly mutate all the views at every point that the model can change.

And, that's the thing: OOP represents a stateful paradigm, in the sense that operations may be performed which mutate the state of an object.

Reagents expire, lab-cultures will mutate, equipment rusts/breakdowns/gets contaminated for stupid unforeseeable reasons.

But at the end of every chain I have a db query and most of those mutate some data or other.

If you can't mutate it, how do you write to it?

Vegetarians notoriously frustrate catering, while I think people who agree never to mutate data are probably easier for programmers to cater for.

If you must mutate references, use let instead of var.