View Single Post
Old 28-05-2020, 13:19   #6
Kushan
FORMER Virgin Media Staff
 
Join Date: Dec 2010
Location: Warrington
Posts: 4,737
Kushan has a bronzed appealKushan has a bronzed appeal
Kushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appeal
Re: Website Unsafe Message (Microsoft Browsers)

Quote:
Originally Posted by Dude111 View Post
People really suck................ THEY MAKE THINGS HARDER FOR PEOPLE FOR NO REASON!!!!!
No, there's perfectly good reasons for doing this: Old browsers are insecure. They are insecure for you, the user and insecure for the sites you're visiting.

There's also a huge cost to supporting older browsers you don't seem to appreciate. If you want to add a new feature to your website, it's easy enough to do - usually there'll be a library that already does it, you just drop it on and away you go - except it'll not work on every browser out of the box, you'll need to test it and tweak it so it works on all sorts - Chrome, Firefox, Edge, IE (maybe), Safari, their mobile equivalents, there's nearly 10 different permutations to test and we're not even talking about older versions yet. Want to test the latest and the previous releases of those? Now you've got 20 permutations. This doesn't include some of the more obscure browsers out there, either.

But wait, what about different Operating systems? Let's not forget Windows and MacOS, so now it's more like 25-30. Now you want us to test on a really old version of whatever it is you're using? How many permutations is that? 50? 100? If you're lucky enough to have a QA department, you're now spending most of your QA budget checking browsers that a single-digit number of people are using. Thousands of £ a year to keep a few people happy.

And the truth is, the reason things only work on newer browsers is because those newer browsers add functionality to make it easier to build web features, things that would take a developer a week to do can be done in a single line - but not all browsers support all features equally.

But what do you do when most browsers support something, but a slightly older one does not? Maybe you wait, or maybe you pay a developer a week's salary to implement it. But if that older one is a couple of years old and used by one or two people? You draw the line, you ask those people to upgrade, you stop testing for it and you move on - because the cost of upkeep is not worth it. The cost of testing is not worth it.

So no, it's not "for no good reason", it's for plenty of good reason.

The web is a constantly shifting, moving and evolving platform. Move with it, or get left behind.
Kushan is offline   Reply With Quote