Comment by diggan

I think it depends. I basically see the web as two parts, "web documents" (usually called "websites") and "web apps" (usually just called apps), and it makes sense that web apps that require lots of interactivity (think drag and drop) would use lots of JavaScript, I don't people have a problem with image editors or map viewers being made more simple by the use of JS for example.

The friction occurs when people building a website for web documents think they should be building a web app, so you end up with a scaffolding that requires heavy JS just to serve what essentially is just text + maybe one or two images. The additional JS doesn't really save the user any time or pain, it just makes everything larger and harder to consume.