5 ms·
Interestingly, with a few exceptions (looking at you, Xcode), stuff barely ever crashes anymore in my experience. Instead the issues are a lot more frustrating
by deergomoo 7y ago
Interestingly, with a few exceptions (looking at you, Xcode), stuff barely ever crashes anymore in my experience.
Instead the issues are a lot more frustrating: failure states where no indication of failure is provided (other than what you’re trying to accomplish isn’t happening), no reason is given, and no means to try again is available.
It’s become even worse now that most things have some sort of web sync aspect. You’re just left turning things off and on in different combinations, in the vague hope that you can reset some piece of state somewhere.
- JMTQp8lwXL 7y agoA hard crash would be preferable to the failure states encountered, mostly because it leads to quicker resolution. For example, when the camera stops working, the first time I tried opening & closing the app numerous times. (Didn't fix the problem). Then I eventually restarted. It probably took me 10 minutes to figure it out. An immediate crash & reboot would take less time. If their OKR's state to reduce number of hard crashes, congratulations, they did. Doesn't mean they delivered on product quality, however.
- deleted 7y ago[deleted]