5 ms·
While the point may be true, it's like don't drive a car because people do die in car accidents. The post is misleading as most of the cards present rare edge c
by zupa-hu 12y ago
While the point may be true, it's like don't drive a car because people do die in car accidents.
The post is misleading as most of the cards present rare edge cases where JS doesn't work. Show percentages as well.
Yes JS may not work 0.1% of the time. So let's fix it once all the higher priority issues are fixed.
- ant6n 12y agoThe comparison is not very good. There are plenty of arguments around not driving cars; safety is a valid concern.
- pharke 12y agoThat's in the same ballpark as saying there are plenty of reasons to not use fossil fuels or there are plenty of reasons to not use English as a lingua franca or plenty of reasons to not eat meat. There are lots of good reasons to not do any of those things but until you come up with a universally acceptable alternative and convince the majority of people to adopt it, you're shit out of luck.
- ant6n 11y agoAll three examples strike me as America centric.
- zupa-hu 12y agoxD
- M2Ys4U 12y agoYou're underestimating how often JS doesn't work by an order of magnitude. According to the UK GDS JS doesn't work for up to 1.1% of users.
- anc84 12y agoAre those human users or dumb bots?
- zupa-hu 12y agoWoohoo, an entire percent. There are 2 interpretations of the situation. Either that 1.1% is a totally pressing issue and almost the entire industry is an idiot for not getting it; or the industry is actually pretty smart and also market forces do their work and it turns out it's not as a pressing issue relative to other things. I like to subscribe to the second idea.
- anc84 11y agoAccessibility for 1% can be a pressing issue if you consider your site/service as something important and you do not want to keep disabled users out. Just as food for thought. Letting the market force people away is not very social.