139: ‘How Many Fingers Should This Baby Have?’ With Special Guests Craig Federighi and John Siracusa

Episode Summary

Executive Summary: Craig Federighi discussed Swift’s first week as open source, portraying it as a major success with huge GitHub activity and broad community involvement. The conversation covered why Apple opened Swift, how it balances modern syntax with systems-level performance, the importance of ABI stability for Swift 3, and why the language is meant to span education, app development, scripting, and servers while coexisting with Objective-C for now.

Main Topics: Swift’s first week as open source (Priority: 5/5): Federighi says the open-source launch massively exceeded expectations, with intense GitHub activity and strong enthusiasm from developers worldwide. Why Apple chose open source (Priority: 5/5): Apple framed open sourcing as essential for making Swift broadly usable across education, scripting, servers, and app development, not just on Apple platforms. Systems language design and performance (Priority: 5/5): Federighi explains Swift as a systems language with predictable memory management, ARC-based performance, and compiler-driven optimization to compete with C-like efficiency. Swift vs. Objective-C (Priority: 4/5): The discussion contrasts Swift’s safety and compile-time optimization with Objective-C’s dynamic runtime and C baggage, while emphasizing that interoperability remains crucial. Swift 3, ABI stability, and language evolution (Priority: 4/5): A major near-term goal is ABI stability and API refinement so Swift becomes a durable platform for the next decade or more, even as syntax and features continue evolving. Adoption inside Apple and across platforms (Priority: 4/5): Federighi describes internal Apple teams adopting Swift where practical, while noting 32-bit support constraints and the growing role of Swift on Linux and servers. Podcast-side commentary on Apple communication and other topics (Priority: 2/5): After the interview, John Siracusa and the host discuss Apple’s openness vs. secrecy, App Store frustrations, and a long digression on the new Apple battery case and Star Wars spoilers.

Key Arguments: Swift’s open-source launch was wildly successful, with GitHub activity and cloning far beyond expectations. Apple sees Swift as a language for the next 20 years, including education, scripting, servers, mobile apps, and systems programming. Open source is necessary for Swift to become a credible teaching language and a cross-platform tool developers can invest in broadly. Swift’s design prioritizes predictable memory management and high performance without relying on garbage collection or a virtual machine. Swift preserves the dynamic capabilities that matter from Objective-C, but avoids paying runtime overhead for them all the time. Interoperability with Objective-C is essential during the transition; Swift cannot replace Apple’s ecosystem overnight. ABI stability is the key milestone for Swift 3 because binary compatibility matters deeply for long-lived apps and frameworks. Internal Apple feedback has already shaped Swift’s direction, especially around incremental compilation, error handling, generics, and Objective-C bridging. The host argues that Apple is more open around Swift than in many other product areas because the language benefits from community-driven development. The post-interview discussion frames Swift as an example of Apple’s pragmatic idealism, while criticizing App Store opacity and exploring the design logic behind Apple’s battery case.

Data Points: GitHub clones: over 60,000 - Federighi cites the first week of open-source Swift activity Launch timing: last Thursday - The transcript places Swift’s open-source release about a week before the interview Swift 1.0 announcement: 2014 - Referenced when discussing the language’s early evolution and feedback cycle Swift 3 goal: stabilize the binary interface - Described as a core milestone for the language’s next major phase Apple’s community engagement: more active than all other languages on GitHub (as described in interview) - Federighi’s claim about the project’s first-week activity 32-bit support: not supported by Swift runtime on macOS at the time - Used to explain why some Apple teams still could not fully adopt Swift Teaching context: university courses and Stanford’s Swift course on iTunes U - Example of Swift’s educational potential Memory model: ARC-based, predictable memory management - Contrasted with garbage-collected languages like Java and scripting languages Open-source clone count: over 60,000 people - Another explicit measure of Swift’s early adoption Wealthfront fee: 0.25% - Sponsor segment after the main interview Wealthfront minimum: $500 - Sponsor segment describing account entry point Wealthfront fee threshold: $10,000 normally; $15,000 with code - Sponsor segment explaining pricing Casper price range: $500 twin to $950 king - Sponsor segment describing mattress pricing Casper trial: 100 days - Sponsor segment describing risk-free sleep trial Harry’s promo deadline: December 18, 2015 - Sponsor segment about holiday shipping cutoff

Pivotal Quotes: "Really, really well. I mean, the level of activity on GitHub is off the charts." — Craig Federighi: His assessment of Swift’s first week as an open-source project "We knew we needed to have this kind of open dialogue. And open sourcing is, as you say, just really accelerating and deepening the kind of feedback that we're getting." — Craig Federighi: Explaining why open development matters for a programming language "People here are idealistic yet really pragmatic." — Craig Federighi: Describing Apple’s internal culture and how it shapes Swift adoption

Implications: Swift is positioned as Apple’s long-term language bet: open, cross-platform, compiler-optimized, and education-friendly. For developers, it suggests greater community influence, better tooling, and a durable path away from Objective-C without sacrificing performance.