Yes, indeed! It's a design philosophy, and one that the market does not always reward. I suspect that for many, it is either not salient, or unimportant. Design is subjective, and multi-dimensional.

Thank you, Don for seeing and writing about this dimension.

The very concept of "fairness" won't help you and will likely hurt your efforts to succeed in life. Besides being somewhat subjective, a business must prioritize profit over fairness in order to survive in a competitive environment. Your employer will pay you what they believe (possibly erroneously) is their optimal for profit, modulo the legal environment and company politics.

Gratitude helps, counting your blessings. Also, tackle something meaningful to you that's very hard. It's the striving that leads to happiness, not the attaining.

Sorry; editing mishap, yes. Here's the missing example:

class Holder { var x = 0 } var n = 1 var h: Holder? = ... h?.x = n++ n // 1 or 2?

PS: We have corrected the editing glitch and restored the missing section. Thanks for catching it.

Just watched the vid. IMO the talk does a disservice by minimizing the importance of mutability or immutability and the related issue of static vs dynamic. Are there commonalities? Sure. Are there major differences in what can be expressed or executed? Sure. But I heard no attention to them in the talk. Imperative, dynamically-dispatched imperative execution has different implications than statically-typed rewriting rules.