The Heart and Soul of Prototypal OO: Concatenative Inheritance
medium.com
medium.com
Which it calls parent slots[0], the prototype being the "template object" originally copied/cloned to make the current object[1].
[0] http://handbook.selflanguage.org/4.5/langref.html#parent-slo...
This book (2003) has a good summary of the space:
http://www.amazon.com/Prototype-Based-Programming-Concepts-L...
There's a diversity of approaches. Self uses prototype delegates. The language I learned on (LambdaMOO) has a single-delegate ("parent") model. There have been research languages that used pure concatenation. And even ones that had early binding and static types.
Are extend, assign etc really more common than just working with prototypes? I've personally never used it but written a lot of OO code using prototype delegation.
Delegation is heavily used in combination with constructors (both ES6 classes and traditional) and factories. Extension is typically used to apply default values, merge data objects or update multiple properties at once.
The use of extension in a way that could reasonably be called a "form of inheritance" is mostly limited to mixins, which I would say aren't more popular than using prototypes (at least not obviously so).