Комментарии:
THANK YOU BRO, thank you.
ОтветитьBro ain’t no way I was the only one who came here thinking he was going to explain “The Depth Of Market” for traders 😂😅
ОтветитьJust came across your channel now, thanks for the straight forward yet informative explanations. 💯
ОтветитьThanks for your short but useful video
Ответитьplease remove background music
ОтветитьOK, so what's the sub?
Ответитьfinally, someone explained the DOM in a way that answered my questions. thank you, bro.
ОтветитьYou've just misled a lot of people ... the DOM is NOT a "Javascript object"; it is a data tree structure. Here's the definition by Codecademy : "The DOM is represented as a type of data structure called a tree. Every object in the DOM is hierarchically under another object, and any object can have multiple children but only one parent. Each DOM object “owns” its children. If you remove an object from the DOM, all of its children will also be removed with it." Javascript creates an object within itself that represents the contents of the DOM tree structure at any given moment.
ОтветитьMy mind is blown after the clarity this video gave me. This might be one of the best things to happen to me in my JS journey.
Ответитьincredible! super clear, thanks for making this video mate.
Ответитьnow i am clear thank you dear
ОтветитьTook me 1 year to try to understand this but thanks to your video it makes soooooooooooo much sense!! Thank you Aaron.
ОтветитьI was doing the Zero to Mastery "Complete Web Developer" course and when Andrei got to the DOM part, I felt completely lost. It felt like he just jumped into using another foreign language without a good explanation. This video helped put things into perspective. Thank you.
ОтветитьGreat explantaion . new subscriber
Ответитьthank you so much, very helpful video
ОтветитьPrera
Ответитьgreat great great video....
Ответитьthat was easy, clear and awesome!!
Ответитьidk why you blewm my mind when you said a style is a subobject with color property. it all makes sense.
ОтветитьKudos for the Alan Partridge visual.
ОтветитьReally good explain not gonna lie
Ответитьthank you mate ! :)
ОтветитьSimple clear explanation.
Thanks..
Great explanation
ОтветитьNice and simple : )
ОтветитьIf you guys want to use the DOM objects now, you can try by writing document.querySelector(".ytp-chrome-bottom").style.display='None' on the console now and see what happens.
ОтветитьWorst explanation...ever.
ОтветитьThank you so much for making this video!
Ответить👍
ОтветитьYou deserve a million likes for this explanation
ОтветитьGreat content. Thanks!
ОтветитьMan this is the best explaination. Watched multiple videos about basic DOMs and they are just trash and complicated. You're a hero dude. Thank you!
ОтветитьAmazing, but the speed was to fast for me. Decreasing the play back speed was also not fun at all -> Overall USEFUL
ОтветитьI have hit like just for the perfection of your teeth
ОтветитьCool. Now explain the Sub in this dynamic.
ОтветитьWow. Great video. Concise and Lean. No fat, no padding. Well done.
ОтветитьThis was one of the easiest to understand explanations. My professor explained it so complicated.
ОтветитьThank you for your wonderful explanation style.
ОтветитьYO I AM IN SCHOOL FOR THIS AND THIS WAS EASILY EXPLAINED IN A FEW MINUTES. THANK YOU!!
ОтветитьTo understand the difference between HTML and the DOM, imagine this real-life analogy:
---
### *Scenario: A Recipe and a Cooked Dish*
1. **HTML as the Recipe**:
- The *HTML* is like a **recipe book**.
- It contains a *static list of instructions* and the ingredients needed to prepare a dish.
- You cannot eat the recipe, but it serves as the blueprint.
**Example**:
- Recipe: "Make spaghetti with tomato sauce."
2. **DOM as the Cooked Dish**:
- The *DOM* is like the *actual dish* you create by following the recipe.
- Once the browser (the cook) processes the recipe (HTML), it creates the cooked dish (DOM).
- Unlike the recipe, the dish can be **modified or customized in real-time**. For instance, you might add more salt, remove some vegetables, or serve it on a different plate.
**Example**:
- Adding more cheese to the spaghetti after it’s served (just like modifying content dynamically via the DOM).
---
### *How the Recipe (HTML) and Dish (DOM) Interact*
1. **HTML is Static**:
- The recipe stays the same once it’s written. You cannot alter the recipe itself.
- Similarly, HTML is static content—it defines the structure but doesn’t change on its own.
2. **DOM is Dynamic**:
- The dish (DOM) can be altered based on needs or preferences, just like you can tweak the dish after it's cooked.
- For example:
- You can add or remove ingredients (elements in the DOM).
- You can change the serving style (modify CSS dynamically).
- You can serve additional portions (add new elements).
---
### *Real-Life DOM Example*
Let’s say you’re visiting a restaurant (the website):
1. **HTML Recipe**: The menu shows "Spaghetti with Tomato Sauce."
2. **DOM Dish**: When the dish is served, you (the user) decide:
- Add more cheese: `document.querySelector('spaghetti').addCheese();`
- Remove mushrooms: `document.querySelector('mushrooms').remove();`
- Replace tomato sauce with Alfredo sauce: `document.querySelector('sauce').setType('Alfredo');`
The server doesn’t change the menu (HTML), but the dish (DOM) can be adjusted as per your needs, giving you a customized experience.
---
### *Key Takeaways*
- **HTML**: Recipe = Blueprint (static and unchanging).
- **DOM**: Dish = Live, customizable version of the recipe.
- **Browser (Chef)**: Transforms the recipe into the dish and allows real-time changes based on user inputs.
Awesome. Like ususal.
Ответитьwithout the JS, you might as well print out your HTML with printer 😂😂😂
Thank you so much. This came out so clear and understandable
Bro you are a GOD. also cover api aspect
ОтветитьThank you for this.
I am grateful man.
Thank you
ОтветитьI'm don't know if I'm dumb af, but this is the first time that I fully understand what DOM is. Thanks bro! (but pls use less music)
ОтветитьThanks alot bro
Ответить