147: Here I Am, I'm a Battery

Release Cycle

Apple's approach to release management is a testament to their disciplined software organization. John Siracusa highlights the importance of a structured release cycle, emphasizing that yearly releases are a matter of efficient management. He explains that Apple transitioned from a more flexible release schedule to a regimented annual cycle, ensuring that projects either meet the deadline or are postponed to future releases 1. This approach allows Apple to maintain a consistent development pace, despite the challenges of managing multiple projects simultaneously.

We're going to put ourselves on a yearly schedule. We're going to be disciplined about it. That is much more sort of business 101.

--- John Siracusa

Siracusa also notes that while major system overhauls are necessary, they must be executed well to avoid setbacks, using examples like launchd and icon services to illustrate successful and problematic implementations 2.

   

Software Overhauls

Software overhauls at Apple have been a mixed bag, with some updates leading to significant improvements and others causing issues. Marco Arment and John discuss how the Mac was once neglected in favor of iOS, leading to rushed updates that sometimes resulted in bugs and poor execution 3. Arment expresses a preference for stability over frequent updates, urging Apple to avoid unnecessary major changes that disrupt user experience.

Please stop updating it every year and please stop trying to do major, like massive shifts on it. Just please.

--- Marco Arment

Despite these challenges, Siracusa believes that Apple's core OS group generally does a commendable job with major rewrites, though the relentless annual release schedule can strain resources and affect the quality of these updates 4.