> "Not necessarily, and bad code can make dangerous tutorials."

W3Schools is not responsible for what devs do, and safe code means introducing more concepts that can leave the scope of a tutorial.

I agree the code sucks, but we're talking about minimizing time to understand something, not security. Save that for the security tutorials.

This is more like your primary school art teacher letting you stick the brush through your eardrum without saying anything.

The problem is nuance, which involves all those little wow-I-wish-I-knew-THAT tidbits that students never learn about until a forum member or colleague hollers at them.

Languages cannot eliminate every subtlety in their use, and there will always be issues that call for more articles explaining how to sidestep them. Novices won't normally get to see this content, and it won't help them to shove it all down their throats at once back at the introductory level courses.

There's a reason most physics students hear about Newton first.