3 ms·
My impression is that people are not primarily arguing that W3Schools is great, but rather that however shitty it might be, it fills a void that MDN doesn't. I
by mercer 8y ago
My impression is that people are not primarily arguing that W3Schools is great, but rather that however shitty it might be, it fills a void that MDN doesn't.
I'm pretty serious about web development, and yet I constantly find myself mildly frustrated with whatever MDN resource I find when I'm looking for a solution to my problem.
If I had to guess why I get frustrated, it's probably because MDN seems to focus on being a comprehensive reference at the expense of offering examples and solutions to those who don't immediately care about the nitty gritty.
I think fetch() is a perfect example of this. Back when I googled how to use it, I ended up on MDN and it wasn't too helpful. I had to scroll down and click on another link to get an example, and while that example was for JSON, it immediately made it clear where I should look if I'm dealing with some other kind of response.
Not that W3Schools is better. It sends me here: https://www.w3schools.com/js/js_ajax_examples.asp https://www.w3schools.com/js/js_ajax_examples.asp
But what I'm really missing here is a php.net style website that gives me some concrete examples that solve the most common use-cases, and either offers more in-depth material if I want to properly understand it, or references MDN. I totally understand how for many situations W3Schools is that resource.