*TRUE* OOP and Other Paradigms

[NightmareX1337]

Setters are often a sign of a poorly designed interface, because values are usually related (length of a dynamic array is related to the data in the array), so allowing them to be modified in isolation can often cause bugs, and many properties that really can be changed in isolation are often set once when the object is created and then never changed again (color of a label for example), so allowing the value to be arbitrarily changed at runtime is a terrific way to waste memory.

I completely disagree. Setters are not often poor design. Sometimes they are, but it's rare and not hard to notice (like your length example). The real problem is public variables, they are head to head against encapsulation.
Also, your label color example is horrible. Why would I waste memory for assigning color a different value? Why on earth color of a label is not changed in runtime? And why should it be immutable?