3 ms·
Lots of shade being thrown at Microsoft, I don't think it's wrong to do that, but I also think that the real problem is being completely ignored -- corporate IT
by bane 8y ago
Lots of shade being thrown at Microsoft, I don't think it's wrong to do that, but I also think that the real problem is being completely ignored -- corporate IT departments that demanded (still demand) IE due to some kind of "security policy".
A few of the places I've worked at had very strong policies about what software was installed on the corporate boxes, and IE was almost universally pushed due to "security reasons" even when it was widely known to be significantly less secure than any concurrent competing browser.
The thing I think about here is that the reason these enterprise websites are broken is not that they're compatible with IE, but that IE wasn't compatible with web standards, and thus sites were hacked at to fit within IE's brokenness. And now the entire world has moved to better conformance with web standards and organizations are stuck with what was an unsecure web browser years ago, and is getting even more unsecure going forward.
Corporate IT Security departments of old get the blame in my book. If they had simply said "nope, IE is not secure, it is not permitted on our systems" the world would literally be a better place. Instead they sent a strong demand signal that Microsoft simply fulfilled.
- AnIdiotOnTheNet 8y agoIt isn't really about bugs in the application, it's that IE has fine-grained security controls and they are easily configured via GPO.