The article disregard that most of the time JavaScript is introduced into the fray because the product needs some level of interactivity that cannot achieved wi

The article disregard that most of the time JavaScript is introduced into the fray because the product needs some level of interactivity that cannot achieved without it. JavaScript right now is the only way a program can run in a page on the browser side. The article also conflates problems caused by 1.) JavaScript being a hard dependency of an application, a misarchitecture, and 2.) low JavaScript code that is common in the wild Those are different problems with different solutions. Both can be solved without removing JavaScript. There are technology which can help reduce the importance of JavaScript in the client side. GatsbyJS is one of them. It allows generating static site and dynamic frontend app depending on what you need. Although GatsbyJS has its own problem that sometimes shoot you in the foot. What we need is to raise awareness to service and product providers that browsing without JS is a thing! That way the whole industry can move in a more efficient manner. Rather than a struggle between engineering and product team, it will be the provider's struggle to provide for paying customers. Meanwhile low JavaScript code quality in the wild - I don't really have a solid idea for it. I can be sure that wisdom can be gotten from the days of old where resource are scarce and things have to be super smart in order to work. There are hidden engineering gems and wisdom over there, but I don't know how to propagate it quick enough to match the growing number of devs. Meanwhile devs will keep coming because of the high demand and nowadays low barrier of entry. What we can do is to encourage the culture of rigor, thriftiness, and constant learning to keep code quality high.