The video is very informative. You should include a visual evidence of the primitive data type being immutable. Same thing with object and array. I like how you make the connection to the memory instead of the value itself. It helps explain what is going on behind the hood in JavaScript. If you can show an updated video with actual example that would be grateful.
Thank you! In the description of the video, I have a link to some code that demonstrates immutability. It defines a variable of each data type (primitive, array, object) as a property of another object. It then demonstrates when the setter is called (code sees the value as changed) and when it isn't. Please see the video description for the link.
Hi Deborah, been following you since 2020, have watched all of your Angular courses on Plural sight, my request and I believe this is currently the hot topic: Next.js, pls make a series on this..
so glad i found your channel. thank you for your clear explanations. one question though: when creating a new object by using the spread operator and the original object contains an array, i would copy the reference of the array, wouldn't I? So maybe I should figure out a combination of using the spread operator to treat the object as immutable and the with() method for the array. Or am i on the total wrong track?
one question : i've read that dynamic arrays (which we use in javascript) create a new array in memory in case of adding new value which would exceed the length of the array , so does that mean that sometimes the address of the array change ?
Detailed simple explanation of why immutability is important. Thank you 👍
So nice of you to say. Thank you for watching!
The video is very informative. You should include a visual evidence of the primitive data type being immutable. Same thing with object and array. I like how you make the connection to the memory instead of the value itself. It helps explain what is going on behind the hood in JavaScript. If you can show an updated video with actual example that would be grateful.
Thank you!
In the description of the video, I have a link to some code that demonstrates immutability. It defines a variable of each data type (primitive, array, object) as a property of another object. It then demonstrates when the setter is called (code sees the value as changed) and when it isn't. Please see the video description for the link.
So important topic explained by @DeborahKurata!!!
Thank you!
Simple yet informative.
Glad it was useful!
perfect timing! i was just dealing with a bug related to this topic
Great! Glad to hear it was useful!
Great video again, now i know why immutability is important. Thank you!
Glad it was helpful! Thanks!
Hi Deborah, been following you since 2020, have watched all of your Angular courses on Plural sight, my request and I believe this is currently the hot topic: Next.js, pls make a series on this..
Thank you for the suggestion!
so glad i found your channel. thank you for your clear explanations. one question though: when creating a new object by using the spread operator and the original object contains an array, i would copy the reference of the array, wouldn't I? So maybe I should figure out a combination of using the spread operator to treat the object as immutable and the with() method for the array. Or am i on the total wrong track?
Awesome explanation
Thank you!
very informative and well descriptive tutorial video. Hope you will give us more and more informative and well descriptive tutorials .❤
Thank you! 😊
Thank you so much!! Very clear explanation❤❤
Thank you. Glad it was helpful!
you are the best Thanks a lot
Thank you for watching!
thank a lot, That's so useful
Thank you!
Thanks a million I think immutability now became a piece of cake Thanks @Deborah
Great! Thank you!
you explain really well, thank for that.
Thanks for watching!
doing god's work Kurata, thanks!
😊 Thank you for watching!
Bravo!!
Thank you!
As usual great job ❤
Thank you so much!
one question : i've read that dynamic arrays (which we use in javascript) create a new array in memory in case of adding new value which would exceed the length of the array , so does that mean that sometimes the address of the array change ?
This answer may be useful: stackoverflow.com/a/20323491