davidbruant
Anyway, it sounds like a lot of work to reduce to literally zero the number of exploitable defects. Some advocate that a lazier approach based on POLA and object capabilities could work too. https://www.youtube.com/watch?feature=player_detailpage&v=eL... (I timestamped for the relevant part, but the full talk is good to watch too).
Building on an object capability language, even if some exploitable bugs remain along the edges, allow a high-level of security. Not sure how Rust stands, but it looks promising for sure.
"...whereas w3schools has had to deal with the changing standards of html4/xhtml/html5." => These differences are 99.99% additions, so don't impact documentation that much. In any case, documentations is more relevant is it documents implementations, not standards (which come after implementation most of the time, not the other way around until recently)
"To MDN maintainers: Please read some "The Elements of Style" by Strunk & White and some "Don't make me think" by Steve Krug, and improve MDN. You guys could have done better."
Over the years, I have noticed that lots of people have good ideas about MDN, but no one seems to care sharing them in a Mozilla channel or better, contribute to MDN! It's a wiki! Something is wrong or inappropriate? Go fix it! (appropriate channel: https://lists.mozilla.org/listinfo/dev-mdc )
It's also been over a year now that Mozilla is building the wiki behing MDN. It's an open source project called Kuma https://github.com/mozilla/kuma/ Check it out and contribute. I have not read the 2 books you're refering to. If you have, go share your ideas!