2 ms·
>> We didn't blame Microsoft for "lock-in" back in the IE-only website days >Yes, we did. My phrasing wasn't as clear as I thought - what I meant to say "We d
by sangnoir 10y ago
>> We didn't blame Microsoft for "lock-in" back in the IE-only website days
>Yes, we did.
My phrasing wasn't as clear as I thought - what I meant to say "We didn't blame Microsoft for 'lock-in' due to 3rd parties creating IE-only websites, we blamed the 3rd parties." Implementing non-standard extensions was par for the course during the browser wars (Netscape did the same), and I doubt there was a real expectation of achieving lock-in via the browser by either party: Windows achieved lock-in via Windows, Office and legal threats. Not IE.
- bzbarsky 10y agoIn South Korea, Windows achieved lock-in via legislation requiring IE (or more precisely ActiveX). See https://www.washingtonpost.com/world/asia_pacific/due-to-security-law-south-korea-is-stuck-with-internet-explorer-for-online-shopping/2013/11/03/ffd2528a-3eff-11e3-b028-de922d7a3f47_story.html https://www.washingtonpost.com/world/asia_pacific/due-to-sec... for a decent summary. And yes, there was very much expectation of achieving lock-in via ActiveX. And it worked in some cases.