I liked scriptaculous.

I have thought about sponsorships (as KZfaq calls them). But I need 30k subscribers before I can do that.

Maps, Sets, and Arrays all have their own constructor with their own prototype object. Then they are all connected to the Object prototype. Whether you use `class` or `object.create` or `new` you are doing the same thing with a constructor and it's prototype. You might also be interested in my other videos about the prototype chain and classes - kzfaq.info/get/bejne/jtWBfrt1vMiwYYE.html kzfaq.info/get/bejne/Zpeaicp0sJOsiGg.html

When you create an Object, that object will automatically have a prototype object. The prototypes are what gets linked to create the prototype chain. If you want methods to be available to the objects that are below then you typically place them on the prototype. The prototypes then get connected to form the prototype chain. You can alternatively create an object to specifically be the prototype of your object. In this case you would put the methods inside the object and then set the object as the prototype for your other object.

and thank you very much too!

prototypes are a core part of JS that goes back to version 1 and they will always be part of JS. They are incredibly relevant regardless of which version features you are looking at.

@@SteveGriffith-Prof3ssorSt3v3 Thank you

You can always use the Object.getPrototypeOf( obj ) method to get the prototype of an object. You can write that in the console.log. Here is a sample that creates an object with its own custom prototype object. It's prototype object then links to the Object prototype and then it links to null. let myObjProto = { f: function() { return 42; } }; let myObj = Object.create(myObjProto, { prop: { value: "value" } }); let protoT = Object.getPrototypeOf(myObj); console.log("prototype is", protoT); while (protoT !== null) { protoT = Object.getPrototypeOf(protoT); console.log("prototype is", protoT); }

Object is the built in top of the chain. Its prototype points to null. You can't change it. But you can build as many custom objects as you like and extend them. It all leads back to Object.prototype and /or null. You can point your object prototypes to null if you want.

This is the error that you get if you try to overwrite the Object prototype: TypeError: Cannot assign to read only property 'prototype' of function 'function Object() { [native code] }'

Here is a good reference to read about __proto__ developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/proto Along with the recommendations to avoid changing the prototype of an Object for performance reasons. Using Object.create( protoObj ) when you create an Object is fine. Try to avoid changing prototypes after the fact and especially with built-in objects. This link too - developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/prototype

Please post requests for tutorials on my tutorial request video - kzfaq.info/get/bejne/gqmVrcSpl9uyY5c.html

I'm starting to work on some courses that I will be posting here on KZfaq.