I'd also comment on his speed/mobile concerns: The web is both big and small, fast and slow, dynamic and static. Most developers have a hard time accomplishing both aspects of the duality, but at least they try.

You can praise the small, slow, and static sites, because of what they're good at, but let us also point out that they aren't optimized for desktop browsers to date, don't utilize the speed of their upper clientele of users to offload processing and handling to the front end, and also don't accomplish as much as possible without the need of a state change.

I like what you put regarding complexity, because let's be realistic, as web developers, are jobs are constantly shifting from technology to architecture to agile to scrum to etc.

The author is complaining about mistakes in hindsight, and tries to complain about modern web apps having the same problems? There's always a new frontier in web development; if you can't handle the fact that certain api's become deprecated or that certain features a dev used aren't completely implemented, then do it better yourself. Update older tutorials, evangelize the correct approaches to problems, then, you'll do you part to remove some misinformation of outdated solutions that others are using.