Alas, I have seen the same kind of logic at work in the world of web design. There are designers who not only donβt know how to write markup and CSS, they actively refuse to learn.
Again, they cite the fear of somehow being constrained by this knowledge (and again, I believe thatβs a self-justifying excuse). In the world of front-end development, that attitude is fortunately far less prevalent. Most web devs understand that thereβs always more to learn.
But even amongst develβ opers who have an encyclopediac knowledge of HTML and CSS, there is often a knowlβ edge gap when it comes to the Document Object Model. Thatβs understandable. You donβt need to understand the inner workings of the DOM if youβre using a library like jQuery.
The whole point of JavaScript libraries is to abstract away the browserβs internal API and provide a different, better API instead. Nonetheless, I think that many front-end devs have a feeling that they should know whatβs going on under the hood.
Thatβs the natural reaction of a good geek when preβ sented with a system theyβre expected to work with. Now, thanks to DOM Enlightenβ ment, they can scratch that natural itch.
Douglas Crockford gave us a map to understand the inner workings of the JavaScript language in his book JavaScript:
The Good Parts. Now Cody Lindley has given us the corresponding map for the Document Object Model.
Armed with this map, youβll gain the knowledge required to navigate the passageways and tunnels of the DOM.
Β
Π‘ΠΊΠ°ΡΠ°ΡΡ ΠΊΠ½ΠΈΠ³Ρ ΠΌΠΎΠΆΠ½ΠΎ Π±Π΅ΡΠΏΠ»Π°ΡΠ½ΠΎ ΠΏΠΎ Π΄Π°Π½Π½ΠΎΠΉ ΡΡΡΠ»ΠΊΠ΅: Π‘ΠΊΠ°ΡΠ°ΡΡ


























0 Comments