"But his customers kept asking him to make sure their websites looked good in Explorer, which remained the default browser in South Korean government offices and many banks for years."

I wish this were just South Korea. (Sorry, Koreans.) But it's also true here in the US, and it boggles my mind. Many of my team's clients are banks and other large financial institutions, and it wasn't until a few months ago that we started rewriting our web app with zero regard for IE. Until then, we had to constantly test all our code on our company-provided MacBooks in a VM running Windows and IE11 (IE10 until last year, in fact). I am overjoyed that Microsoft has finally put their giant mistake to rest, and I only hope everyone using it follows suit (though I doubt it for awhile).

Man, who remembers the days of requiring massive try-catch sequences attempting to instantiate a variety of ActiveX plugins just to get XHR-facilitated AJAX to work in IE? I do, and I wish I didn't. Or specific comments -- or was it CDATA? -- to cause JS to only run in IE? Ah, the bad old days.