I wish I had thought of sneaking in a scary banner in ~2013 when I still had to support IE6 for a web development job I had.
I, like a majority of web developers, was using Chrome to do all my development and testing, and would only occasionally VM Windows XP to test Internet Explorer, which usually had something broken, and would usually end up with me spending a majority of my time fixing, and when I would complain about it, management would point to the server logs and say "Look, N% of people are still using IE6, we have to support it!" If I had been smart enough to put a little deprecation warning on there, life might have been easier for me.
I’ve replied elsewhere in how I reported the support overhead for older browser versions.
While one could fudge numbers once, we could get accustomed to misrepresenting in the future too. Once users/customers discover this, they’ll always keep second-guessing us. Trust once lost would be difficult to regain. It is better to how customers that they need not waste money anymore and shouldn’t support/facilitate users using insecure and outdated technology anymore either. They could give it a positive spin and get good PR too.
This is terrible advice. Taking a bold gamble without total authorization can pay off sometimes... lying to management is how you get fired (at best) or sued.
I, like a majority of web developers, was using Chrome to do all my development and testing, and would only occasionally VM Windows XP to test Internet Explorer, which usually had something broken, and would usually end up with me spending a majority of my time fixing, and when I would complain about it, management would point to the server logs and say "Look, N% of people are still using IE6, we have to support it!" If I had been smart enough to put a little deprecation warning on there, life might have been easier for me.