This article can basically be boiled down to saying sharing mutable state everywhere is bad. The primary point of OOP is the mutable state of an object should n

This article can basically be boiled down to saying sharing mutable state everywhere is bad. The primary point of OOP is the mutable state of an object should never be shared with other objects. I understand where the author is coming from because many bad, large code bases use OOP Java to share mutable state, but this is the result of the coder attempting to write procedural code in OOP. The author somewhat acknowledges this by referencing Alan Key's definition, but this goes to show in practice no one really has a monopoly on defining OOP. Better to throw out the bad parts and keep the good parts than to throw out the baby with the bath water.