From the article: > the reason why JavaScript development is so complicated: > web development itself is inherently complicated. It's really sad to me tha

From the article: > the reason why JavaScript development is so complicated: > web development itself is inherently complicated. It's really sad to me that the writer cites necessity as the reason for complexity. > We are trying to build applications that run right in a dozen browsers I remember cross-browser CSS and JavaScript from 2005 as infinitessimally shorter, and that was when we had to contend with IE 6. All of the other browsers back then behaved fairly uniformly. Now, IE 11 is almost indistinguishable from the rest. > look good on thousands of different devices There are really just two devices: big screen, little screen. To think you're targeting "thousands of different devices," you must be counting every make and model as a "different device" (and even then, it's more like dozens). Tell me, how does targeting the Samsung Galaxy S3 and the iPhone 6 require a bunch of JavaScript dependencies? > load fast enough for impatient commuters in the subway This is an art we have lost. The web used to ride on 28.8 kbps. > and are still accessible enough that blind people can use them. That also has been a solved problem for well over a decade. > The Cambrian explosion of tools you see around you > is what rapid progress looks like when it’s not > controlled by an Apple or a Microsoft. The web was never controlled by Apple. At one time it was dominated by Microsoft, but even then I could write cross-browser JavaScript without really thinking about it, with jQuery (2006). > At the same time, web developers are closing security > vulnerabilities all over the place. What other security hole is there for web devs to handle besides cross-site scripting, and how does any security hardening lead to magnitudinous JavaScript dependencies? > If this evolutionary process frustrates you [...] Is this evolution or entropy?