There will always be non-technical users. The trick is to focus their frustration on the parties they should be frustrated with. Take for instance those screens browsers present when you try to visit a website with dodgy security. These are universally awful user experiences and users likely have no idea what the hell is going on, but browsers do it anyway for the users&#x27; benefit and for the long-term health of the web. When users encounter these warnings, they don&#x27;t think &quot;Oh jeez, Firefox sucks so much&quot; they think &quot;I better get the hell out of here and not visit this web site anymore&quot;.<p>I&#x27;d argue that more strict adherence to standards and rejection of old, deprecated code is better for users because it&#x27;s better for the long-term health of the web as a platform. The effort spent maintaining a mess of unnecessary backwards-compatibility (particularly with things meant to be temporary from the start) is effort that would be better spent providing actual value for users in the form of quality improvements, better performance, and features.