Live data from Hacker News

Why iOS 13 and Catalina Are So Buggy

tidbits.com

201–210 of 368 posts

Re: Why iOS 13 and Catalina Are So Buggy

#201
post #104

I have a slightly different take on this. I think every company should dedicate a certain percentage of their revenue to handling bug reports from users. Yes, many bug reports will be bogus, but many will be pure gold (I speak from experience). Yes, it involves a lot of manual work. But it is so incredibly worth it — you get to catch the odd bugs that you will never catch with automated or in-house testing. In contra…

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…

The quality of the original "Inside Macintosh" books was the main reason I started programming on the Mac back in the day, and lost interest in the Amiga.

Re: Why iOS 13 and Catalina Are So Buggy

#202
post #104

I have a slightly different take on this. I think every company should dedicate a certain percentage of their revenue to handling bug reports from users. Yes, many bug reports will be bogus, but many will be pure gold (I speak from experience). Yes, it involves a lot of manual work. But it is so incredibly worth it — you get to catch the odd bugs that you will never catch with automated or in-house testing. In contra…

Just a not that there is a way to get a bug report filed - call support, get the issue escalated because its not fixed, if they cant fix it it will go to engineering.

I have personally witnessed hundreds of support cases go through this various process, in some cases taking months of work (for communication mostly from eng to customer) of T2 support reps.

Now - is their current spend sufficient? Probably not, but Apple consistently ranks among the highest customer service ratings - so they probably think spending more here is a waste of time.

Re: Why iOS 13 and Catalina Are So Buggy

#203
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…

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.

Re: Why iOS 13 and Catalina Are So Buggy

#204

Apple stores are highly tuned to and responsive to customer experience in-store. The same is true with their AppleCare support online and via phone. The metric they focus on is Net Promoter Score. Maybe this same model could be applied to the OS, Apps and services. Apple user experience would be improved methinks.

As someone described, Jobs focused heavily on the sale experience - anything after that, unless someone (or his own experience with his product) convinced him, was irrelevant.

The moment your money parted with you, your importance ended. This was visible, among other things, in gutting departments that kept Apple alive when literally everyone else had better hw & sw - people who did long-term accounts with for example government customers, specific market areas, etc.

Re: Why iOS 13 and Catalina Are So Buggy

#205
post #166
post #164

Earlier quoted context omitted.

I use WhatsApp for 99% of my messaging. I’d be happy with the new share sheet row if it could be configured to show me my common WhatsApp contacts. But because it’s Messages only, it only shows people I very very rarely want to contact.

It’s not Messages only, WhatsApp just hasn’t implemented it yet.

When WhatsApp get round to implementing it, will I be able to turn it off for messages?

Re: Why iOS 13 and Catalina Are So Buggy

#206

Earlier quoted context omitted.

> 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?

The macOS kernel (XNU) does not have any kind of containerisation support. I believe "Docker for Mac" is actually a Linux kernel running inside a hyperkit/xhyve VM, and uses Linux's container support. Apple hasn't put much public effort into making macOS work well inside a virtual machine. Recent versions in particular, where the window compositor uses Metal for drawing, don't run well. Apple hasn't opened the API fo…

> "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 CPUs, after all! (Workstation has a "i7-5820K" vs the Macbook Pro's "i7-8850H")

Re: Why iOS 13 and Catalina Are So Buggy

#207
post #104

I have a slightly different take on this. I think every company should dedicate a certain percentage of their revenue to handling bug reports from users. Yes, many bug reports will be bogus, but many will be pure gold (I speak from experience). Yes, it involves a lot of manual work. But it is so incredibly worth it — you get to catch the odd bugs that you will never catch with automated or in-house testing. In contra…

> If Apple also spent 10% of its revenue on processing bug reports and fixing bugs

Just to be clear, you're suggesting they dedicate $25B/year to bug fixing? Seems high, given their total R&D budget for 2018 was only ~56% of that.

https://www.macrumors.com/2018/11/05/apple-2018-form-10-k-hi...

Re: Why iOS 13 and Catalina Are So Buggy

#208
post #102

I have been told by multiple sources that Apple engineering salaries are not competitive with industry leaders and haven't been for a long time. I wonder if the dissolution of the Jobs anti compete agreements exacerbated the issue. However Apple seems to be willing to pay for highly sought after skills. I have also been told that they don't have company level hiring standards so you should expect uneven abilities acr…

They need to unionize. The company they work for has 60 Billion in profit!!!

Re: Why iOS 13 and Catalina Are So Buggy

#210
post #183

Earlier quoted context omitted.

This seems pretty far removed from most other people's experiences.

Which is why I was asking if there was any kind of quality study / survey / anything better than opinions around this, because as you say the anecdotes in my anecdote arsenal seem to be quite a bit different from other folk (or at least other highly verbal folk) on the internet.

I agree with you SCdF. Win 10 has been the most reliable Windows for me since 3.11, except maybe late-stage XP when all the worst bugs had worked out. I think it’s always the case that people that have bad experiences are going to be vocal, because you don’t go around talking about “oh hey, everything worked normally today.”

The deletion bug WAS pretty bad, but it also affected a VERY tiny group within the subset of users that had opted in to experimental/advanced-preview updates.

Post reply on HN