5 ms·
Empathy and accessibility. Does it make sense to have a ramp in front of your shop for < 5% customers?
by cryptonym 1y ago
Empathy and accessibility. Does it make sense to have a ramp in front of your shop for < 5% customers?
- nchmy 1y agoMy 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"
- littlestymaar 1y agoIt'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.
- nchmy 1y agoThere's plenty of other chromium browsers - Vivaldi seems to do a good job in this regard. Also, Firefox exists, though they don't seem to care about privacy much anymore either. And, of course, safari, which is terrible in most regards
- littlestymaar 1y ago> There's plenty of other chromium browsers - Vivaldi seems to do a good job in this regard. Being chromium derivatives, they don't really have a say in what's included in “their” browser though. > Also, Firefox exists Well, you disregarded is as “arcane browser” right above.
- nchmy 1y agoIn what way did I call Firefox arcane? Firefox generally has better support for web features than safari.
- littlestymaar 1y agoIt has less than 5% market share left…
- nchmy 1y agoit is included in Baseline and passes more tests than safari, so i would hardly call it arcane
- littlestymaar 1y agoYet people treat it as such and drop support. Remember this is the comment you argued in favor above: https://news.ycombinator.com/item?id=45590086 https://news.ycombinator.com/item?id=45590086 > 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.
- cryptonym 1y agoGrandma or poor folk with their old device may not be "largely a choice"
- nchmy 1y agoDon'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).
- todotask2 1y agoIt 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.
- nchmy 1y agoYeah, 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.
- cryptonym 1y agoShould we build SPA given it's poorly accessible and provide bad performance? Tried old school SSR? Even on modern devices, it's waaaayy faster and much more enjoyable than JavaScript bloated "modern" website.