Sonoma seems pretty buggy. It is hard to understand how things got that bad when feature updates are “wallpaper” and “widgets”.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Briefly Paused Work on New Features for iOS 18 and macOS 15 to Clean Up Bugs
- Thread starter MacRumors
- Start date
- Sort by reaction score
Bwahaha, hearing that the employees have to beg for time to fix bugs is a bummer, but hearing that they got a week for it is embarrassing.
A whole year pause would have been more adequate, in a week they will fix no more than a few smaller quirks.
Anyway, this shows how broken Apple internally is, and in what a bad condition their operating systems are, and that they also have the featuritis syndrome.
All what they do is mainly for sake of revenue and not customer satisfaction.
That’s the big difference between Steve Jobs and Tim Cook.
Shame on you Tim, SHAME, SHAME! <GOT>
But keep the clothes on!
A whole year pause would have been more adequate, in a week they will fix no more than a few smaller quirks.
Anyway, this shows how broken Apple internally is, and in what a bad condition their operating systems are, and that they also have the featuritis syndrome.
All what they do is mainly for sake of revenue and not customer satisfaction.
That’s the big difference between Steve Jobs and Tim Cook.
Shame on you Tim, SHAME, SHAME! <GOT>
But keep the clothes on!
Last edited:
So it looks like OS 15 will omit silicon based Macs. I hope security updates will be available for a few more years for my 2019 Intel 27" iMac. At that point with Apple cancelling the option for a 27" iMac hopefully a reasonably priced 32" iMac will be available. 🙏🏻
How about we focus on the software that was released like 5 minutes ago?
I've said it over and over, Apple's main issues are (mostly) software related.
I've said it over and over, Apple's main issues are (mostly) software related.
They need to develop next year's release all year long. They don't start working on it right before it is released.
I'd 9 women can create a baby in 1 month, surely more software engineers can fix these bugs.
I just hope they don’t use this excuse to explain why they are not moving fiercely on artificial intelligence. They are too busy fixing bugs.
Last edited:
Maybe they can use artificial intelligence to fix the bugs...
What would make that a good idea? I would prefer a dedicated team developing and maintaining their own codebase.
If this report is accurate, it highlights the major problem at Apple over the last 10+ years. There are too busy rushing to the next version to properly ever maintain or finish a current version. As much as they want to say Craig is trying hard to release stuff without bugs, I think what they really mean is he’s trying hard to release stuff without bugs in spite of the fact that there is a constant marketing momentum to release new major system versions every year. I’ll say it a million times if I have to, they need to slow down and get things right. Maybe split up the release cycle to release macOS one year, and the mobile operating systems the next year, or develop them on a general 2 year cycle. Sonoma has been an absolute disaster, myself and many others can barely work with external drives, see constant, crash reports, an entire breaking of the print system, and many little bugs that make you upgrading in the first place. This past week I used a 2012 Mac mini running 10.15 to do some file work, because it was significantly more reliable than my Mac Studio running Sonoma.
I can see how that would make sense, but in practice it’s kind of tough to split up the teams that way. Generally the person or team developing the software are going to be better at fixing bugs, as they know the ins and outs of the code, and why they made the choices they made. Also coders tend to not like other people fixing their bugs are changing their code. I’m not sure how Apple does things internally these days, but I think what you would probably see is a team collecting and categorizing the bugs, then the person or team who worked on the individual piece of code that is buggy will work through to fix it.
I think the idea on stopping development for the next system, to fix the current system, comes down to them not pushing their teams to work on new ideas, and give them the time they need to sort through the problems their software currently has.
You get to a point in software development where adding people just makes managing and progressing a project slower and more complicated. Same goes for testing and if you have a yearly major update milestone to reach, the pressure is on staff and managers to just sign it off, regardless of whether the software is truly ready, You also see this in features now being delayed and drip fed into updates. What has happened is a clear sign the team is stretched too far. Yearly feature updates of a mission critical piece of software like the operating system is frankly stupid. It was always a case of the marketing team winning the argument over the dev team. No software engineer worth their salt was ever going. to say major yearly updates of the most mission critical software for any hardware device is a good idea. I've become so concerned about it, I am now blocking all operating system upgrades to my devices and won't even look at a system upgrade, until that OS is feature complete and a couple of years old. I only allow security updates through to my devices in the interim. Happy to be a revision or two behind the cutting edge and let other Apple users be the beta testers for Apple. Personally, I think it's only a matter of time before a major security issue happens with Apple. Tim's quest to maximise profits has a downside and this is one of them. The other no doubt is being felt in the hardware team, who would be under the same insane pressure.
Last edited:
I think the way Microsoft did it at one time is that they split it so that one would be working on new features for the release, and the other team would be working on fixing bugs from the features they worked on the previous release. Not sure how well that would work here, but just having one team always working on features and the other on just fixing bugs is not a good way to go.
Maybe, it was their Apple products that didn't work and they were upset about it, so they made software developers switch gears and fix things.
Internally they no doubt have a similar structure. The problem is the cadence of expected OS upgrades.
It's apple that is afraid of imaginary monsters cause they don't even have a public visible list of bugs. Report a bug and you don't even know if they are working on it or how many people already reported it.
Honest question because I do not know this answer. How many large companies do that?
