Earlier quoted context omitted.
It's not a beta, it's what they encourage their users to upgrade to
I know. I’m talking about iOS 13 beta 1. If you think this is what a bad OS looks like, you should try that.
iOS 12 beta 1 was a lot better, FWIW.
Why iOS 13 and Catalina Are So Buggy
51–60 of 368 posts
Re: Why iOS 13 and Catalina Are So Buggy
#52[deleted]
Re: Why iOS 13 and Catalina Are So Buggy
#53The way I've heard one company deal with noticing non-crashing bugs is to treat warning logs as 'crashes' with backtrace snapshots and upload them as specially tagged non-fatal crashes. Might help apple see if clients are having specific icloud issues.
This seems like a really good idea to me. Is it possible to do in a way that preserves privacy and doesn’t basically become a hidden “telemetry” system?
Make it opt-in and require a privacy review every time something like this goes in?
Re: Why iOS 13 and Catalina Are So Buggy
#54The way I've heard one company deal with noticing non-crashing bugs is to treat warning logs as 'crashes' with backtrace snapshots and upload them as specially tagged non-fatal crashes. Might help apple see if clients are having specific icloud issues.
This seems like a really good idea to me. Is it possible to do in a way that preserves privacy and doesn’t basically become a hidden “telemetry” system?
Well it would have the same permissions as crash reports in general? It uploads the same amount of info as normal crashes right?
Most apps send analytics up already if you are not already aware, most don't ask for your permission to do so.
Re: Why iOS 13 and Catalina Are So Buggy
#55Tangentially related: GitHub has already dropped support for Mojave. The whole site is now broken in Safari 12 because it’s no longer the “current” version of the browser. Well, it is if you run Mojave, as you need to upgrade the entire system to get Safari 13.
I can understand not developing new features for Safari 12, but speaking of regressions, why would you go break things that used to work a week ago?
Re: Why iOS 13 and Catalina Are So Buggy
#56I have a theory that this year tons of stuff was rewritten in Swift, because with the lockdown of the ABI it's now possible to write libraries in Swift. This might be why this year is a bumper crop of bugs.
Very little has been rewritten in Swift.
Really? I read otherwise: https://blog.timac.org/2019/0926-state-of-swift-ios13/
It'd be hard to know unless you worked there. It's just a wild theory, I might be wrong :)
Re: Why iOS 13 and Catalina Are So Buggy
#57As a VoiceOver user, I can provide a lesser known perspective. I've gotten used to waiting several months until I actually install a new major release. With the exception of iOS 12, basically all releases since iOS 5 were quite buggy when it comes to apples screen reader VoiceOver. Luckily, applevis.com these days publishes a list of known problems with accessibility on iOS a few days before every major release. So t…
> their accessibility stack is still lightyears before Android. Don't you mean "ahead of"?
That’s what that means, “before” being the opposite of “behind”. It’s just not as common a construction in most English locales as it used to be. It does still get more restricted usage in this sense: when considering the future, “this is what lies before us” wouldn’t sound out of place.
Re: Why iOS 13 and Catalina Are So Buggy
#58Tangentially related: GitHub has already dropped support for Mojave. The whole site is now broken in Safari 12 because it’s no longer the “current” version of the browser. Well, it is if you run Mojave, as you need to upgrade the entire system to get Safari 13. I can understand not developing new features for Safari 12, but speaking of regressions, why would you go break things that used to work a week ago?
I agree that's a rather aggressive schedule for support, but I'm running Mojave 10.14.6 (18G103) and Safari Version 13.0.2 (14608.2.40.1.2) right now.
Re: Why iOS 13 and Catalina Are So Buggy
#59Earlier quoted context omitted.
Very little has been rewritten in Swift.
Really? I read otherwise: https://blog.timac.org/2019/0926-state-of-swift-ios13/ It'd be hard to know unless you worked there. It's just a wild theory, I might be wrong :)
That's a very small fraction of the binaries that ship in the OS.
Re: Why iOS 13 and Catalina Are So Buggy
#60Tangentially related: GitHub has already dropped support for Mojave. The whole site is now broken in Safari 12 because it’s no longer the “current” version of the browser. Well, it is if you run Mojave, as you need to upgrade the entire system to get Safari 13. I can understand not developing new features for Safari 12, but speaking of regressions, why would you go break things that used to work a week ago?
[deleted]