Supporting IE11... still.
-
So, I'm about to release a new website. Over the past few years I've gotten used to using polyfills to handle older browsers like IE11 for public sites, but the more and more polyfills I tack on to a site for compatiablity the slower IE11 is running. Yes, it supports flexbox and also a basic CSS grid, so I can get IE11 to work-ish if I need to. My question is though, how many of y'all are still targeting IE11 for publicly accessible sites? I've made this site work in IE11, but still... The latest stats I've seen suggest IE is still used for approximately 6% of desktop traffic and about 3% of all web traffic (if you combine desktop and mobile). But is making your site bloated for 3% of people really worth it... I used to think so, but with WASM down the road, etc. I mean for real... it's time IE died. What do y'all think?
Jeremy Falcon
-
So, I'm about to release a new website. Over the past few years I've gotten used to using polyfills to handle older browsers like IE11 for public sites, but the more and more polyfills I tack on to a site for compatiablity the slower IE11 is running. Yes, it supports flexbox and also a basic CSS grid, so I can get IE11 to work-ish if I need to. My question is though, how many of y'all are still targeting IE11 for publicly accessible sites? I've made this site work in IE11, but still... The latest stats I've seen suggest IE is still used for approximately 6% of desktop traffic and about 3% of all web traffic (if you combine desktop and mobile). But is making your site bloated for 3% of people really worth it... I used to think so, but with WASM down the road, etc. I mean for real... it's time IE died. What do y'all think?
Jeremy Falcon
Do not support IE - if you will all problems will land on your desk, as MS does not support it anymore...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
-
Do not support IE - if you will all problems will land on your desk, as MS does not support it anymore...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
Starting to believe it. I'd love to know more about that 6% demographic. I'm using netmarketshare.com for the info, but it only tells you so much.
Jeremy Falcon
-
So, I'm about to release a new website. Over the past few years I've gotten used to using polyfills to handle older browsers like IE11 for public sites, but the more and more polyfills I tack on to a site for compatiablity the slower IE11 is running. Yes, it supports flexbox and also a basic CSS grid, so I can get IE11 to work-ish if I need to. My question is though, how many of y'all are still targeting IE11 for publicly accessible sites? I've made this site work in IE11, but still... The latest stats I've seen suggest IE is still used for approximately 6% of desktop traffic and about 3% of all web traffic (if you combine desktop and mobile). But is making your site bloated for 3% of people really worth it... I used to think so, but with WASM down the road, etc. I mean for real... it's time IE died. What do y'all think?
Jeremy Falcon
Microsoft outright said [IE was a compatibility solution](https://www.theverge.com/2019/2/8/18216767/microsoft-internet-explorer-warning-compatibility-solution) and is legacy code. We no longer support IE. If it works, great! If it doesn't work, we'll take a peek and see if there's an easy fix, and if so, great! But otherwise: move on. Enabling users to continue using software that holds back the industry is bad for everyone. (and great to hear from you again, Jeremy!)
cheers Chris Maunder
-
Microsoft outright said [IE was a compatibility solution](https://www.theverge.com/2019/2/8/18216767/microsoft-internet-explorer-warning-compatibility-solution) and is legacy code. We no longer support IE. If it works, great! If it doesn't work, we'll take a peek and see if there's an easy fix, and if so, great! But otherwise: move on. Enabling users to continue using software that holds back the industry is bad for everyone. (and great to hear from you again, Jeremy!)
cheers Chris Maunder
Agreed on all points 100% man. If this site wasn't a pay, for-profit site... I'd dump it like right now. There's that crazy part of me I can't let go of that says... what about that 3%. lol This will be the last site I make that supports it though... ever. Even Bootstrap 5 is dropping in-built support for it, it needs to die. Not sure if I should say this publicly, but I just did a contract for Amex and they still wanted a in-house product to support IE11... like internal here... not public. What's the stats like for CP? I'd reckon most of us devs have dumped it along time ago, so like 0.000001% I'd bet.
Chris Maunder wrote:
and great to hear from you again, Jeremy!
Likewise. How's the kids? Still on a Mac running Windows?
Jeremy Falcon
-
So, I'm about to release a new website. Over the past few years I've gotten used to using polyfills to handle older browsers like IE11 for public sites, but the more and more polyfills I tack on to a site for compatiablity the slower IE11 is running. Yes, it supports flexbox and also a basic CSS grid, so I can get IE11 to work-ish if I need to. My question is though, how many of y'all are still targeting IE11 for publicly accessible sites? I've made this site work in IE11, but still... The latest stats I've seen suggest IE is still used for approximately 6% of desktop traffic and about 3% of all web traffic (if you combine desktop and mobile). But is making your site bloated for 3% of people really worth it... I used to think so, but with WASM down the road, etc. I mean for real... it's time IE died. What do y'all think?
Jeremy Falcon
You do have an advantage if you do support IE, and that is that you are more likely to get that business since others may not be supporting that browser. And there is also how much will it impact you to include ie support. It if is easy, just as well support IE. Depends on the tools you are using too.
-
So, I'm about to release a new website. Over the past few years I've gotten used to using polyfills to handle older browsers like IE11 for public sites, but the more and more polyfills I tack on to a site for compatiablity the slower IE11 is running. Yes, it supports flexbox and also a basic CSS grid, so I can get IE11 to work-ish if I need to. My question is though, how many of y'all are still targeting IE11 for publicly accessible sites? I've made this site work in IE11, but still... The latest stats I've seen suggest IE is still used for approximately 6% of desktop traffic and about 3% of all web traffic (if you combine desktop and mobile). But is making your site bloated for 3% of people really worth it... I used to think so, but with WASM down the road, etc. I mean for real... it's time IE died. What do y'all think?
Jeremy Falcon
40% of our customers are still on different versions of IE. They're a slow moving bunch. Apparently the average age of their computers are 7 years. Luckily I don't do front end stuff.
Wrong is evil and must be defeated. - Jeff Ello
-
So, I'm about to release a new website. Over the past few years I've gotten used to using polyfills to handle older browsers like IE11 for public sites, but the more and more polyfills I tack on to a site for compatiablity the slower IE11 is running. Yes, it supports flexbox and also a basic CSS grid, so I can get IE11 to work-ish if I need to. My question is though, how many of y'all are still targeting IE11 for publicly accessible sites? I've made this site work in IE11, but still... The latest stats I've seen suggest IE is still used for approximately 6% of desktop traffic and about 3% of all web traffic (if you combine desktop and mobile). But is making your site bloated for 3% of people really worth it... I used to think so, but with WASM down the road, etc. I mean for real... it's time IE died. What do y'all think?
Jeremy Falcon
-
So, I'm about to release a new website. Over the past few years I've gotten used to using polyfills to handle older browsers like IE11 for public sites, but the more and more polyfills I tack on to a site for compatiablity the slower IE11 is running. Yes, it supports flexbox and also a basic CSS grid, so I can get IE11 to work-ish if I need to. My question is though, how many of y'all are still targeting IE11 for publicly accessible sites? I've made this site work in IE11, but still... The latest stats I've seen suggest IE is still used for approximately 6% of desktop traffic and about 3% of all web traffic (if you combine desktop and mobile). But is making your site bloated for 3% of people really worth it... I used to think so, but with WASM down the road, etc. I mean for real... it's time IE died. What do y'all think?
Jeremy Falcon
The relevant statistic is not the percentage of people using IE11 on the 'net, but the percentage of people using IE11 that visit your site(s). How about maintaining counter for the different browsers used to visit your site, and seeing whether IE11 is worth the effort to support? On future professional (== for pay) projects, I would quote two prices - one not including IE11 support, and one including it. I would also give the prospective client the latest IE11 usage statistics, and let them decide whether it is worth it.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
So, I'm about to release a new website. Over the past few years I've gotten used to using polyfills to handle older browsers like IE11 for public sites, but the more and more polyfills I tack on to a site for compatiablity the slower IE11 is running. Yes, it supports flexbox and also a basic CSS grid, so I can get IE11 to work-ish if I need to. My question is though, how many of y'all are still targeting IE11 for publicly accessible sites? I've made this site work in IE11, but still... The latest stats I've seen suggest IE is still used for approximately 6% of desktop traffic and about 3% of all web traffic (if you combine desktop and mobile). But is making your site bloated for 3% of people really worth it... I used to think so, but with WASM down the road, etc. I mean for real... it's time IE died. What do y'all think?
Jeremy Falcon
I've never specifically targeted IE, in any of its bastardized forms.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
So, I'm about to release a new website. Over the past few years I've gotten used to using polyfills to handle older browsers like IE11 for public sites, but the more and more polyfills I tack on to a site for compatiablity the slower IE11 is running. Yes, it supports flexbox and also a basic CSS grid, so I can get IE11 to work-ish if I need to. My question is though, how many of y'all are still targeting IE11 for publicly accessible sites? I've made this site work in IE11, but still... The latest stats I've seen suggest IE is still used for approximately 6% of desktop traffic and about 3% of all web traffic (if you combine desktop and mobile). But is making your site bloated for 3% of people really worth it... I used to think so, but with WASM down the road, etc. I mean for real... it's time IE died. What do y'all think?
Jeremy Falcon
I have a client whose internal, country-wide web app is implemented using Java Server Pages and applets which interact with local hardware through JNIs. So, guess what I'll be stuck supporting until the dust buildup shorts out a vacuum tube at some point? Oy!
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright "I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
-
So, I'm about to release a new website. Over the past few years I've gotten used to using polyfills to handle older browsers like IE11 for public sites, but the more and more polyfills I tack on to a site for compatiablity the slower IE11 is running. Yes, it supports flexbox and also a basic CSS grid, so I can get IE11 to work-ish if I need to. My question is though, how many of y'all are still targeting IE11 for publicly accessible sites? I've made this site work in IE11, but still... The latest stats I've seen suggest IE is still used for approximately 6% of desktop traffic and about 3% of all web traffic (if you combine desktop and mobile). But is making your site bloated for 3% of people really worth it... I used to think so, but with WASM down the road, etc. I mean for real... it's time IE died. What do y'all think?
Jeremy Falcon
This is a more complex question that it may appear to be. What is the projected user base? Desktop, mobile, or both? Where are customers located? Industrial nations? Mobile will be using a "modern" OS -- what desktop OS are in play? Does your client have other commercial sites? If so, look at their stats for browser and OS. I found several stats sites that put IE as ~1.4% of the overall browser market, and ~5% for the desktop market. But that's overall -- these figures may not be accurate for YOUR market. What is the projected budget to develop and maintain the site for IE? If the budget is 10% of the total and the expected revenue from IE customers is 3%, supporting IE is counter-productive. My group made the decision to support the last 3 revs of the top 5 browsers + Edge. Costs are the driving factor, not only development time to support quirky browsers, but testing time to test that plethora of quirky browsers. We write current JavaScript and use Babble to transpile to support our planned user base, which also helps reduce dev & test costs. Why Edge? It's built into Windows so it's present for most of our user base. [Granted, the change to Chromium has eliminated a lot of testing.] That said, our site works on most modern browsers ... excepting IE (which is far from modern). YMMV
-
Agreed on all points 100% man. If this site wasn't a pay, for-profit site... I'd dump it like right now. There's that crazy part of me I can't let go of that says... what about that 3%. lol This will be the last site I make that supports it though... ever. Even Bootstrap 5 is dropping in-built support for it, it needs to die. Not sure if I should say this publicly, but I just did a contract for Amex and they still wanted a in-house product to support IE11... like internal here... not public. What's the stats like for CP? I'd reckon most of us devs have dumped it along time ago, so like 0.000001% I'd bet.
Chris Maunder wrote:
and great to hear from you again, Jeremy!
Likewise. How's the kids? Still on a Mac running Windows?
Jeremy Falcon
I actually switched to a Dell! For about 3 months. And hated it with a dark, fierce, unhealthy passion. I'm back on a Mac. My biggest issue (and to ensure this thread is now fully off topic) is we're still on WebForms, which .NET Core doesn't support, so I can't easily just switch to VS for Mac or VS Code. Know anyone who would love nothing better than to convert a WebForms site with roughly 300 web controls over to something better? Blazor and .NET 5? I mean: how hard could it be, really? :rolleyes:
cheers Chris Maunder
-
I actually switched to a Dell! For about 3 months. And hated it with a dark, fierce, unhealthy passion. I'm back on a Mac. My biggest issue (and to ensure this thread is now fully off topic) is we're still on WebForms, which .NET Core doesn't support, so I can't easily just switch to VS for Mac or VS Code. Know anyone who would love nothing better than to convert a WebForms site with roughly 300 web controls over to something better? Blazor and .NET 5? I mean: how hard could it be, really? :rolleyes:
cheers Chris Maunder
Chris Maunder wrote:
I'm back on a Mac.
The irony here is... I'm the Mac fanboy but yet I'm on a PC. What is this world coming to? You hear about Apple Silicon? They're switching back to RISC (via ARM this time) processors like in the olden days. Except now Windows will still run on ARM so we're still good on the dual boot front. Never thought we'd see the day.
Chris Maunder wrote:
Know anyone who would love nothing better than to convert a WebForms site with roughly 300 web controls over to something better? Blazor and .NET 5? I mean: how hard could it be, really?
Hah... sure man. Just ask any rookie PM... all you need to do is press that shiny magic button to fix everything. That's what the sales pitch said. :)
Jeremy Falcon
-
You do have an advantage if you do support IE, and that is that you are more likely to get that business since others may not be supporting that browser. And there is also how much will it impact you to include ie support. It if is easy, just as well support IE. Depends on the tools you are using too.
Agreed. The biggest impact I'll have is JS code that's a bit bloated. It's not the end of the world, but say for instance... I use Babel a lot a lot. It runs and transpiles my TS and ESNext back down to ES5. For instance, to get something like a default parameter in IE11...
function test(x = "hello") {
// look ma, x has a default value
}Would end up like this...
function test(x) {
var x = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : "hello";
// look ma, x has a default value
}It's not the end of the world, but the more you do that and more stuff ads up. So, the site will be a bit slower for everyone because of IE... that 3% who won't upgrade.
Jeremy Falcon
-
40% of our customers are still on different versions of IE. They're a slow moving bunch. Apparently the average age of their computers are 7 years. Luckily I don't do front end stuff.
Wrong is evil and must be defeated. - Jeff Ello
Do you mind saying what your target audience is? For me, this is a retail site... which means I don't think I can drop IE11... but I want to.
Jeremy Falcon
-
See it this way: every web site looking broken in IE11 is another nail in it's coffin. If it's a pain to support, help kill it.
I really, really want to. It's already done for the most part (the site), but I do think this will be the last time I support it.
Jeremy Falcon
-
The relevant statistic is not the percentage of people using IE11 on the 'net, but the percentage of people using IE11 that visit your site(s). How about maintaining counter for the different browsers used to visit your site, and seeing whether IE11 is worth the effort to support? On future professional (== for pay) projects, I would quote two prices - one not including IE11 support, and one including it. I would also give the prospective client the latest IE11 usage statistics, and let them decide whether it is worth it.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
Agree 1,000% on that. I don't have those stats yet though as this site is brand new. Since the site is done for the most part, I may just let it run for a year or two and find that number out and then drop support for it if need be.
Jeremy Falcon
-
Do you mind saying what your target audience is? For me, this is a retail site... which means I don't think I can drop IE11... but I want to.
Jeremy Falcon
Car retailers and workshops make up the bulk.. IT knowledge varies quite a bit I have to say. Half the customers are using the newest and best, and the other half buys a new computer when the old one breaks.
Wrong is evil and must be defeated. - Jeff Ello
-
This is a more complex question that it may appear to be. What is the projected user base? Desktop, mobile, or both? Where are customers located? Industrial nations? Mobile will be using a "modern" OS -- what desktop OS are in play? Does your client have other commercial sites? If so, look at their stats for browser and OS. I found several stats sites that put IE as ~1.4% of the overall browser market, and ~5% for the desktop market. But that's overall -- these figures may not be accurate for YOUR market. What is the projected budget to develop and maintain the site for IE? If the budget is 10% of the total and the expected revenue from IE customers is 3%, supporting IE is counter-productive. My group made the decision to support the last 3 revs of the top 5 browsers + Edge. Costs are the driving factor, not only development time to support quirky browsers, but testing time to test that plethora of quirky browsers. We write current JavaScript and use Babble to transpile to support our planned user base, which also helps reduce dev & test costs. Why Edge? It's built into Windows so it's present for most of our user base. [Granted, the change to Chromium has eliminated a lot of testing.] That said, our site works on most modern browsers ... excepting IE (which is far from modern). YMMV
Well, it's not for a client per se... it's for my own company so I'd be the client. So, there are no other sites demanding the requirement. It's just 25 years of web development has taught me... people don't always upgrade. So, I need at least a base stat to start with.
BryanFazekas wrote:
these figures may not be accurate for YOUR market.
That's a good point. I have no idea what the figures are yet. Since the site is made to support IE11 I may just let it run for a couple years to find this info out... and drop support in two years if I get no customers using it.
BryanFazekas wrote:
What is the projected budget to develop and maintain the site for IE? If the budget is 10% of the total and the expected revenue from IE customers is 3%, supporting IE is counter-productive.
Very good point.
BryanFazekas wrote:
Why Edge? It's built into Windows so it's present for most of our user base. [Granted, the change to Chromium has eliminated a lot of testing.]
Agreed. Which is also the reason I'm still targeting IE11.
BryanFazekas wrote:
which is far from modern
I think we should all switch back to VBScript. :rolleyes:
Jeremy Falcon
