I don&#x27;t believe that.<p>I understand that some of the issue is lazy developers, but I really think that the majority of the problems would be caused by unmaintained code.<p>Websites frequently sit around un-touched for years, hell our company website has some js code that was written by me over 4 years ago and hasn&#x27;t been touched since because there&#x27;s just no need to screw with it. And i&#x27;ll be honest, it&#x27;s not going to get updated until something breaks, and I would consider myself someone who likes to  be on the cutting edge and is willing to endure breaking changes in more things than i should.<p>I really think that by advocating for a &quot;good&quot; subset of the language, we can get all of the benefits of removing old stuff with very little of the downsides. Something like &quot;use strict&quot;; in javascript now. It removed many terrible things from the language in a way that you could mix old and new code together and get the benefits of both.<p>That worked great, and i really think it could work great again. Something like a &quot;use es6&quot; or something that removes a massive set of &quot;bad ideas&quot; in the language, but it does it in a per-file or per-function basis. Allowing new code to be written in a better way, and allows old code to keep going as it was for a very long time.