What does "slowing down a bit" even mean? Sorry, but this just reads like total fluff to me. Where exactly should we slow down? There's no clear problem stateme

What does "slowing down a bit" even mean? Sorry, but this just reads like total fluff to me. Where exactly should we slow down? There's no clear problem statement nor proposed solution. Web development has been improving drastically over the last few years, which is amazing. But you don't have to use any of these newer technologies! Even if it's evolving rapidly, it's also pretty strict when maintaining backwards compatibility. Another problem I have with this article is that it puts websites and web apps in the same bag. You cannot do web apps without JS. There are tons of applications that are impossible without JS! Progressive enhancement is not feasible for applications. When I have document-focused content, I make sure it works with JS disabled, but I don't think anyone should bother with that when they're building a web app. There's a lot of tools that are really targeting applications, but they get jammed into regular websites. What I do think we should do is improve our documentation and improve our communication skills. I don't think this is limited to the web, but I'd love it if people were more up-front about what problems their framework or library is meant to solve. Talk about the tradeoffs that you made when building that framework / library, and explain why you made those design decisions. This is all important in figuring out what tools to use. And talk about its shortcomings as well! Tell me what parts are still rough around the edges. This can help developers decide on whether or not X framework is a good choice for their problem.