No way. The current more-than-a-year update cycles for iPad and Macs are already too long. Everything should have annual updates.
What timeframe would you prefer and why?
No way. The current more-than-a-year update cycles for iPad and Macs are already too long. Everything should have annual updates.
I blame agile/scrum for a lot of problems in the modern world. Before I retired I was placed into various scrum teams and I hated it. It is certainly effective for slapping stuff out the door, but is the enemy of doing truly great or inspirational work. My best ouput over many years happened after long periods of quiet reflection and very carefully thinking about the right way of designing systems. That all went to pot when the agile philosophy of just getting something banged out and worrying about fixing it later. That way lies plenty of dead end strategies and wholesale revisions sooner or later. Glad I’m out of it now. Meanwhile, teams of developers are using my old carefully planned code libraries on a daily basis, all done without a stand up or sprint in sight.Some bugs take minutes, some bugs take weeks, some need some major rewrite.
More like this.2 year software cycles, please.
Craig seems like a bright guy and he’s Apple’s best executive active at working a room, but it’s indisputable that the software experience has indeed been garbage on his watch. Something has to give. I don’t know if it’s the yearly cycle or what, but it really does feel a bit like we haven’t had a decent iOS release in over 10 years which is profoundly ridiculous when you think about it.iOS has been awful for years when it comes to bugs.
Craig Federighi should have went years ago.
Software quality control has been garbage on his watch.
Apple’s executive leadership is much too rotten for this type of wholistic product-oriented leadership at this point.I made a thread related to this a while ago:
Unrealistic — but fun — idea...
There're many comments, in various threads, wishing Apple would slow down, or even stop, adding software features, and focus on tightening-up their software.
Many often cite Snow Leopard as being the heyday for Apple's "it just works" age, and I'm sure there's a similar reference for iOS. As Apple continues to strive to add more and more bells and whistles to their software, more and more bugs and inconsistencies are bound to come up.
As far as I know, this is somewhat inevitable with such a fast development cycle. I've heard people blame Apple's focus on pleasing shareholders first, and consumers second — drive more sales of the newest hardware models through software updates that require new purchases. I'm sure it's more complicated than that, but you're here for a crazy and fun idea, not my ignorant speculation...
The idea...
Apple announces, in typical cryptic fashion, that the Apple polishing cloths will no longer be available until further notice.
Later, when it comes time for WWCD of that year, the theme is some clever variation on 'the year of polish' or 'our lineup has never been shinier' or something actually good.
The point:
Apple announces that the polishing cloths were no longer available to the public, as they were needed internally. They needed them so they could spend a full year focused on 'polishing' their existing offerings (not literally, of course - I'm talking software).
They announce the name of the new update to macOS as [clever name], and a video plays with a reel like: (with accompanying iOS and iPadOS versions)
New features: none!
Added functionality: none!
Pretty novelties: none!
...
Bugs fixed: 23,434,543
Consistency improved: 3,567,343 instances
Energy efficiency: up 363%
Crash decrease: 476%
User satisfaction: +254%
etc... (any metrics which can actually measure these improvements)
Then, at the end, they show a room full of Apple employees polishing MacBooks, iPhones, watches, and iPads. All getting shinier and shinier...
- They talk about taking everything they already have, but has objectively needed more time to polish and refine, and then re-offering it in an update which re-commits to the principles of quality over quantity, reliability, and "it just works".
- They talk about longer lasting hardware (due to more efficient and optimized software), in order to help with e-waste.
- They talk about staying true to the principles which made them the most valuable company in the world.
- They talk about defining their software in the same way they have done with their hardware: polished and refined to a level unmatched in the industry.
"The polishing cloths will be available again on [DATE]." <– the release date for the 'new' OS.
Shareholder relations...
There would need to be a separate, specific, presentation directed at shareholders, so they don't think Apple has gotten lazy and will lose sales.
This would be a long-term gain to offset the downturn in hardware sales, and to get fans to fall in love with their products again. If they pulled this off, then it would, hopefully, pull more and more people into the Apple ecosystem due to it's ease of use, consistency, and reliability — all things which used to be associated with Apple far more frequently.
Not gonna happen!
I know. I just thought it would be fun to write out and discuss.
Always good to see a Snow Leopard reference. Best damn software Apple ever shipped.Let's go!!! Mac OS 15: Snow Leopard 2!!!
Right on. I don’t see how these things don’t aren’t prioritized considering how comparatively slow (historically, to Android) Apple has been to implement new features.Thank God. They should do this sort of clean up at least once every year. Performance, stability and lack of bugs should be the foundation of every software release.
It's insane to me that they apparently don't have a dedicated bug squashing teamYou’d think they are big enough to have two separate teams, one focused on fixing things and another one developing new things?
Exactly. Apple should have kept Scott Forstall. But Tim Cook was, and still is, too mediocre to realize the extremely high value of someone like Forstall. Cook is an MBA, and MBAs are typically mediocre and far more concerned about making money above all else.iOS has been awful for years when it comes to bugs.
Craig Federighi should have went years ago.
Software quality control has been garbage on his watch.
So the team fixing bugs will wait for the new stuff to be delivered so they can fix it?You’d think they are big enough to have two separate teams, one focused on fixing things and another one developing new things?
What is forstall doing nowadays that shows his quality?Exactly. Apple should have kept Scott Forstall. But Tim Cook was, and still is, too mediocre to realize the extremely high value of someone like Forstall. Cook is an MBA, and MBAs are typically mediocre and far more concerned about making money above all else.
Had Apple kept Forstall, in addition to the increased comparative stability that iOS had under his watch, we would've still had the most beautiful skeuomorphic design in the entire tech industry on our iPhones, iPads, and Macs. But instead, we're stuck with this ugly Microsoft-pioneered flat design.
Do *NOT* get me started with Scrum/ "agile"/ "Dev-ops". Great methodology for very limited circumstances. Do not use Scrum for something as complex as a modern operating system.I blame agile/scrum for a lot of problems in the modern world. Before I retired I was placed into various scrum teams and I hated it. It is certainly effective for slapping stuff out the door, but is the enemy of doing truly great or inspirational work. My best ouput over many years happened after long periods of quiet reflection and very carefully thinking about the right way of designing systems. That all went to pot when the agile philosophy of just getting something banged out and worrying about fixing it later. That way lies plenty of dead end strategies and wholesale revisions sooner or later. Glad I’m out of it now. Meanwhile, teams of developers are using my old carefully planned code libraries on a daily basis, all done without a stand up or sprint in sight.
I’m glad someone else doesn’t agree with agile. It was cool for indie software back in the day that was shareware and stuff but now full on OS’s and mainstream software are riddled with bugs. They can only have their customers be their beta testers for so long.. not to mention that now cyber attacks are a huge threat compared to back in the day. It’s getting really risky. I prefer waterfall. I’m getting tired of screaming “it just doesn’t work!” about all my Apple products everyday. Apple seriously needs to just stop, slowdown and get everything running 100% again so we can actually say “it just works!”. I’m getting worried about cyber threats which are more important than a moving desktop wallpaper. Basic stuff should work, like the settings app. I’ve had 3 different Apple devices malfunction today, it really pisses me off!I blame agile/scrum for a lot of problems in the modern world. Before I retired I was placed into various scrum teams and I hated it. It is certainly effective for slapping stuff out the door, but is the enemy of doing truly great or inspirational work. My best ouput over many years happened after long periods of quiet reflection and very carefully thinking about the right way of designing systems. That all went to pot when the agile philosophy of just getting something banged out and worrying about fixing it later. That way lies plenty of dead end strategies and wholesale revisions sooner or later. Glad I’m out of it now. Meanwhile, teams of developers are using my old carefully planned code libraries on a daily basis, all done without a stand up or sprint in sight.
No, but I know that TFTP runs on port 69.. it’s trivial.Do you remember FTFF?…
Yep, 1 week, 3 day of which our meetings followed by 1 day of trying to rewrite code and the last day trying to explain to the PM why you couldn’t fix it.Now that's something new.