IE9 support is already in a sad state. Many new websites already look in IE9 as bad as in IE6. Chrome should spawns less processes (hold some more tabs in one process). IE spawns less processes than Chrome and therefor is less of a memory hog. Firefox finally needs a proper multi-process implementation. Even the latest Developer edition just uses two processes (firefox.exe and plugin-container.exe) - I just tried it…
This is party time; Internet Explorer 8, 9 and 10 die on Tuesday
51–60 of 177 posts
Re: This is party time; Internet Explorer 8, 9 and 10 die on Tuesday
#52I don't understand why Microsoft divides its browsers this way. They seem to be the only one that actually has versions, and [security] updates within a version. Instead just have a single browser (instead of 5 or more counting from IE6) and any update increments the version. Both Firefox and Chrome work this way. They would have to allow installing the latest version of IE on any machine all the way back to XP, but…
I don't think they can. IE's (since IE5) is not your usual standalone browser application - it's an operating system component, that's used in a lot of places, starting right from the desktop. Tighter integration and mutual OS-browser dependence means it's not as easy as saying "ok, let's allow IE10 to run on Vista".
Re: This is party time; Internet Explorer 8, 9 and 10 die on Tuesday
#53It will be a while still before you can actually party. As long as a measurable percentage of your users are still on these browsers, you're missing out on money of you don't support them.
Re: This is party time; Internet Explorer 8, 9 and 10 die on Tuesday
#54Earlier quoted context omitted.
Yes it does. They could ship a statically-linked copy of Edge to Windows Vista (and even XP) users via Windows Update. The old IE DLLs would have to stay there to be used by the system, but the actual web browser could be a newer one.
That's a terrible idea from a security standpoint.
Re: This is party time; Internet Explorer 8, 9 and 10 die on Tuesday
#55Earlier quoted context omitted.
Firefox probably won't help with non-browser software, if that's what the parent comment was referring to. I also have to develop an app for a client for XP because of some proprietary hardware that still doesn't have a Windows 7/8/10 driver.
Yes this is my problem. The hardware manufacturer does not want to support upgrades (they want to sell new hardware) and so I am stuck supporting XP. In my situation there is not even hardware the customer can upgrade to as the original hardware supplier has left the market. We are all stuck with XP until something catastrophic happens.
Re: This is party time; Internet Explorer 8, 9 and 10 die on Tuesday
#56Earlier quoted context omitted.
Really? I know that would be easier for developers, but think about it from a "it's my computer" point of view - do you really want people doing that to you? It's your computer, you should be able to to run whatever software you like. A reminder to upgrade, OK, that's fine. But actually disabling? You go too far.
I laughed a little bit imagining a user yelling out "it's my computer!" and actually believing they should have full, absolute control over anything it does... while running a Microsoft operating system.
Re: This is party time; Internet Explorer 8, 9 and 10 die on Tuesday
#57Oh poor, deluded TNW. Software only dies in the way developers care about when users stop using it. Well beside its actual expiry (which seems to be 2020), people STILL use XP with an ancient versions of IE6 and IE7. Many Vista users stick on IE7. So calm yourself and put flexbox back down. You've got a few years before that's supported enough.
If I was a developer, I'd carefully look at my referer logs and if only 15% of my user community was using IE 8-10, I'd just develop for IE 10. I would NOT warn the end users about needing to upgrade, I'd just let script errors occur and not release any compatibility fixes. I'd respond to support tickets explaining that there are bugs in their old version of IE and suggest they upgrade, or install Chrome or Firefox.…
> I would NOT warn the end users about needing to upgrade
People using your product are discussing it on review sites, on social media, with friends/family, etc.. If you silently give some of them a broken product, a few will contact support; but I imagine most will assume your product is just low quality. So that's the word they'll spread.
For corporate users: well, you'd need to talk with your customers. They might be facing a seriously expensive upgrade process, and could be extremely unhappy to hear you're setting an arbitrary deadline for them.
Re: This is party time; Internet Explorer 8, 9 and 10 die on Tuesday
#58Oh poor, deluded TNW. Software only dies in the way developers care about when users stop using it. Well beside its actual expiry (which seems to be 2020), people STILL use XP with an ancient versions of IE6 and IE7. Many Vista users stick on IE7. So calm yourself and put flexbox back down. You've got a few years before that's supported enough.
If I was a developer, I'd carefully look at my referer logs and if only 15% of my user community was using IE 8-10, I'd just develop for IE 10. I would NOT warn the end users about needing to upgrade, I'd just let script errors occur and not release any compatibility fixes. I'd respond to support tickets explaining that there are bugs in their old version of IE and suggest they upgrade, or install Chrome or Firefox.…
Are you really willing to take a 10% hit on sales?
You can announce EOLs until the cows come home (Microsoft has and look how well it has done them). If your product stops working, they'll complain at you and then cancel their contract and find another provider who will support them.
I'm speaking from a gruelling 15 years experience developing enterprise SaaS. We've only just dropped IE6. It'll be years before IE8 goes away.
Re: This is party time; Internet Explorer 8, 9 and 10 die on Tuesday
#59Earlier quoted context omitted.
If I was a developer, I'd carefully look at my referer logs and if only 15% of my user community was using IE 8-10, I'd just develop for IE 10. I would NOT warn the end users about needing to upgrade, I'd just let script errors occur and not release any compatibility fixes. I'd respond to support tickets explaining that there are bugs in their old version of IE and suggest they upgrade, or install Chrome or Firefox.…
It's easy to say this stuff, less easy to implement in a business. It depends on your demographic and your content. Take B2B sales or B2B SaaS. Enterprise users are THE main reason for crappy old browsers in my experience, so the real question becomes... Are you really willing to take a 10% hit on sales? You can announce EOLs until the cows come home (Microsoft has and look how well it has done them). If your product…
Re: This is party time; Internet Explorer 8, 9 and 10 die on Tuesday
#60Oh poor, deluded TNW. Software only dies in the way developers care about when users stop using it. Well beside its actual expiry (which seems to be 2020), people STILL use XP with an ancient versions of IE6 and IE7. Many Vista users stick on IE7. So calm yourself and put flexbox back down. You've got a few years before that's supported enough.
If I was a developer, I'd carefully look at my referer logs and if only 15% of my user community was using IE 8-10, I'd just develop for IE 10. I would NOT warn the end users about needing to upgrade, I'd just let script errors occur and not release any compatibility fixes. I'd respond to support tickets explaining that there are bugs in their old version of IE and suggest they upgrade, or install Chrome or Firefox.…