4 ms·
I’d suggest quality and stability of the rapidly advancing Apple ecosystem became the priority. MacOS has had to keep up with a relentless march in services an
by bredren 3y ago
I’d suggest quality and stability of the rapidly advancing Apple ecosystem became the priority.
MacOS has had to keep up with a relentless march in services and devices each with their own peculiarities.
iPhone has had to have an annual release cycle, and there are multiplatform apps and crossplatform features to maintain and extend on deadline.
- bmitc 3y agoI have been at a company that transitioned from normal release cycles to arbitrary yearly release cycles. Every year became a literal race to fix issues, improve existing features, and add new features. It was a gigantic mess. The yearly release cycle only really gives a few months to do all of that, because the other months are doing integrations, testing, and bug fixes to get the release out the door. I can certainly see that if the emphasis on new features greatly outweighs that of bug fixes and improvements, then you can extend the implementation months for larger features because you can just bleed the bug fixes and improvements into next year's release. But then that year's feature set takes precedence and dept accumulation occurs. My own experience with macOS is that it stopped "just working" a decade ago Apple stopped caring about it and poured everything into iOS. And then this is exacerbated by today's mode of operating by just treating features like they're free and frequent release cycles.
- newsclues 3y agoIt's not the release cycle per say, but the need to pack new features in each cycle for marketing and sales. A regular release cycle that focuses on security, stability and incremental improvements, is fine as long as there isn't a need to constantly push new features in.