My question, though, is who are the 5% of users in this case who are using some arcane browsers? Surely that's largely a choice, physical disabilities are not.
It doesn't seem unreasonable to say to those folks "were evidently not using the same web"
It's not comparable to a physical disability byt gatekeeping the people who just don't want to be tracked all day by Google doesn't sounds right to me though.
> From business perspective it makes a lot of sense to just drop that bottom 5%. Actually, many businesses support Chrome only, they don't even support Firefox.
Don't major browsers essentially auto update? And to the extent that a device is so old that it can't support newer versions, surely it must be VERY old and perhaps is somewhat likely to be replaced sooner than later.
I think I'll probably carry on with not supporting browsers that don't have Sec-Fetch-Site. The alternative, Csrf tokens, actually causes me immense issues (they make caching very difficult, if not impossible).
(and I say all of this as someone who is specifically building something for the poorest folks. I'm extremely aware of and empathetic to their situation).
It still depends on the target audience. Some websites or apps are single-page applications (SPAs), can older devices handle that? For example, my mum’s Android phone was too slow to even load a page.
Secondly, users should upgrade their devices to stay safe online, since vulnerabile people are often scammed or tricked into downloading apps that contain malware.
So we should not cater to outdated browsers when they could pose a risk.
Yeah, I'm very amenable to this take. WordPress, for example, is infamous for having extreme backwards compatibility. But that often results in many sites being on ancient versions of php (and surely other tech as well). I'm of the opinion that they should all be running currently-supported versions of php and everything else. If you can't use my plugin because your server is shit, so be it.
It’s not “digital cash”, there is no such thing as “digital cash.” It’s an account that a person has with a bank that’s intended for routine transactions, so it’s closer to a checking account than physical cash.
Soon current version of the toy will be deemed unsafe and start catching fire. You'll have to get a new version of the toy, still available easily but it'll only run on crazy expensive batteries you can get from Vicky. Or you could try to build your own batteries but specifications for those are hazardous, undocumented and changes over time.
Also, for the new version of the toy you'll have to learn to play a new game as the old way to play with it'll become half-working.
Website can't provide notification on iOS. You may find workaround but that would be either expensive or under Apple's control. This use-case without notifications is quite useless.
I know two people who have been scammed by ads pushed on Instagram. One for a fake sell of clothes and another for fake reselling of concert ticket. In both instances, price of that scam was worth multiple years of subscription.
CDN (can't say specifically about Cloudflare but that's true for other) may allow picking faster routes than BGP (BGP tends to optimize cost rather than perf), sometimes better compression than Origin on the path, and fast handshakes at Edge with already hot connections towards Origin.
Edgecomputing can also help accelerating dynamic content.
reply