I'd argue that Microsoft is much worse, what with their utter ubiquity in corporate environments, linkedin, github and win home users. Google ruined cell phones and Microsoft ruined personal computing.
The problem is it is often difficult to decide where incompetence ends and where malicious begins. Microsoft Edge or at least EdgeHTML has a stated goal of being 100% compatible with Google Chrome. As you might guess, it isn't even close. Why? There are far too many competent people at Microsoft to say "never attribute to malice what can be described by incompetence". This isn't the kind of incompetence at Equifax.
Its sad that one has to be 100% compatible with Chrome. Is this something that someone at Microsoft really said? one should have to be compatible with the standards. If that statement is true, then it supports the claim of Google's dominance- which is unhealthy for the browser market, and users.
Maybe I didn't capture the wording perfectly. Maybe I reported what I heard and not what they said?
> any Edge-WebKit differences are bugs that we’re interested in fixing
context:
> We recommend that web developers avoid UA sniffing as much as possible; modern web platform features are nearly all detectable in easy ways. Over the past year, we’ve seen some UA-sniffing sites that have been updated to detect Microsoft Edge… only to provide it with a legacy IE11 code path. This is not the best approach, as Microsoft Edge matches ‘WebKit’ behaviors, not IE11 behaviors (any Edge-WebKit differences are bugs that we’re interested in fixing). In our experience Microsoft Edge runs best on the ‘WebKit’ code paths in these sites. Also, with the internet becoming available on a wider variety of devices, please assume unknown browsers are good – please don’t limit your site to working only on a small set of current known browsers. If you do this, your site will almost certainly break in the future.
Personally, I think operations infrastructure should take a a more hands-off approach and let people use whatever web browsers they want and focus on educating users on why and how rather than on what. However, it is not practical for a variety of reasons. I had a chance to chat with a Chrome team member. He assured me that if you are an IT department and want to deploy Chrome in your enterprise, the Chrome team is committed to stand behind you. You can start at https://enterprise.google.com/chrome/chrome-browser/ If you have custom home-grown applications that require a legacy browser, you can centrally manage lists. In practice, this means that users will just need to open Google Chrome. If they go to some address that requires a legacy browser, Chrome will automatically kick you to the legacy browser. When someone continues on the legacy browser, you can kick them back to Google Chrome and have them continue there. I think this is the better path forward especially considering that Windows 7 will end of life in 2020. While I love Mozilla Firefox, I think Chrome is your only choice when it comes to Enterprise desktop.
For web developers like me, Edge has such a small market share that it makes no sense to test for Edge. From what I understand above, I shouldn't have to test for Microsoft Edge. It shouldn't have any of the legacy stuff from MSIE. That being said, threats of mono culture aside, I think it is best for any corporation to move their web browser to Google Chrome. Your people will be more productive on Google Chrome because it is the browser they know and love.
