JavaScript performance, WebAssembly, and Shared Memory in Microsoft Edge

Re:JavaScript performance, WebAssembly, and Shared Memory in... by sangnoir on Friday April 21, 2017 @10:09AM (#14165736)

>> 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.

[ Parent | on HN ]

Re:JavaScript performance, WebAssembly, and Shared Memory in... by bzbarsky on Saturday April 22, 2017 @12:36AM (#14171139)

In South Korea, Windows achieved lock-in via legislation requiring IE (or more precisely ActiveX). See 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.

[ Parent | on HN ]