Complexity is a choice, not a property of the platform
Writing in response to Remy Sharp's The web didn't change, you did, the argument is straightforward: what we call "complexity" in modern front-end work is largely optional. As Sharp puts it:
Web development did not change. Web development grew. There are more options now, not different options.
Browsers have become more capable and still work with web pages built over 20 years ago.
[…] The web really didn't change. It really didn't become complex. The web development process is not one single path. There is simply more choice and more options.
The practical consequence is that when a small problem gets an enormous framework, that is a decision made by the developer, not a requirement handed down by the web. Nothing forces the newest toolchain onto a site whose needs are already met by older techniques — using float instead of flexbox is fine if it works.
Tooling choices and the absence of a canonical stack
Web design carries a fair amount of ego, and plenty of people criticize others for picking the "incorrect" tools. The reality is that no perfect tool exists and no perfect way to build a site exists. That is uncomfortable, but it also means nothing is fixed and everything remains open to experimentation.
A concrete example: Sass is a constant in side projects, a choice some developers would dismiss now that emotion, Tachyons, plain CSS and PostCSS are all available. Familiarity and the leverage it provides are legitimate reasons to stay. The same person can reach for emotion at their day job or try something new as it appears.
Age is not a quality signal
Being old does not make technology bad, and being new does not make it good. That sentiment runs through the discussion around "Front-End Dissatisfaction (and Backing Off)" and its comment thread. The point is consistent with Sharp's framing: you are free to pick the tools that fit the problem and your own knowledge, rather than the ones with the most current momentum.



