This playlist is a gem. Detailed, well organised and great explanations. Plus the Github repo where all the code is amazing as well. Thank you Nader for putting this all together. One questions regarding the exercise #3. I understood that when we modify the stock array, it gets updated for all because array and objects are references. However, for the name property which we also update, does not get updated for all. Instead all the new objects created now has there own name. Is this different behaviour between 'name' and 'stock' because name is primitive type(string/by-value) and stock is array(non primitive/by-reference type)?
amaizing, you really made it incredibly digestible to understand this topic. kudos for te order of the topics aswell shows how well tought the course is
weird I get a typeError in the bonus exercise... function Person(name) {this.name=name}; const cleo = Person("Cleo"); TypeError: Cannot set properties of undefined(setting 'name')
HAHAHAHAHA If using boop as the function name makes laugh uncontrollably, why don't you let the cat and boop go? It cracks me up every time you say boop you can't help but laugh, but then you're trying your best to stay serious about the knowledge point.
best teacher ever 👏👏👏👏👏👏
Discovering this channel is like discovering gold
"arrays are basically just glorified objects" ,
oh and by the way nader, your explanation is really clear, love that
This playlist is a gem. Detailed, well organised and great explanations. Plus the Github repo where all the code is amazing as well. Thank you Nader for putting this all together.
One questions regarding the exercise #3.
I understood that when we modify the stock array, it gets updated for all because array and objects are references.
However, for the name property which we also update, does not get updated for all. Instead all the new objects created now has there own name.
Is this different behaviour between 'name' and 'stock' because name is primitive type(string/by-value) and stock is array(non primitive/by-reference type)?
Yup, that's exactly right! The String itself is a value type not a reference type (in js) so it's a new separate value each time or change :)
100% extremely clear, love this
amaizing, you really made it incredibly digestible to understand this topic. kudos for te order of the topics aswell shows how well tought the course is
Clear as crystal
Nader, so good! Thanks once again...
congrats ! man for 1k subscriber brother , hope you will get 1 million one day 💌
Thanks! I’m really glad these videos are able to help more people get started and really learn these topics. 😊
@@TechWithNader brother do you have any plan to make a react js course after the Javascript course?
@@madfoodhunter Absolutely! Going to move to the DOM first so we understand the fundamentals then do React 😊
love this video
Thanks! It was was making these - glad you’re finding them useful 😊
weird I get a typeError in the bonus exercise...
function Person(name) {this.name=name};
const cleo = Person("Cleo");
TypeError: Cannot set properties of undefined(setting 'name')
weird asf
HAHAHAHAHA If using boop as the function name makes laugh uncontrollably, why don't you let the cat and boop go? It cracks me up every time you say boop you can't help but laugh, but then you're trying your best to stay serious about the knowledge point.
😂😂😂