Thank you for this! I've spent all day trying to find a video that satisfactorily explained linked lists in JavaScript and this is the first time it actually made sense. Keep it up!
One of the clearest Linked Lists explanations I've seen. Thank you! I've had a hard time wrapping my brain around this, but your clear explanations, visuals alongside the code, and repetition, really helped me! Thank you!
Couple of things you may want to clarify. When you start coding out the linkedlist constructor, you should specify you're making a doubly Linked list. Also it helps so much to have visuals (the visuals on the right don't quite explain how the pointers are working/moving from node to node, etc.)
Thanks. I fail to understand under what situation we need to bind a function in constructor. The way we used to do react class methods (which is no longer required with Arrow function now)
Nice Video. I am careful( actually never) using classes. But I similarly use objects. I just add methods to a js object, and it is pretty close to a class. Is this bad practice?
It's not bad practice. Classes are more of 'syntactic sugar' in Javascript. It's a nice-to-have because it allows you to write code that feels more Object-Oriented. But definitely not necessary
![[DOKKAN BATTLE] Worldwide Campaign Announcement Video Part 2!](http://i.ytimg.com/vi/JpT5Voak6WA/mqdefault.jpg)
The best Linked Llist explanation on the internet.
Thank you Paschalyn!
Thank you for this! I've spent all day trying to find a video that satisfactorily explained linked lists in JavaScript and this is the first time it actually made sense. Keep it up!
One of the clearest Linked Lists explanations I've seen. Thank you! I've had a hard time wrapping my brain around this, but your clear explanations, visuals alongside the code, and repetition, really helped me! Thank you!
Glad you were able to find value
Couple of things you may want to clarify. When you start coding out the linkedlist constructor, you should specify you're making a doubly Linked list. Also it helps so much to have visuals (the visuals on the right don't quite explain how the pointers are working/moving from node to node, etc.)
So the "this.previous" node pointer in the beginning wasn't a big enough clue that I was building a doubly linked list?
My favorite black dev for sure
Great video!
Good job with the structure and all the analogies and editing to aid the explanation. Great Pace aswell!
Keep it up! 💪
Much appreciated!
How does the oldTail have any reference to the this.head, i don't see how that is suppose to update the head, please can someone explain this to me
I love this video
How does the context (this) get autobound to the methods even if we are not using fat arrow functions?
A class method in javascript will automatically be bound to the context of the class.
Thanks.
I fail to understand under what situation we need to bind a function in constructor.
The way we used to do react class methods (which is no longer required with Arrow function now)
Nice Video.
I am careful( actually never) using classes. But I similarly use objects. I just add methods to a js object, and it is pretty close to a class. Is this bad practice?
It's not bad practice. Classes are more of 'syntactic sugar' in Javascript. It's a nice-to-have because it allows you to write code that feels more Object-Oriented. But definitely not necessary
@@DevSage thanks. Maybe I try the sugar to sweeten it up :)
Awesome bro
Useful Content. Video Resolution Quality is less
video quality is very poor