Sure, but what’s the original sin at work here? Google investing their time and resources into their browser projects, or the fact that web became this complex

Sure, but what’s the original sin at work here? Google investing their time and resources into their browser projects, or the fact that web became this complex mess because web developers beat the drum for 15 going on 20 years that the web should be an app runtime? Duplicating an app runtime feature for feature and bug for bug is difficult in a capital intensive sort of way. Even companies that can afford the expenditure, primarily Microsoft, decided to get out of that game because that level of expenditure comes with its own opportunity costs even at their level. And there are alternatives: WebKit and Mozilla, one of those is the exclusive web renderer for iPhones and iPads which is not an insignificant amount of hardware in the world. Google puts the work in. It’s really just that, and it’s their private prerogative to put that work in if they so choose, where others choose not to. The diversity of rendering engines isn’t great compared to say 15 years ago, but it’s not so bad that it’s a total monoculture in the way IE6 was. Actually thinking about it, more people are using more and different browser rendering engines than back then because Chromium-based browsers don’t have the total dominance that IE6 did, and there’s a lot more people on the web than there used to be. We had diversity, but we’re talking iCab, pre-WebKit OmniWeb, Opera on Presto, and yeah, Trident’s not really around anymore, but it was there, and so was Gecko and WebKit. At least you don’t need a browser that supports ActiveX controls for regular websites anymore.