> It’s this idea that if you can’t consume the raw, hardcore documentation then you’re not worth it of using that technology.
I tend to avoid w3schools but this isn't at all the reason why. I don't believe that what w3schools provides is a made-easy resource for a hard concept. Actually I would say that's exactly what MDN is.
For the most part, I find that w3schools usually only provides a basic enumeration of the possible property values for an attribute or something like that with absolutely no additional insight whatsoever. I don't really believe that is helpful for beginners even in a pragmatic sense. Yet, somehow they continually peg the top of any HTML-related Google search.
MDN on the other hand almost surely details the most important caveats and practical aspects about whatever it is you're looking up. That I think is some of the most important information for beginners. It does not provide the same kind of "raw hardcore" documentation you'd get from reading the spec for example.
I tend to avoid w3schools but this isn't at all the reason why. I don't believe that what w3schools provides is a made-easy resource for a hard concept. Actually I would say that's exactly what MDN is.
For the most part, I find that w3schools usually only provides a basic enumeration of the possible property values for an attribute or something like that with absolutely no additional insight whatsoever. I don't really believe that is helpful for beginners even in a pragmatic sense. Yet, somehow they continually peg the top of any HTML-related Google search.
MDN on the other hand almost surely details the most important caveats and practical aspects about whatever it is you're looking up. That I think is some of the most important information for beginners. It does not provide the same kind of "raw hardcore" documentation you'd get from reading the spec for example.