There is an issue with monoculture of rendering engines.
Developers assume every browser have the same things implemented and start to build around this assumption. Also Google can dictate how the web looks like.
Microsoft was hostile to web standards and would not implement W3C recommendations in Internet Explorer, which meant most web devs would be wasting their time implementing those standards since almost all users were on IE back then.
Chromium actually does follow standards, and has adoption through voluntary downloads rather than by being preinstalled on the monopoly OS.
Creating artificial “feature” based defacto standards
Chrome offers adherence to standards as one of their features. But it also introduces new features that look like standards, meant to increase profits for the parent company.
There is an issue with monoculture of rendering engines. Developers assume every browser have the same things implemented and start to build around this assumption. Also Google can dictate how the web looks like.
Exactly, we’ve seen this previously with Internet explorer.
And Netscape before that, it had reached 90% market share.
You’re missing the point. Netscape implemented the html standard, they didn’t introduce new, proprietary “features” to gain that market share.
That’s not the same.
Microsoft was hostile to web standards and would not implement W3C recommendations in Internet Explorer, which meant most web devs would be wasting their time implementing those standards since almost all users were on IE back then.
Chromium actually does follow standards, and has adoption through voluntary downloads rather than by being preinstalled on the monopoly OS.
There are two things to consider here:
Chrome offers adherence to standards as one of their features. But it also introduces new features that look like standards, meant to increase profits for the parent company.