IT only pushes back because the business users who use old web apps push back. Gotta make sure that IT knows the MSFT no longer has their back and so they need to be more aggressive with the business users and their app vendors.
EDIT: I mean, I understand if you want to be able to keep using a JS/CSS framework, but it's not really reasonable to ask for upstreams to keep supporting such marginal systems.
I swear there are bank machines in the field still running Windows XP. It's truly astonishing.
The old browsers are presumably (according to that page) still getting security updates by Microsoft, so I'm not what you're arguing. (Either way, if the browsers are not getting security updates, that's on Microsoft, not on upstreams.)
Can you explain what you mean?
EDIT: Hopefully to clarify what I'm puzzled about: How is having to use an old Bootstrap a security issue?
So it seems it's pretty safe to remove support for it.
Source: https://analytics.wikimedia.org/dashboards/browsers/#all-sit...
But if you're B2B then, you're not selling to that 1%, you're selling to a range of companies.
So 1% of end users having IE9 translates to 10% of your customers having (some) users with IE9.
Sometimes you're not even selling to companies, you're selling to partners or resellers selling to companies, so now that 10% of companies translates to 60% of your partners / resellers having (some) companies which themselves have (some) users with IE9.
So what was 1% of users can translate to much more than 1% of revenue lost just by dropping support.
And that's before I get started on how general those analytics are rather than breaking it down to office workers during work. Again, if your business is selling SaaS that targets workers then you'll likely come across a client with a need for older IE support sooner rather than later.
There's another reason why B2C is fine to drop support:
People are resourceful, if you have a website which breaks in IE9 then they'll probably just switch to chrome and it'll work fine if it's something they really want.
Companies however tend to be less flexible, if they know they have IE9 installed they'll insist on having "IE9 support" in the acceptance criteria, even if it's only installed on a few machines which likely will never be used with your software.
I'm actually happy to see bootstrap, jquery etc drop IE9 support because it makes it much easier during negotiation to drop support and push back against such proposals.
IE9 is still in extended support until April due to the fact it's the most recent IE that can run on Vista, and Vista is still in extended support until April 11.
In fact – and I too am not a lawyer, so don't consider this actionable advice – you might do well to throw up a warning, if not altogether disable access, to whatever product it is your users are accessing on XP, just to make sure you have all your HIPAA bases covered.
Everyone interprets HIPAA differently and based on a statement like: "Continuing to use Windows XP after 4/8/14 (or other unsupported operating systems) becomes a HIPAA violation if it’s not addressed in your security risk analysis[0]." You can run XP indefinitely as long as your IT says it's OK and they've "secured it properly." However, if they do get hacked or whatnot, they can get a fine if their security analysis wasn't good enough.
I don't recommend it. I actually despise it and try my hardest to get people to drop it. But in the end, I've had to deal with a lot of XP running IE8 systems that need connections to the software I'm in charge of. There's nothing I can do unless I get rid of those users and most of the time I can't because I have to "support modern browsers" as noted in the contract and the contract is with the state, not the individual users. Yes, the contracts will get updated to be more specific, but most of the contracts are on 5 year cycles.
State .gov contract work is amazing. /s
[0] https://pimsyehr.com/resources/compliance/hippa-compliance/2...