I'm trying to understand the "JavaScript way" of creating and using objects and I think I'm running into a misunderstanding of an object and a prototype.
In a new project I've started I've decided to try out prototypal inheritance. I'm confused if this means I should just create an object that I intend to use and then create other objects based on that using Object.create()
such as:
var labrador = {
color: 'golden',
sheds: true,
fetch: function()
{
// magic
}
};
var jindo = Object.create(dog);
jindo.color = 'white';
Or if I should create a kind of class and that create instances of that using Object.create()
.
var Dog = { // Is this class-like thing a prototype?
color: null,
sheds: null,
fetch: function()
{
// magic
}
};
var labrador = Object.create(Dog);
labrador.color = 'golden';
labrador.sheds = true;
var jindo = Object.create(Dog);
jindo.color = 'white';
jindo.sheds = true;
Having much more experience in Class-based OOP the latter method feels more comfortable to me (and maybe that's reason enough). But I feel like the spirit of prototypal inheritance is more in the first option.
Which method is more in the "spirit" of prototypal programming? Or am I completely missing the point?
Every object in JavaScript has a built-in property, which is called its prototype. The prototype is itself an object, so the prototype will have its own prototype, making what's called a prototype chain. The chain ends when we reach a prototype that has null for its own prototype.
prototype is a property of a Function object. It is the prototype of objects constructed by that function. __proto__ is an internal property of an object, pointing to its prototype. Current standards provide an equivalent Object.
Prototype-based programming is a style of object-oriented programming in which classes are not explicitly defined, but rather derived by adding properties and methods to an instance of another class or, less frequently, adding them to an empty object.
The most important difference between class- and prototype-based inheritance is that a class defines a type which can be instantiated at runtime, whereas a prototype is itself an object instance.
The prototype
is just another object to which an object has an implicit reference.
When you do:
var obj = Object.create( some_object );
...you're saying that you want obj
to try to fetch properties from some_object
, when they don't exist on obj
.
As such, your second example would be closer to the way you'd use it. Every object that is created using Object.create(Dog)
will have in its prototype chain, that Dog
object. So if you make a change to Dog
, the change will be reflected across all the objects that have Dog
in the chain.
If the main object has the same property as exists on the prototype object, that property is shadowing that property of the prototype. An example of that would be the null
values you set on properties of Dog
.
If you do:
var lab = Object.create(Dog);
lab.color = 'golden';
...you're now shadowing the color
property on Dog
, so you'll no longer get null
. You're not changing Dog
in any way, so if I create another object:
var colorless_dog = Object.create(Dog);
...this one will still get the null
value from the prototype chain when accessing the color
property.
colorless_dog.color; // null
...until you shadow it:
colorless_dog.color = 'blue';
colorless_dog.color; // 'blue'
So given your example:
var lab = Object.create(Dog);
lab.color = 'golden';
lab.sheds = true;
...it looks something like this:
// labrador // Dog
lab.color---> color:'golden' color:null
lab.sheds---> sheds:true sheds:null
lab.fetch()--------------------------> fetch: function() {
alert( this.color ); // 'golden'
// "this" is a reference to the
// "lab" object, instead of "Dog"
}
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With