[breatheoften]

This response is interesting. The engineer attempts to differentiate the philosophy behind chromes feature prioritization as being due to their desire to implement features in a manner that conforms with the ideals behind the "extensible web" manifesto.

But there is a sense to which "extensible web" focused engineering is inherently at odds with a desire to contain browser complexity and to prioritize the security, performance, and stability of the average web site browsing experience across platforms.

My general experience with using the web these days (with any browser) is that on average sites I visit seem:

1. More broken 2. Slower 3. More invasive

There's definitely an extent to which this is "not browser makers fault, this is the fault of site developers" -- however to completely abdicate platform vendors responsibility and say that it's not a requirement for browser technology to solve is to (potentially) watch the whole web platform erode to the point where it is no longer sufficient to satisfy users needs. In a way it's balmer on stage chanting "developers developers developers" vs jobs in a drum circle meditating "users users users". Not that I necessarily think Safari is the best drum circle development example -- I'm more tempted by "brave".