2 ms·
I prefer to call it "spooky action at a distance." Because what I observe is that's what gets under software engineers' skin... They think the abstraction is to
by shadowgovt 5y ago
I prefer to call it "spooky action at a distance." Because what I observe is that's what gets under software engineers' skin... They think the abstraction is too vague or causes things to happen that are hard to predict, but also hard to trace because the control code is separated from the consuming code, or it has modified the syntax tree or the data at runtime in a place the developer can't directly observe.
This differs from abstraction, which is fine. Abstractions are the bread and butter of programming. But if an abstraction is too leaky, or it interoperates badly with other abstractions applying to the same code... It ceases to be abstraction and becomes spooky action at a distance.
You could implement subclassing in a language via an inheritance chain or you could implement it via taking objects and replacing their various methods and fields with other methods and fields after they've been constructed. One is the object inheritance abstraction. The other is spooky action at a distance.