5 ms·
Yeah, this. ~95% of our usage is on chrome (our app is education so lots of chromebooks) and yet safari makes up 50% of the problems. The issues recently with
by jordanthoms 5y ago
Yeah, this. ~95% of our usage is on chrome (our app is education so lots of chromebooks) and yet safari makes up 50% of the problems.
The issues recently with localstorage being broken ( https://twitter.com/jaffathecake/status/1389493762129375232?lang=en https://twitter.com/jaffathecake/status/1389493762129375232?... ) have been particularly egregious, there's lots of users losing content on safari and we have to explain it's due to Apple breaking their browser (again).
- cudgy 5y agoWhat about your choice to use technology that you admit is broken? Or at least imply that Apple will break?
- ryandrake 5y agoWhat do your developers use as their "daily driver" browser? I bet it's Chrome. Reminds me of a decade ago, when IE6 was the bane of everyone's existence, yet no developer actually used IE6 regularly enough to catch bugs themselves. You've got to dogfood at least in proportion to your users. This also sounds a little like when application or game developers complain that some very high percentage of their bug reports come from Linux instead of Windows, but when you ask how many of their developers primarily develop and test on Linux, the answer is zero. Well, of course you're going to get most bugs on a platform not regularly used by the devs!
- jordanthoms 5y agoIt’s a mix of chrome and firefox, though also some safari to make sure we notice issues. What I’m talking about is obviously broken web apis ( another recent example: https://news.ycombinator.com/item?id=27509206 https://news.ycombinator.com/item?id=27509206 ), or missing features, not so much compatibility issues that would be explained by that. We have far fewer issues from Firefox for example, and certainly not major data loss bugs like those.