tyrrrz

I mean, if you're not the sole user of the tool, you can't guarantee that everyone can log in (or would want to)

If you can afford to always be logged in, then sure, but it's not always an option. Especially if you need a general solution.

Glad to hear that :)

The only environments where self-contained deployment matters are the ones you mentioned: browser, mobile phone, and also desktop. So yes, 45mb is a big difference (actually my app is 250mb).

Quoting the article:

> It may also appear that the details we have to take into account here are not that different from the implementation-aware assumptions we were making when using mocks, as neither are actually governed by the interface of the component. However, the major distinction is that the coupling we institute here is between the test double and the real implementation of the component, rather than between the test double and the internal specifics of its consumer.

Can you expand on what you mean by "a trivial mock implementation"?

To me "avoiding mutations" does not mean "no mutations", but rather "no mutations in-between states in a state machine". The system should model state as an immutable snapshot, while mutations when forming that state are completely acceptable.