If Microsoft really believes no-one needs IE, why is it still shipping it as part of Windows 10? Specifically, why is it still shipping IE as the only browser as part of Windows 10 Enterprise LTSC, including LTSC 2019? Yes, that is the version of Windows 10 with an "extended support end date of 9 January 2029"* * https://support.microsoft.com/en-us/help/13853/windows-lifec...
Retiring Internet Explorer
81–90 of 122 posts
Re: Retiring Internet Explorer
#82Earlier quoted context omitted.
The second sentence is not much of a surprise; why would something require IE if not for its ActiveX support? Certainly, some things might render brokenly in other browsers, but ActiveX is the only real "IE-only feature" a site might depend on.
VBScript and HTA files (HTML Applications) come to mind. HTAs were actually an interesting direction, once used them to ship a simple application (a very visual FTP upload). It was unsandboxed HTML and JS that could access all the ActiveX APIs. A bit like Electron now. Can't image there not being a few niches out there that heavily rely (or relied) on HTAs
Re: Retiring Internet Explorer
#83> Burndown List >> Banking, especially in Asia My bank in China requires Windows + IE + a custom ActiveX control to use their Internet banking. As a result, I don't use it. One of my accounts can be used via their mobile app (if you read Chinese or have another phone to use camera translation). My business account cannot be, and I am therefore required to visit a branch along with my official chop (seal / stamp) when…
Re: Retiring Internet Explorer
#84> Burndown List >> Banking, especially in Asia My bank in China requires Windows + IE + a custom ActiveX control to use their Internet banking. As a result, I don't use it. One of my accounts can be used via their mobile app (if you read Chinese or have another phone to use camera translation). My business account cannot be, and I am therefore required to visit a branch along with my official chop (seal / stamp) when…
"My bank in China requires Windows + IE + a custom ActiveX control to use their Internet banking. As a result, I don't use it." Why not have a VM just for internet banking? Surely that's easier than taking the chop out of the safe and waiting in line at the branch.
Re: Retiring Internet Explorer
#85This is tangential, but I wonder how Chrome got so far ahead, not in market share but in features and quality, even with IE's 10+ year head start. Did Google just throw more programmers at the problem, or was there more to it? I suspect this has already been discussed to death, so pointers to previous discussions would be good.
Re: Retiring Internet Explorer
#86> A fascinating set of circumstances led to Internet Explorer’s dominance in Asian markets. First, early browsers had poor support for Unicode and East Asian character sets, forcing website developers to build their own text rendering atop native code plugins (ActiveX). South Korea mandated use of a locally-developed cipher (SEED) for banking transactions, and this cipher was not implemented by browser developers… Ac…
I'm Korean so I glad to see someone speaks out this. Actually it was rather inevitable, partially because of the U.S. gov that time. The Korean gov wanted to grow e-commerce/e-banking in 1999 but the American gov did not allow to export cipher higher than 40 bits. As a result the Korean gov had to develop its own 128 bits cipher (SEED). It was even before AES/SSL/TLS were introduced so the whole crypto stack was impl…
> I would say it was quite pioneer in 1999 but since then the gov don't even dare to replace the crypto policies. Now we are stuck at this in 2020.
AFAIK, the government removed the SEED-only policy some time ago (in the early 2010s) but it’s the price of the system infrastructure that makes them keep using the old, ActiveX based systems.
I’m personally thankful for smartphone’s to come, as the banks started to consider implementing support for other operating systems. If it wasn’t the abundance of smartphones, I believe there might have not been any non-windows/IE support. Its much better nowadays, with multiple startups in the finance space like Toss, Kakao, etc...
Re: Retiring Internet Explorer
#87> IE9 was a fantastic, best-of-its-time browser, and I’ll forever be proud of it. But as IE9 wound down and the Windows 8 adventure began, it was already clear that its lead would not last against the Chrome juggernaut. This is tangential, but I wonder how Chrome got so far ahead, not in market share but in features and quality, even with IE's 10+ year head start. Did Google just throw more programmers at the problem…
1. Significantly faster Javascript execution engine (V8) than MSIE and Firefox
2. Process isolation model improved security posture
3. Multi-platform compatibility (Windows/Mac/Linux) very soon after launch
4. Improved usability: browser history search, autocomplete in address bar, etc.
Here's the original announcement (featuring Sundar Pichai, then VP of Product, now CEO): https://www.youtube.com/watch?v=LRmrMiOWdfc
Re: Retiring Internet Explorer
#88Earlier quoted context omitted.
I'm Korean so I glad to see someone speaks out this. Actually it was rather inevitable, partially because of the U.S. gov that time. The Korean gov wanted to grow e-commerce/e-banking in 1999 but the American gov did not allow to export cipher higher than 40 bits. As a result the Korean gov had to develop its own 128 bits cipher (SEED). It was even before AES/SSL/TLS were introduced so the whole crypto stack was impl…
What I think is kind of interesting is that South Korea arguably had/has the technical know-how to have built it's own domestic browser with SEED and good Hangul/Hanja language support built into it and ended up with a very siloed alternative web. As an example, I'm thinking of the ubiquity of the Hangul Word Processor over Microsoft Word (which apparently has been around for over 30 years!) which gained near ubiquit…
There are two major factors in the ubiquity of HWP:
1. Its use of the de facto standard format in the SK government (the de jure standard is the ODF since 2007, but its use is virtually nonexistent). This stems from the fact that it was the most viable word processor supporting Hangul the script back in 1990s.
2. Its excellent support of table-based layout. HWP is a decent word processor in comparison to MS Word, and in some cases it is even superior. Koreans used to produce lots of documents based on tables [1] and HWP's UX was specially tailored to them. MS Word lagged behind for a long time, probably because this use case is not common in English worlds.
[1] You can search for "이력서" (résumé) to see what I mean. Even a plain document tends to be styled in this way.
Re: Retiring Internet Explorer
#89> IE9 was a fantastic, best-of-its-time browser, and I’ll forever be proud of it. But as IE9 wound down and the Windows 8 adventure began, it was already clear that its lead would not last against the Chrome juggernaut. This is tangential, but I wonder how Chrome got so far ahead, not in market share but in features and quality, even with IE's 10+ year head start. Did Google just throw more programmers at the problem…
Re: Retiring Internet Explorer
#90I understand Microsoft needs to continue supporting IE for old websites but my boss a couple days ago used the Microsoft Lifecycle Policy as a reason why we, as website developers, need to support IE11 also. I would like articles saying people shouldn't use IE to also explicity answer the question, "Should website developers support IE?"