Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
bosi5083yWe had an similar discussion at work at the end of last year. In our case the pure numbers were enough. We have plenty of tracking at our sides (I'm not proud of this but in this case it helped us) and know how many users are still using ie. The number was so low that management agreed to drop the requirement that each feature must also work in ie11.
-
It's possible and most of the time it isn't a vulnerability in itself, therefore it's a valid requirement so long as they factor in the added complexity and effort. Whether it's a good financial decision is a question for management. If you still want to convince them to cut IE support, research how much money is spent on it (working hours) and present your findings along with browser usage statistics and trends. Make them understand that not only is IE support not paying for itself, it will only get ever less significant.
-
C0D4669023yOpen analytics, find IE usage vs Chrome/Edge/Firefox and tell them to justify the extra costs of supporting x users each month.
-
arekxv10523yJust keep saying that IE is a security risk for both user and your website which is technically true as it is no longer updated nowadays. There just comes a time when you have to cut the cord.
-
stop68023yNo:
- Security risks, due of active X
- adding unessary bloat for a few users
- new features are not supported. -
It is sad that the last good windows os (7) is being discouraged from being used as well. It worked and didn't get in your way, or rape your data.
Not saying IE is good or anything, but sometimes older shit doesn't suck as bad as newer shit.
Edgey I know. -
Actually it gave me an idea to simulate thousands of calls to a random website faking the client as IE, and make them worried about backwards compatibility. :D
Related Rants
Can PMs still reasonably require web apps to be compatible with Internet Explorer? Does the "you gotta to tailor to everyone’s needs" argument still stand nowadays? I ask this because I’ve been working on a client project for about two years now and last time they asked for IE compatibility was about a year ago. I’m preparing for the next time it absolutely stops functioning with IE to debunk their desire to remain stuck in the year 2003.
I know Microsoft simply isn’t supporting it anymore and are discouraging anyone from using it. I feel like it should be enough of an argument. However, often times enough isn’t enough. Anybody have any arguments or examples of why it’s a terrible idea to stick with it?
question
ie