> Third one is when you learn that the behavior of any imperative language (down to the working of the microprocessor data paths) can be fully represented in a pure functional rewrite language (without destructive assignment / cell state changes).
What no one is ever able to explain is: why is this a good thing?
The underlying machine does destructive assignment. The whole thing is a big mutable array. Why should we represent it in another way?
The difficulty of a given problem changes depending on the perspective you're looking at it from. That's why understanding different models helps.
Optimizing deeply enough will eventually make any abstraction leaky though, so you'll never fully escape mechanical sympathy.