Snow Leopard had nothing to do with leopard being a disaster. It was just after 3 straight years leading up each OS was touting 150+ features in each release and that isnt sustainable. Also they had most of the team working on the launch of the iPhone so just didn't have the recources. The first time i started feeling like an os x was kinda a disaster was Lion and that was because the iPhone was out and iOS was now the top thing over there instead of os x.
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 Reportedly Overhauling Its Software Development Process Following Buggy Release of iOS 13
- Thread starter MacRumors
- Start date
- Sort by reaction score
Told you so.
30+ years ago we had "Feature bits" (flags) architected in our code base. But all these youngster script kiddies are assumed to be smarter. Good luck with that Timmy.
BTW. I told you so. See my earlier posts - I noticed a quality downfall beginning with iOS 9.
30+ years ago we had "Feature bits" (flags) architected in our code base. But all these youngster script kiddies are assumed to be smarter. Good luck with that Timmy.
BTW. I told you so. See my earlier posts - I noticed a quality downfall beginning with iOS 9.
Last edited:
Honestly Windows 10 for me right now is way more stable than OS X is now and as you said, its on a far wider array. Havent had a blue screen/screen freeze in I don't know how long. Only time I have needed to restart my computer is when cumulative update comes and thats it. Chromium Edge which is in beta is more stable than Safari which has been out how long? I'm not saying macOS is horrible by any means but can not say at this time it is more stable. 90 % of time people have these problems because of software that tweaks or changes the normal function of the os and the system becomes unstable or slows down or an update breaks because of it. I have never really had a problem with any OS except when I did something stupid to cause it.
Absolutely spot on, Catalina is horrific... I hope to god it improves
I wonder how he feels about the current state? Still filled with ill will toward Apple, wishing he could help, or sad and resigned to the fact that the madness will continue?
[automerge]1574363246[/automerge]
I have no issues with Mojave on my 2017 iMac. I have no plans to touch Catalina.
I was thinking OS X just sucked at multiple monitors. It's frustrating. Ignoring MST on DisplayPort is ridiculous.
I do have to give either Apple or Microsoft props for properly handling remoting into a computer with multiple monitors. The ability to choose which machine by monitor is brilliant.
Are you a software developer for a major company like Apple? The competition is absolutely fierce at that level. You miss a feature and you're considered a YEAR behind and it becomes big news and hurts your brand.
At the same time, you want to to BEAT the **** out of your competitors so you want to build fast.
And in parallel, you get to hire some of the best in the world, who want to prove themselves hard by building the latest and greatest.
All three things don't mass well with each other.
It could be a reflection of the transition to a services company. Though for my part beyond iTunes Match there aren't any services I find worth buying.
Funny thing is that my iOS experience for 13 hasn't been as much of a problem as OS X Catalina.
Apple is overhauling the way it develops and tests iOS, macOS, watchOS, and tvOS in hopes that the new approach will improve the quality of each software platform over the long term, according to Bloomberg's Mark Gurman.
The report claims the new strategy is already being applied to development of iOS 14 ahead of its release next year. The shift comes after the buggy release of iOS 13, which has already received eight updates with bug fixes and delayed features in the last two months, which is more than usual over that time.
The new process will see Apple implement "flags," allowing the company's software engineers to selectively enable or disable unfinished or buggy features in an isolated way to ensure that overall stability is not jeopardized. Flags are already commonly used by other tech companies like Google and Microsoft.
Apple has also considered delaying some iOS 14 features until 2021, according to the report, as part of its efforts to ensure the update is more stable. Apple is believed to have taken a similar approach with iOS 12, delaying some features until iOS 13, which contributed to iOS 12 being a rather stable update.
The changes were reportedly announced at a recent meeting with employees led by Apple's software engineering chief Craig Federighi.
In the meantime, Apple continues to test iOS 13.3, with a third beta released this week.
Article Link: Apple Reportedly Overhauling Its Software Development Process Following Buggy Release of iOS 13
The tight integration and symbiosis of hardware and software.
Not..err...going so well.
I like more features. I'm ok with some minor bugs here and there if it means I get more features on a yearly basis. It's software folks, all software has bugs.
Because developing this way is slower.
It's easier and faster to rip out old code, change it to new, as you implement a new feature, then check-in everything when you *believe* it works. The downside, of course, is that if it doesn't work you're stuck with only two options --- the old code (which doesn't implement what you want) and the new code (which implements 15 different parts of what you want, one of which may not work).
The alternative is to try to reduce every change you make to a minimal size, and make those changes as independent as possible. Some will be "packaged" as a collection of small check-ins, some will be packaged as a litter of #ifdef's and if( FEATURE_XXX() ) throughout the code.
The alternative is more robust, yes. But it also slows you down a LOT. It can work well for some contexts (like updates to LLVM, where it's already been in place for years), especially where the nature of each problem is fairly well understood and the only task remaining is to implement the understood changes. But it's very problematic for new exploratory code, where you don't really know whether an idea will work or how it will pan out.
It may result in something like each *big* Apple change having to be written essentially twice, once in "exploratory" mode, then again in "responsible" mode. This may not be a bad thing; some of what Apple has shipped has been half-baked not just in execution but even in design.
But that's the basic issue, that's why it's been avoided till now by most teams; because it will slow things down.
Unit Tests should always be written regardless of developers practicing Test Driven Development. TDD is a method of unit tests and code pretty much concurrently. Plenty of developers find TDD hard going, rather than writing code first, then Unit Tests towards the end of the piece of work.
If you can't Unit Test your code, then maybe you've got a ****** code base.
If you can't Unit Test your code, then maybe you've got a ****** code base.
Last edited:
Slow news day.https://www.macrumors.com/2018/01/30/apple-to-focus-on-ios-performance-quality-issues-axios/
Is MR just rehashing old articles now?
swingerofbirch
macrumors 68040
If you have to learn a lesson this many times, you haven't really learned it.
Will Apple do better this time? Possibly.
Will they forget those principles? Probably.
Will Apple do better this time? Possibly.
Will they forget those principles? Probably.
Wow. Did you really say that if i want stability i should wait for the ‘new, improved’ load of crap software to stabilize? That is incredibly short-sighted. Why go through the effort upgrading if the release is buggy and error prone? I cannot fathom that approach on any terms.
If it is truly your ‘want’, your computer is simply a toy. One cannot get any serious work done if they are always dealing with bugs and stability issues.
As a serious software developer, Apple should wait until this half-baked load of poo is stable before they foist it on their customers.
You clearly don’t know anything about it yet you’re so hateful of a guy who lead the creation of the entire platform. What you don’t know is that it was a goal set by Steve Jobs himself to build their own mapping system in two years to get rid of Google. So during the time of iOS 4 they were already working on new Maps. Don’t forget that Scott was reporting directly to Tim and that means Tim approved it and it’s kinda his fault too. I’m 100% sure that such herculean task couldn’t be done by today’s Apple.
And you’re commenting on an article that says Apple can’t get their stuff properly released so I don’t understand what are you talking about.