[DonHopkins]

I'm sure somebody can come up with a better term than "master/slave", for an equitable relationship between hardware or software that's harmoniously cooperating towards a shared goal by willfully and respectfully delegating authority.

Even the old telnet protocol politely and consensually negotiates with will/won't/do/don't, and it's not protocolly correct for a server to rape a client, who historians then romanticize as a mistress.

Another common metaphor that I find cognitively dissonant is calling the relationships between nodes in a tree "parent" and "child", since all humans have exactly two biological parents, but all tree nodes have only one parent.

https://www.quora.com/Can-a-binary-tree-node-have-multiple-p...

[another-dave]

& why are Strings made up of chars — surely a string should be made up of Threads?

[amygdyl]

Commander - Receiver Instructor - Actor

Off top of head

[wruza]

[super]<class> and [sub]<class>s (or simply 'subitems'). Like in superview and subviews, group and subitems, superclass and subclass.

[DonHopkins]

Yes, that's a great example of why it's always good to use names that describe the nature of the relationship, because nodes can exist in multiple hierarchies at once, that have no topological relationship to each other, like a view hierarchy and a class hierarchy.

A Button can be inside a Panel, but not a subclass of Panel.

A Button can be a subclass of Control, but not inside a Control.

Having two types of parents (view and class) is different that having two parents (mommy and daddy).

[fanf2]

There are situations with IVF where a child may have more two parents, e.g. when the genetic mother is different from the gestational mother.