Ndtyjky

I read here we can use Object.create to achieve inheritance

Here is an example with a Rectangle which inherits from Shape

function Shape() {}



function Rectangle() {

  Shape.call(this);

}



Rectangle.prototype = Object.create(Shape.prototype);

Rectangle.prototype.constructor = Rectangle;



var rect = new Rectangle();

I am wondering if using Object.setPrototypeOf instead of Object.create is correct ?

function Shape() {}



function Rectangle() {

  Shape.call(this);

}



Object.setPrototypeOf(Rectangle.prototype, Shape.prototype);



var rect = new Rectangle();

If it's correct, then I am wondering why so many examples show inheritance with Object.create because you need to worry about the constructor property when using this method.

With Object.setPrototypeOf you don't need to redefine the consctrutor prop, I find it safer and simpler.

Sometimes your code may rely on the constructor property, which allows you to access the constructor without knowing its function name explicitly. But besides that, there is no real need to set it.

For example, the instanceof operator does not depend on it.

If you don't need to bother about it in your own suggested solution, then you also would not need it in the Object.create solution.

The reason to prefer the Object.create method is that Object.setPrototypeOf may impact the efficiency of your code, as is warned about in the mdn documentation. This does not happen with the Object.create method.