As with any feature, it must be used properly.

But, from an OOP perspective, modelling state changes is natural and desirable. So mutability seems a sensible default.

It's only the recognition of issues that can arise from state changes that has us wanting to lop off the entire feature. A rather strange and drastic "solution" in my view.