I can probably count on one hand how many truly clear and straight forward youtube coding tutorials I've watched, this is one of em, hitting subscribe!

Great video! Being an old-school C++ developer, I personally never understood why JavaScript ever needed to borrow the class syntax. One cannot really deny anymore that classes exists in JavaScript, they surely didn't. I prefer the syntax 'prototype' above 'class'. Many early C++ book editors around 1990 had a hard time explaining what a class is all about, almost apologetic for the confusing word choice. A prototype really says what it does, as it shapes how the instantiated object will look like, while a class has nothing to do with classification.

My head is still spinning, but this breakdown helped me understand how to use classes more. Thank you so much.

I've been a Javascript programmer for more than 10 years, but suddenly, you opened my mind to a whole new sight to OOP in Javascript !!

I never dreamed I can understand these class things, but after this tutorial, those abstract things go straight into my head without any resistance. legend teacher, as always thank you.

Steve, you are the ONLY ONE I found online, that explained well enough so I could understand, I always tried to find a relationship (a kind of "translation") between functions and classes and you simply explained it. Perfect video. Thank you very much.

"It is important to understand that the class syntax is being interpreted as using the prototype syntax and that CLASSES do NOT exist in JavaScript." Great 👍

No bs, straight to the point, clear explanations with clear examples. So underrated!

This is exacly what I'm looking for! Now it makes more sense why the syntax in class is constructed in a bit of a weird way. Many thanks!

this channel is pure gold.

I think in 11:16, the line should be Object.setPrototypeOf(EmployeeP.prototype, PersonP.prototype) instead. Great video! I love it!

Omg! I finally understood prototypes - I have watched three different tutorials and I still did not get that...until I came across this video! Thank you so much!

Yooooo...been searching for a clear instructional video on this topic, finally found it. Thanks a lot.

great way to explain, clear and in a not too fast speed, so the brain can follow. thank you for the great tutorial.

After 10 videos on constructors, classes, and prototypes in javascript, finally a video that makes me really understand....thank you.

such a good tutorial, you don't skip anything and actually understanding what's a class doing and how to simulate it using prototype explains the logic behind it.

So happy I found your channel, I could cry! You’re making every subject I was shaky on just make sense!

What a clear and insightful video on what can be a very complicated concept! I've saved your 'JavaScript from the start' playlist and will be working my way through, one per day. Thanks Steve for the great education!

This is so useful I cannot explain how much it made my learning prototype easy

You are a true engineer, thanks man

I can't stress how clear this was. Thanks

Thank you so much. I am not good at english but your explanation is amazing. I can understand whole things. Thank you.

you are the best! you have nice voice and speech and so good at explaining, thank you

I have never seen a explanation like this really u r a great teacher sir applauds 🙏

one of the best if not the best javascript channels in youtube

A lot of libraries use the manual prototype method and there are some neat tricks you can do with it. I first saw this when analysing mongoose code. There are some challenges if you want to represent this with types in a typescript project, I found using class syntax to be less pain in that regard.

The beeeeeeeeeeest explanation ever. Thank you so much mate.

Thank you for creating this. Very good!

Thank you so much, you have helped me sort out the details that were getting mixed up in my head.

You truly deserve a Subscribe. Thank you for breaking down the complexities of a very confusing language!

Very concise explanation. Better than code bootcamp. Subscribed

Prime level content!! You are really good at JS❤🎉

After making a connection between the EmployeeP object and the prototype of the PersonP using Object.setPrototypeOf() method, a new prototype method(function) is added on the the EmployeeP object (in the line number 51) with the name of employeeInfo. So, my question is that whether this new method (employeeInfo) will be added to the prototype of PersonP or another prototype object of the EmployeeP? BTW your way of imparting the information (idea) is unmatchable, it's GOLD STANDARD. I will try to teach my students your way.

my god finally i understand the difference, Thank you man you saved me.

Fantastic explanation. I can always count on this channel to clear things up. Thanks man.

Thank you! Steve, It's a great tutorial, and your explanation is really great. :-)

Great tutorial with super clear explanations! Thanks a lot!!

Just discovered your channel, man .. if only you've been around 20 years earlier, I would be a JS master by now :) The thing that confused me for many years is what "this" means depending on the different contexts. I was a AS3 developer for many years, so i was used to the class logic, never understood the "prototype" concept because of that. When "class" was introduced in ES i finally could work the way i was used to. But thats why i've never understood "this". Now, i even think the prototype way of doing things is more logical. And understanding it clears up a ton of other things in JS that puzzled me.

Awesome. You made it clear for me, thank you.

As an advanced novice JS coder, I always found 'prototypes' confusing ... Your video makes the case for the class paradigm vice prototype model in my view ... Coming from the Java and Python world, classes and subclasses are the way to go and are more OOP than 'prototypes' ...

Gold! Incredible! Thank you!

Excellent tutorial, thank you.

Another very cool tutorial!

Thanks for such clear, and concise concepts! Keep up the good work :)

Thank you man, you are very talented to explain those concepts... God bless you!

Yea one of the nice things about class is its inheritance of scope. Thanks

I was struggling with 2 things, what a class really is (in JS) & what practical purpose it serves for the work I do. You have answered that perfectly .. knowing that the class syntax is just syntactic sugar for functions makes my brain happy! Subscribed.

Nice content, nice explanation, I'm a newbie & I could derive a lot of sense out of this. Helpful & v.much to the point. Clean clear crisp. And your voice is so cool :p Cheers keep this great work going.

Great explanation on JS classes. Thanks Steve.

JavaScript Classes and Protototypes beautifully explained. Thanks, Steve {2023-08-18}

Thanks a lot! It's much clear now the concept to me

@steve griffith : Hello Steve. This is really Awesome. By far the best Explanation ever. All your Videos are Awesome. Keep Rocking. A Small Clarification, I feel it has to be Object.setPrototypeOf(EmployeeP.prototype, PersonP.prototype). [ You have written EmployeeP. This causes an error and I'm not able to call getDetails Function from the Base Class. ] Please do correct me if I'm wrong. Thanks

wuauu !!! You made it very easy . A lot of thanks, Blessings

This is such a good explanation, thanks mate.

Another clear explanation - thank you!

At 11:13, if you set the prototype of EmployeeP to PersonP.prototype, the EmployeeP.__proto__ becomes the PersonP.prototype, and the EmployeeP.prototype stays the same it was, that's what happens for me at least. Because of that the methods inside PersonP.prototype cannot be called through the objects created by EmployeeP. I don't know if I did something wrong, but to fix that I simply wrote Object.setPrototypeOf(EmployeeP.prototype, PersonP.prototype), so now the prototype object of EmployeeP function is a child of the prototype object of PersonP function, I think that's how the prototype chain for classes is too.

Thanks it made it clear to me that even if it ends up being the same thing, classes makes it more clear that they are tied together. I do wonder if one way performs better than the other tho but its probably not that important.

Really good explanation

Hi Steve, I am just starting my career in coding and have to say you are like a god of coding for me. I read blogs, excerpts from books, and what not but the way you explain things is just amazing. I am preparing for the MCSA-70-480 exam as a part of my apprenticeship and these tutorials are so helpful for a beginner like me. Just wanted to know if by any chance do you take personal coding classes or any sort of official coding lessons if somebody is interested in learning from you 1-1? My learning at this point in time is exam based and there are so many things that I come across in practice questions that I just can't understand and hence feel the need for proper mentoring for expedited learning.

Clear and useful tutorial

thank you it' s a really good one

Its actually Prototype, classes don’t exist in JS. Also, this is “this”. And its also an Object

Grenat tutorial , thanks you

It should be: Object.setPrototypeOf(EmployeeP.prototype, PersonP.protoype) With code shown in video, you're effectively attaching the employeeInfo() method to PersonP prototype, meaning even PersonP instances would have that method after that point.

Great video very helpful!

Nice explanation 👍

VERY NICE..... Easy to understand.

Spiegazione eccellente, complimenti!

thanks for this video man. It really helped a lot.

Thank you professor.

Thank you so much, you explained it really well.

thanks Steve very helpful.

Very well explained. I will be hitting subscribe.

best explanation

Great Steve. Cristal clear and you make it easy. But, what happens if you create a variable without new (i.e: let Jose = PersonP)?

This is fantastic. Are there any advantages of one over the other? Maybe private #variables in classes, for example?

thank you very much ,you are great

Thank you so much for the very concise information. Sometimes I see projects on Github mixing these techniques (Especially Node.js projects). Why is that? Is there some advantage to mixing these or using one or the other?

At line 47 PersonP.call(this, nm, id) is there any other way to write it using the setPrototypeOf or Object create method? Thank you very much for your tutorial. Amazing as always!

How many times have I watched this video over the last few months? Lost count...

Excellent tutorial as usual. I was wondering though, why not add getDetails to PersonP like you did with the properties? I.e. this.getDetails = function() { // code block }. This makes the prototype way look more like the class way. I assume they are just different ways of doing the same thing, is that right?

Loved it, pal.

very clear, thank's

Why do you need line 50? Where you set prototype? It seems that you can have inheritance just with the PersonP.call line. I imagine I'm missing some inheritance functionality that would be missing but I can't think of it.

very helpful thanks a lot

hi just wanted to know doesn't it breaks linkage with Function.prototype with EmployeeP ? I guess instead "Object.setPrototypeOf(EmployeeP, PersonP.prototype)" we should use "Object.setPrototypeOf(EmployeeP.prototype, PersonP.prototype)"

Hi Steve, thanks for this video. I came back to this again after refactoring some code into factory functions and away from classes. My question is: with what you've shown here, will we still encounter the various pitfalls with 'this'? (ie. having to bind explicitly when invoked from another function -- my intuition says yes because this illustrates an alternate syntax for the same end result). To that end, would you recommend a more functional / composition based approach where factory functions return objects with certain properties and then object types are returned by composing those functions? Cheers!

why arent we able to call - console.log(mary.getDetails()) if the getDetails function was passed to function EmployeeP ?

is there any difference in which one to use? Perhaps one is faster or something like that? Or are they equal ?

great video man. Thanks

is this new? Back in my day, I don't recall JavaScript having classes, much less the ability to extend a class. This is all very Java like.

Great explanation!!!

Awesome video! I have a question regarding the number of functions that can be extended. For instance, EmployeeP extends PersoneP1 and PersoneP2.

Why are methods of a class Person store in Person.prototype and after that we call these methods not passing by prototype ?

Great explanation. Thanks :)

I'm still confused between prototype and the hidden property [[Prototype]] that os called by the accessor function __proto__ ?

Thanks, it is very helpfull)

From what I'm reading, the use of Object.setPrototypeOf() is highly discouraged due to massive performance issues. I also miss how this relates to __proto__ in this very example. Last thing I noticed is that doing SuperClass.call(this, params) is called constructor theft in Nicholas Zakas' excellent book "Principles of object-oriented Javascript", and I wonder if there's any alternatives to that.

Thank u so much bro, actually i have a small question which is :: which one should i use, classes or objects, and why ?

Why we don't invoke PersonP function inside PersonP right away instead of using PersonP.call()?