Live data from Hacker News

Why iOS 13 and Catalina Are So Buggy

tidbits.com

301–310 of 368 posts

Re: Why iOS 13 and Catalina Are So Buggy

#301
post #262

Yesterday a coworker was frustrated with his computers, and said something insightful: "When software gets past a certain age it just gets bad." He was referring primarily to Android and Windows (10) but it applies to every piece of software that suffers from feature creep. If it's a cash cow they have to keep stuffing new things in and periodically repainting it to make it look new again. Around 10.9, MacOS reached…

I'm reading this on a late-2013 MBP retina running 10.9.5 and not only does it do everything I need it to do, "upgrading" from here would actually cause me to lose essential functionality (which is why I haven't done it). I have a stash of replacement MBPs to replace this one with when it finally does die, but I don't know what I'm going to do when they're all gone because AFAICT everything Apple is producing nowaday…

I actually really like 10.14 - I'm kind of shocked you're still on Mavericks. My 2010 MBP (with upgraded SSD) still rocks 10.13 fine.

What are you worried about losing with Yosemite+?

Re: Why iOS 13 and Catalina Are So Buggy

#302
post #167

Earlier quoted context omitted.

God this, my number one share contact is my ex, who i broke up with almost 5 years ago, and literally havent contacted in over 4. This person isn't even a contact in my contacts anymore, yet still top HOW.

Technology is really reinforcing the correct behavior - if you think you don't want to talk to someone, DELETE them off your phone/social media. I used to have the same problem until i took the plunge and just banished everyone i didn't like out of my digital life. If i don't want to interact with them, i just make their contacts poof/block them

I’ve got a large number of contacts who I rarely (but not never) want to contact.

Re: Why iOS 13 and Catalina Are So Buggy

#303
post #301
post #262

Earlier quoted context omitted.

I'm reading this on a late-2013 MBP retina running 10.9.5 and not only does it do everything I need it to do, "upgrading" from here would actually cause me to lose essential functionality (which is why I haven't done it). I have a stash of replacement MBPs to replace this one with when it finally does die, but I don't know what I'm going to do when they're all gone because AFAICT everything Apple is producing nowaday…

I actually really like 10.14 - I'm kind of shocked you're still on Mavericks. My 2010 MBP (with upgraded SSD) still rocks 10.13 fine. What are you worried about losing with Yosemite+?

iPhoto mainly. But also, in general, Mavericks Just Works for me so any change involves risk with very little potential payoff. I have a ton of apps that I rarely use, but I know they work. If I "upgrade" and next year I discover that this broke something that I only use once in a blue moon, now I'm totally hosed.

Also, I just can't stand the new "flat look". It's just ugly and lazy. It feels like Windows. And the fact that I can't change it offends my sensibilities.

Re: Why iOS 13 and Catalina Are So Buggy

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

You can have releases based on a timed schedule, or you can have them based on a set number of features. You either release every year, making sure it's solid regardless of what new features are in place. Or you based it on when the requested features are ready and solid. If you try to do both, you're in for a bad release.

Re: Why iOS 13 and Catalina Are So Buggy

#305

I've having a feeling that iOS 13 & Catalina is felt buggy b.c. it's not the operating system itself that's buggy but that the updater is buggy. Many things have changed in this release, and the installer/updater had to handle too many different scenarios. For example, when I upgraded from Mojave to Catalina, an 'Moved Files' directory appeared that contained some files (that was once) in /usr/local/. I don't remembe…

> For example, when I upgraded from Mojave to Catalina, an 'Moved Files' directory appeared that contained some files (that was once) in /usr/local/ This is a consequence of the read-only root filesystem in Catalina: https://support.apple.com/en-us/HT210650 Even with SIP disabled you can't do shit to that volume until you remount rw (at least, this was reported to work in betas, haven't seen anyone test the shipped O…

This isn't true, /usr/local is one of the writable firmlinked directories. How else would homebrew work?

Re: Why iOS 13 and Catalina Are So Buggy

#306
post #262

Yesterday a coworker was frustrated with his computers, and said something insightful: "When software gets past a certain age it just gets bad." He was referring primarily to Android and Windows (10) but it applies to every piece of software that suffers from feature creep. If it's a cash cow they have to keep stuffing new things in and periodically repainting it to make it look new again. Around 10.9, MacOS reached…

I'm reading this on a late-2013 MBP retina running 10.9.5 and not only does it do everything I need it to do, "upgrading" from here would actually cause me to lose essential functionality (which is why I haven't done it). I have a stash of replacement MBPs to replace this one with when it finally does die, but I don't know what I'm going to do when they're all gone because AFAICT everything Apple is producing nowaday…

I thought it was just me. I've ended up with a stash of mid-2015 MBP in my office too.

Re: Why iOS 13 and Catalina Are So Buggy

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

Mountain Lion, El Capitan, and High Sierra were all essentially 'Snow Leopards'

Snow Leopard also introduced major new features, like Quicktime X and the App Store. It wasn't quite what people seem to think it is now, 10 years later.

Re: Why iOS 13 and Catalina Are So Buggy

#308
post #296
post #293

Earlier quoted context omitted.

> I have a stash of replacement MBPs You make it sound like they're t-shirts or something haha

More like vintage cars. (My wife and I both drive old cars because it's nearly impossible to find a new car that doesn't spy on you or allow itself to be remotely disabled.)

Really? I drive a base-level 2015 RAV4 and there's no network connection to anything (except, I guess, my iPhone when I play music over Bluetooth).

Maybe where I am cars are still behind the times.

Re: Why iOS 13 and Catalina Are So Buggy

#309

Yesterday a coworker was frustrated with his computers, and said something insightful: "When software gets past a certain age it just gets bad." He was referring primarily to Android and Windows (10) but it applies to every piece of software that suffers from feature creep. If it's a cash cow they have to keep stuffing new things in and periodically repainting it to make it look new again. Around 10.9, MacOS reached…

macOS' problem ironically enough I think is that it is not a cash cow. Apple stopped charging for it with 10.9, but of course more importantly, the Mac itself does not generate a ton of cash for Apple (which was always the true source of revenue). Not a day goes by that I don't imagine features I wish macOS did for me. The desktop OS is not "mature" or "complete", its just not a big enough piece of the pie with comparison to iPhone for Apple to invest time in it. If you were to gift the Mac/macOS business to some random startup, there is a good chance it would see huge stability and evolution. Unfortunately, the business is coupled to a company that happens to make a different product that makes it way more money. If anything, Apple has been removing "features" from macOS at great pain to its users -- and I don't mean 32 bit or this security stuff, I mean the fact that they don't focus almost at all on the surrounding ecosystem. Apple used to continue investing in software for macOS like Final Cut Pro and Aperture, things that kept them invested in the OS itself. They very clearly do not want to be in that space anymore, so its weird to think that the OS is somehow "done" and just "spinning its wheels".

For a good non-open source example, look at Photoshop: it's been around for almost 30 years and people still think its worth paying for and are generally happy with the updates they get. Perhaps some are unhappy with the pricing model, but I actually see lots of people that are very happy with that too (myself included).

macOS only seems stale because it hasn't changed meaningfully in so many years, not because it can't.

With regard to the bugginess: yes, I think it has everything to do with the fact that they are now trying to ship a new version of iOS, iPadOS, tvOS, watchOS, AND macOS every year on the dot.

Re: Why iOS 13 and Catalina Are So Buggy

#310
post #155
post #89

Earlier quoted context omitted.

Yes. Thing is this are de-facto only two platforms alive. Yes. Mobile (and desktop) developers life suck. But someone has to write all that software. And, IMO, iOS/macOS/Cocoa/Xcode is best out there. And most importantly - most stable. Nice boutique experience, nice API, good documentation, everything is integrated and working. Other platforms are even worse. Way worse. I am also doing Switch, KaiOS, Xbox, PS3/4, di…

> And most importantly - most stable I have to restart XCode at least once an hour to get all my breakpoints back and several times a day if it crashes for no apparent reason and boots up with the project missing, empty or missing files. Fortunately I don't do a lot of app development any more but some low level C libs don't compile themselves (no: not possible to do this in any other language). Stable is not what I…

Well, they said "most stable".
Post reply on HN