Live data from Hacker News

Why iOS 13 and Catalina Are So Buggy

tidbits.com

221–230 of 368 posts

Re: Why iOS 13 and Catalina Are So Buggy

#221

Earlier quoted context omitted.

> "Docker for Mac" is actually a Linux kernel running inside a hyperkit/xhyve VM, and uses Linux's container support. This is indeed correct. Your Docker VM lives at: /Users/$USERNAME/Library/Containers/com.docker.docker/Data/vms/0/Docker.raw It would be very nice to be able to use libvirt from my Mac in the same way as my Linux workstation. Or be able to migrate VMs between the two. They're both using the same-ish C…

It would be very nice to be able to use libvirt from my Mac in the same way as my Linux workstation. I believe libvirt as such is supposed to work on macOS. Furthermore, recent versions of Qemu apparently support using macOS's Hypervisor.framework. So it seems like this should be doable, although I've not had a chance to try it myself yet.

Cool, thank you for the info. It's been a while since I tried it.

Re: Why iOS 13 and Catalina Are So Buggy

#222

Earlier quoted context omitted.

I was just speaking with an acquaintance at Apple this weekend that works in a group in this area at Apple, and they pretty much said exactly what you just said. Also, it doesn’t help that they can’t directly benefit from the general progress the industry is making in virtualization and container areas without rewriting for their own platform.

> Also, it doesn’t help that they can’t directly benefit from the general progress the industry is making in virtualization and container areas without rewriting for their own platform. Can you expand on this? Are there limitations on MacOS that prevents them from doing so?

Aside from the software side, the licensing also heavily restricts virtualisation - if Apple would just /permit/ it, I know of several companies (not to mention open source groups) who would /love/ to create some industrial-scale iOS/OSX testing tools - right now they're limited to "duct tape a bunch of iPhones plugged into old-gen mac minis into a rack" and that's an absolute nightmare to manage...

Re: Why iOS 13 and Catalina Are So Buggy

#223
post #169
post #162

Earlier quoted context omitted.

You are writing this based on gut feeling, big companies simply can't go over every bug report- it's not scalable. I used to work on a product at a big company, we took users input very seriously, not only from bug reports but also by analyzing telemetrics data and simple users "star" feedback. At the end of the day it's simply impossible to both fix everything and still go forward when the product is big and complex…

Does the Chrome team go over every bug report? It seems like it to me, though I've only filed a few.

They also ignore bugs for a decade or more.

Re: Why iOS 13 and Catalina Are So Buggy

#224
post #161

Earlier quoted context omitted.

Did they not use 2000? Or XP? Or even 7 for that matter?

I've used Windows on and off since 3.11, and have used 98, xp, 7 and 10 a lot. As much fun as it is to hate on Windows, if I'm honest with myself 10 has been the most stable experience I've had with Windows, with the possible exception of 3.11 (though that was a long time ago).

It’s not like there was anything to do in Win3.11 other than Word, mspaint, Solitaire, and writing funny messages in the marquee screensaver

Re: Why iOS 13 and Catalina Are So Buggy

#225

That doesn't make sense. None of this has changed from previous updates and all previous macOS updates were far more stable than this one. This isn't a particularly feature laden update either. But now all of a sudden we get catastrophic (deleted emails) and less catastrophic (missing Music playlists) data loss, crash bugs and generally weird behaviour of many apps. I have identified one particular area where bugs ar…

Shortcuts are another feature where they changed the format and anything that syncs back to an iOS 12 device becomes nonfunctional

Another bad piece of this release is that iOS and iPadOS were staggered: iOS 13 came out on September 19th and iPadOS on the 24th. Even if all of your devices were new enough to update, the iPad didn't have a compatible release for the better part of a week, so a bunch of features were broken.

Re: Why iOS 13 and Catalina Are So Buggy

#226
post #142

Macos used to not have a yearly schedule. New versions took the time they needed. I think it's actually a better model, it allows engineers the time to test and make sure things work. Having arbitrary deadlines just increases the amount of crunch time which usually increases the amount of bugs. Other than that, I wish that Apple did another Snow Leopard and focused for one year purely on fixing bugs in macos x instea…

Although I like looking forward to the next macOS name unveiling and seeing new themed wallpapers, I think operating systems should get a regular stream of small updates for individual features and builtin apps, instead of monolithic yearly releases branded as distinct products. As for API sets, SDKs and third-party app compatibility, they could still be tied to yearly milestones, e.g. "macOS 2020 January", so there…

Exactly, a long time between releases pushes teams to get their feature into this release even if just 90% ready. If the Mail.app team could ship updates not just annually, I’m sure they’d make faster progress and ship more stable releases.

Re: Why iOS 13 and Catalina Are So Buggy

#227
post #5

I can only surmise (hope) that their resources are diverted towards Something Big. Could be ARM macOS and/or AR glasses. Not that this excuses the bugginess of their current core products. Bringing up comparisons to Steve Jobs must be the tech equivalent of Godwin's Law, but if there was one thing about him, it's that he actually was a user of his own products, like us. It feels like there's no one at Apple (or other…

With their culture, something big will be worked on by a relatively small team in total secrecy. The team, in name of secrecy, will repeat the same mistakes that some other teams are fixing elsewhere.

Norbert Wiener pointed this out 60 years ago, re: US military secrecy during WWII.

Re: Why iOS 13 and Catalina Are So Buggy

#228
post #200

Earlier quoted context omitted.

If Apple spent more than $11 dollars on documentation they also might not be in the situation they're currently in. So much of what happened in Catalina is just flat out not written down in the Developer Documentation. Apple's documentation has been waning for a while, but it's fallen off a cliff in the last eighteen months. It's impossible to believe that's not having an impact on external software quality, and it's…

I remember doing my first hackintosh, due to an attempt at a startup where we wanted to have a iOS and OSX client. The documentation blew me away, nicely packaged with XCode, and made it really look like a platform that would care about developers, especially given how niche it was. That was 10.6 time. Currently, I have a Mac forced on me by company. I look at docs... and they are the same docs I remember, with bits…

There are a surprising amount of Catalyst API documents that literally just have the function name and no description of what it does and an empty page.

Re: Why iOS 13 and Catalina Are So Buggy

#229
post #71

The only iOS 13 bugs I’ve been bitten by are: 1. Safari’s back button now seems to lose the position on the previous page - sometimes. 2. The share sheet has a row of Messages contacts that I didn’t ask for, don’t want, and can’t turn off - and it creates the risk of super-inappropriate sharing, because all my work contacts are eligible for being on this row, seemingly at random.

I completely agree with point 2, and I have already accidentally shared a hacker news story to a work colleague without intending to! I can’t understand why there is no option to remove it.

[deleted]

Re: Why iOS 13 and Catalina Are So Buggy

#230
post #200

Earlier quoted context omitted.

I remember doing my first hackintosh, due to an attempt at a startup where we wanted to have a iOS and OSX client. The documentation blew me away, nicely packaged with XCode, and made it really look like a platform that would care about developers, especially given how niche it was. That was 10.6 time. Currently, I have a Mac forced on me by company. I look at docs... and they are the same docs I remember, with bits…

This boggles my mind. My flabber is ghasted. Documentation is of paramount importance! How else will people build an ecosystem around your software if they can't figure out how to use it in a variety of ways? I really hope this isn't some trend of just abandoning the commons, taking without adding back in.

I think the point is to get the average beginner dev frustrated and not make macos apps. They've been pruning the platform slowly but surely for quite some time now

ipad seems to be their focus for "pro" stuff now. Now that iPad apps can run on macos i think that's a clear sign that if you want to make a macos app - don't bother, make an ipad app

Post reply on HN