I've been afraid of this too. I wrote a system in C# that used immutable data and actually used that to do rollbacks when evaluating a scenario failed. My fear

I've been afraid of this too. I wrote a system in C# that used immutable data and actually used that to do rollbacks when evaluating a scenario failed. My fears was that since there are no "val" and really bad immutable collections in C#+.Net the maintenance coder would probably remove list.AsReadOnly() and putting in public on setters as part of fixes to bugs. That didn't happen though, the maintenance guy was really smart and got the ideas without me explaining much more than mentioning immutability. But this is why languages like Scala are important. Immutability and similar design(patterns) are a result of discipline and sometimes convention in languages like Java and C#. It's bound to fail due to humans being humans.