Agreed. MDN is for the web what MSDN is for Windows programming - long, detailed, sometimes confusing, sometimes contradictory, and the number one resource you can find online. My three top resources for web documentation are: RFCs, MDN, and StackOverflow. I'm not even sure where I would find a list of all properties that a given DOM element support and what browser version support was added if not on MDN.

I do. I feel like Mozilla is the only organization that I can trust to provide neutral, unbiased documentation about all the standardized web APIs out there.

Plus with GitHub single sign-on it's actually very easy to contribute to or edit an article (assuming most web developers have a GitHub account). I was surprised when I found that out.

MDN is so confusing when it comes to their documentation. Some pages are better than others, but some are even contradictory in what they say. Then there is the PHP documentation which is both amazing and horrible. Each page starts off with official documentation which is even worse than MDN, but then they created a community documentation on each page (for that method/function/class whatever) below the official ones which are voted up and down by randoms and actually works out to be some of the best documentation on the web. Maybe we should all just jump to community maintained documentation. If i ever am pushed to a PHP doc page, I scroll past the official documentation and read the top rated community post which almost always gives me what I need instantly.

Stackoverflow is my preferred source of course.

I personally hate MDN. I actually prefer W3Schools. I want straight to the point examples.

I'm quite the opposite. I often use MDN when I need detailed explanation of JS or DOM features. I think it's a nice resource. If I need straight examples I go to StackOverflow. W3S isn't on my list any more.

W3Schools often has incomplete or outdated information.

I don't think that's true anymore. Do you have any examples?