4 ms·
I'm genuinely curious, does anyone here know if there's an underlying framework issue behind so many iOS bugs? Because in my experience so many bugs seem to ha
by crazygringo 7y ago
I'm genuinely curious, does anyone here know if there's an underlying framework issue behind so many iOS bugs?
Because in my experience so many bugs seem to have something to do with some kind of underlying data or sync model (not even remote sync, just on the device itself).
E.g. half the time I delete a voice memo, it re-appears 10 seconds later. Or maybe a quarter of the time I send an e-mail from the "Share" button in an app, it shows up as an unsent draft when I switch to my Mail app (despite the fact the e-mail was actually sent). Or sidebar shortcuts to folders I create in the Files app gradually and randomly disappear over the course of days/weeks.
It's like there's some funky async stuff going on behind the scenes, where either a common library has flaws or race conditions that seem to pop up everywhere, or it's so hard to use the library correctly that even the internal teams which program the apps are making mistakes with it.
- eddieh 7y agoI can't speak to the specifics, but after working on a significant third-party SDK for iOS I can say that libdispatch isn't hard to use correctly, but it is easy to use incorrectly. Worse still, once you get yourself into a libdispatch mess it is hard to escape without a total rewrite.