All you may need is HTML
Some years ago I was interviewing for head of automation position, and in the process was asked how&#x27;d I go about making sure a Web admin interface (to a product that by and large doesn&#x27;t need a Web interface, think, in the same category as Kubernetes) is well-tested.<p>To which I responded that I&#x27;d not use any JavaScript.  Ideally, XML with stylesheets.  Very light-weight, renders extremely fast, and is extremely friendly to automation tools (doesn&#x27;t even require a browser for most tests).  For the kind of product this was intended for, and I still believe it to this day, it would&#x27;ve been perfect: nobody needs any CSS animations there or any kind of interaction beyond filling forms and submitting them.<p>One of the interviewers was the head of the front-end department.  He hadn&#x27;t for a moment considered this to not be a joke, but pretended to answer this seriously by explaining that if they don&#x27;t put a fashionable JavaScript framework into job description, they will not be able to hire front-end programmers.<p>In reality, there are plenty of things on the Web that could, in principle, be just HTML or, as in my example, XML + stylesheet, but won&#x27;t be for no reason other than to feed the echochamber of the job market.  Nevermind that from the business side this makes user experience worse, costs more to host and to maintain, and yet...