I usually come across these ideas where the author “bemoans” about the collapse of the web and usually has a radical “fix” to make it work. The complexity in the web browsers is for a reason- to ship in even more complexity for end users and push through proprietary standards. Everyone likes to be the gatekeeper.
The web has evolved through a combination of specifications and implementations. Organizations like the WHATWG, W3C, and IETF have been collaboration spaces for independent developers, corporations, and academics to discuss potential new features of the web. Then, browsers would test those ideas out in a variety of implementations.This was an interesting structural piece: it reassured us all that it was possible to follow along, and that a multi-participant web was one of our goals. It was frustrating to pull up caniuse and see blank spots, but the idea was that different browsers may take the lead in some areas, but everyone catches up eventually. Chrome was not always the first to jump on features, or the first to optimize.A clean start for the web – macwright.com
Rest of the write up deals with the various engineering issues. My concern is that web has shrunk to the level of apps.Most users access it through mobile (while I prefer the converse) as it allows a broader range of freedom. Mobile workflows constrain you artificially. They force everything through tiny apps (which compete for attention) and hence brings forth its own set of issues (especially for health intervention).