4 ms·

Who still uses IE11 anyway?

by yannoninator 5y ago

bovermyer 5y ago
Not sure. Globally, IE has 0.71% browser market share. SOMEONE is using it.
speedgoose 5y ago
Some legacy Windows software are stuck with IE 11 for their webviews.
nextweek2 5y ago
This is an old joke: Those downloading Chrome.
ta988 5y ago
Some lab equipment with internal HTTP servers require IE6 to be configured . And they are still sold... It is almost usable in IE11 but you have to disable tons of safeties.
deleted 5y ago
[deleted]
jackdh 5y ago
Speaking from previous experience it's likely legacy systems built for even older IE's (8,9,10) were patched to IE11 but not any further due to time (money) involved.
goda90 5y ago
I work writing enterprise software. IE is integrated into our legacy desktop client so we can render new web pieces until everything is updated to be web, then we'll switch to Electron for the client. It's a huge pain to get things like CSS to work right, and the dev tools are super buggy.
omh 5y ago
This week I've been dealing with an IE11 related problem from a C# app. The C# app is built using WebBrowser Control[1] which is tightly integrated with the app itself. WebBrowser only supports IE11 but the webapps that it connects to are increasingly dropping support. The vendor is reluctant to upgrade their app because the replacement options apparently (?) require extensive refactoring to get the same integration. IE11 seems to be in a weird limbo. But the fact that it's still technically supported by Microsoft means that conservative software vendors aren't forced to migrate. [1] https://docs.microsoft.com/en-us/dotnet/desktop/winforms/controls/webbrowser-control-windows-forms https://docs.microsoft.com/en-us/dotnet/desktop/winforms/con...
- tester34 5y ago
  How about WebView2? https://docs.microsoft.com/en-us/microsoft-edge/webview2 https://docs.microsoft.com/en-us/microsoft-edge/webview2
  - omh 5y ago
    I've been asking the vendor the same question! They seem to think it's not a drop-in replacement and don't want to rework their code to deal with the changes. I'm not sure to what extent this is Microsoft making compatibility hard or just a lazy vendor.
    - adzm 5y ago
      It is a completely different API compared to WebBrowser/MSHTL. It is akin to using CEF (Chromium Embedded Framework) for the most part. This can require rewriting pretty much everything that interacts with the browser currently as well as dealing with a completely different threading and event model in the new APIs (both WebView2 and WebKit/CEF/etc)
H12 5y ago
Employees who are forced to use it at work. Some large companies put installation restrictions on third-party software for security reasons, and find that throwing money at Microsoft for an enterprise support contract is cheaper than re-engineering their ancient internal software to work on something other than IE. And because these are also the types of giant companies that tend to shit money, there are plenty of mid-sized B2B saas companies willing to bend over backwards to win a contract and earn their droppings. So I'm sure there are a good few developers forced to support IE11 by a bad contract who will be bummed by this news. But full deprecation has to happen eventually, and it will only help the effort to have engineers telling middle management "the project will take twice as long because we have to support IE11".
- o_m 5y ago
  This used to be the case, but not anymore. The new Edge browser has IE mode which makes the browser behave like IE 11. Only those using Windows XP and Vista won't be able to use the new Edge browser, but they have bigger issues, like not getting any security updates.
jaywalk 5y ago
14% of the users of my application. In the US. Yeah, it's practically gone from the public web. But when you look at business stuff, there is a lot more IE out there still than people realize.

Who still uses IE11 anyway?

bovermyer 5y ago

Not sure. Globally, IE has 0.71% browser market share. SOMEONE is using it.

speedgoose 5y ago

Some legacy Windows software are stuck with IE 11 for their webviews.

nextweek2 5y ago

This is an old joke: Those downloading Chrome.

ta988 5y ago

Some lab equipment with internal HTTP servers require IE6 to be configured . And they are still sold... It is almost usable in IE11 but you have to disable tons of safeties.

deleted 5y ago

[deleted]

jackdh 5y ago

Speaking from previous experience it's likely legacy systems built for even older IE's (8,9,10) were patched to IE11 but not any further due to time (money) involved.

goda90 5y ago

I work writing enterprise software. IE is integrated into our legacy desktop client so we can render new web pieces until everything is updated to be web, then we'll switch to Electron for the client. It's a huge pain to get things like CSS to work right, and the dev tools are super buggy.

omh 5y ago

This week I've been dealing with an IE11 related problem from a C# app. The C# app is built using WebBrowser Control[1] which is tightly integrated with the app itself. WebBrowser only supports IE11 but the webapps that it connects to are increasingly dropping support. The vendor is reluctant to upgrade their app because the replacement options apparently (?) require extensive refactoring to get the same integration. IE11 seems to be in a weird limbo. But the fact that it's still technically supported by Microsoft means that conservative software vendors aren't forced to migrate. [1] https://docs.microsoft.com/en-us/dotnet/desktop/winforms/controls/webbrowser-control-windows-forms https://docs.microsoft.com/en-us/dotnet/desktop/winforms/con...

tester34 5y ago
How about WebView2? https://docs.microsoft.com/en-us/microsoft-edge/webview2 https://docs.microsoft.com/en-us/microsoft-edge/webview2
- omh 5y ago
  I've been asking the vendor the same question! They seem to think it's not a drop-in replacement and don't want to rework their code to deal with the changes. I'm not sure to what extent this is Microsoft making compatibility hard or just a lazy vendor.
  - adzm 5y ago
    It is a completely different API compared to WebBrowser/MSHTL. It is akin to using CEF (Chromium Embedded Framework) for the most part. This can require rewriting pretty much everything that interacts with the browser currently as well as dealing with a completely different threading and event model in the new APIs (both WebView2 and WebKit/CEF/etc)

H12 5y ago

Employees who are forced to use it at work. Some large companies put installation restrictions on third-party software for security reasons, and find that throwing money at Microsoft for an enterprise support contract is cheaper than re-engineering their ancient internal software to work on something other than IE. And because these are also the types of giant companies that tend to shit money, there are plenty of mid-sized B2B saas companies willing to bend over backwards to win a contract and earn their droppings. So I'm sure there are a good few developers forced to support IE11 by a bad contract who will be bummed by this news. But full deprecation has to happen eventually, and it will only help the effort to have engineers telling middle management "the project will take twice as long because we have to support IE11".

o_m 5y ago
This used to be the case, but not anymore. The new Edge browser has IE mode which makes the browser behave like IE 11. Only those using Windows XP and Vista won't be able to use the new Edge browser, but they have bigger issues, like not getting any security updates.

jaywalk 5y ago

14% of the users of my application. In the US. Yeah, it's practically gone from the public web. But when you look at business stuff, there is a lot more IE out there still than people realize.