97: ‘Copious Software Projects’ With Guy English

Episode Summary

Executive Summary: The conversation begins with sports as narrative entertainment and turns into a long, detailed critique of Apple’s yearly software-release cadence. The speakers argue that iOS/macOS are being asked to do too much in too little time, causing bugs, slower adoption, and quality issues, especially after the iOS 8 launch. They contrast this with earlier, steadier OS X improvement cycles and discuss how tighter integration across Apple platforms raises the complexity ceiling.

Main Topics: Sports as narrative, not statistics: The speakers compare baseball and soccer to stories rather than data, arguing that sports are compelling because outcomes are unpredictable, emotional, and not reducible to spreadsheets or batting averages. Don Mattingly and sports fandom through personality: A temporary interest in the Dodgers stems from Don Mattingly’s legacy as a beloved Yankees player, illustrating how sports attachment often comes from individual stories and nostalgia rather than team loyalty. Apple’s annual OS release cadence is under strain: The main thesis is that Apple is trying to ship too many major features every year, leaving only a few months for real feature development after bug-fixing and beta cleanup, which increases instability. iOS 8 adoption slowdown as a warning sign: They point to Apple’s own adoption numbers to argue that buggy releases reduce trust and may cause users to delay updates, which harms both customers and developers. Integration across Apple platforms raises complexity: Mac, iOS, watchOS, iCloud, and future Apple TV features increasingly depend on one another, making synchronized shipping harder and making bugs or delays in one product affect the whole ecosystem. Marketing, messaging, and Apple’s feature strategy: They discuss how Apple’s marketing is intertwined with product design, and how iOS 8 largely answered competitive pressure from Android/Windows Phone with features like larger phones, keyboards, and sharing. Backups and practical trust in software/services: A Mac failure becomes a demonstration of why automatic backup tools like Backblaze matter: the machine can fail, but if backup is automatic, data loss is avoidable and stress drops dramatically.

Key Arguments: Apple likely gets only 3-6 months of real feature-building time per annual OS cycle because the first months are spent fixing the previous release’s bugs and the last months are spent stabilizing the beta. The iOS 8.0.1 bug and related quality issues are evidence that Apple may have overcommitted; even a small-percent bug can affect tens of thousands of users and damage trust. Apple’s own adoption data suggests users are updating more slowly than they did with iOS 7, implying that bad experiences and negative word of mouth can materially slow updates. The yearly cadence is not necessarily the problem by itself; the bigger issue is the amount of change Apple tries to cram into each year. Apple’s growing ecosystem interdependence means that features increasingly require synchronized releases across devices and operating systems, amplifying schedule pressure. Some earlier OS X releases benefited from a steadier, more gradual improvement path; the speakers contrast that with recent releases that feel more rushed. The conversation rejects the idea that Apple intentionally degrades older devices; they argue that no engineer would choose to make software slower on purpose because it harms both users and company culture.

Data Points: iOS 8.0.1 affected users: 40,000-50,000 users - The speaker cites estimates of how many devices were hit by the bad update after its brief availability. iOS install base: ~10 million install base - Used as the denominator when discussing the relative size of the iOS 8.0.1 issue. iOS 8 adoption vs iOS 7: 47% iOS 8 / 47% iOS 7 / 6% earlier versions - Apple’s own developer-facing adoption snapshot from October 5, 2014. iOS 7 adoption 20 days after launch: 70% - Used for comparison to argue that iOS 8 adoption was lagging significantly behind. Harry’s price comparison: $20 vs $40+ - The ad reads that equivalent Harry’s blades cost about half of comparable Gillette Fusion blades on Amazon. Backblaze price: $5/month - Automatic online backup for one Mac, including external drives. Ubar discount: 50% off / $10 - Coupon code 'Gruber Edition' reduces the normal $20 price to $10. Ubar update cadence: 30 updates since July - Illustrates how quickly the developer iterated after launch. Podcast runtime: 2+ hours / 6+ hours - References to long debug episodes with Nitin Ganatra and Don Melton.

Pivotal Quotes: "The bottom line for me… it's the narrative fiction." — John Gruber: Explaining why sports remain interesting despite seeming statistically repetitive. "I think they've bit off more than they could chew in terms of how much it was going to do and ship." — John Gruber: Core thesis on Apple’s overextended annual software-release cycle. "No new features." — John Gruber: Reference to Snow Leopard as an example of a release that intentionally focused on stability and refinement.

Implications: For listeners and developers, the episode suggests Apple should prioritize fewer, more polished features over headline-grabbing yearly expansion. If trust in updates keeps slipping, adoption slows, developer incentives weaken, and Apple’s ecosystem advantage erodes.