Episode Summary
Executive Summary: The episode spans a long WWDC preview focused on Apple’s direction: skepticism about Swift on servers, support for boring/established back-end tech, and a call for Apple to slow down and fix quality issues. The hosts especially want visible progress for Siri, Mac, WatchOS, notifications, and better APIs that open third-party app access, while also discussing sponsorships, AirPlay 2/Messages in iCloud, and personal computer/car headaches.
Main Topics: Server-side language choices and the case against Swift: The hosts debate what language is best for server-side development, arguing that Swift on the server is still too new and risky, while older, boring, open technologies are safer. They discuss .NET Core as more reasonable than old .NET because it runs cross-platform and keeps C# benefits without the Windows ecosystem baggage. WWDC expectations: Apple slowdown, quality, and missing macOS/Siri progress: A major thread is what Apple should announce at WWDC. The speakers want signs of life for Mac and Siri, but also hope Apple is taking time to fix bugs, finish features, and avoid shipping half-baked releases. They frame this as a 'rebuilding year' where stability matters more than flashy launches. Siri improvements, SiriKit expansion, and default-app-like behavior: The conversation turns to frustrations with Siri's reliability and intelligence, plus wishlist items like a SiriKit audio intent, more generic SiriKit actions, and the ability to choose default apps for certain intents. The group sees these as high-value platform improvements for users and third-party developers. WatchOS limitations and possible redesigns: The hosts discuss WatchOS shortcomings: slow Bluetooth behavior, poor audio playback APIs, weak notification controls, and static complications. They want smarter complications, third-party watch faces, better background audio support, and improved radio/power handling, especially when the watch is on the charger. iOS feature maturity: notifications, dark mode, springboard, and UI framework rumors: The speakers talk about likely iOS 12 features and what is probably not coming, such as major home screen redesigns. They speculate about future UI frameworks, cross-platform efforts, and dark mode, but mostly expect incremental improvements rather than a big visual overhaul this year. Personal gear: iCloud storage, HomePod/AirPlay 2, and beach computer logistics: The discussion gets personal as the hosts talk about Messages in iCloud storage usage, HomePod stereo pairing, AirPlay 2 testing, and the practical problem of working at the beach with the wrong laptop/monitor setup. The thread blends product commentary with real-world workflow pain. Car ownership frustration and replacement strategy: In a later off-topic segment, Casey details major BMW repair costs and considers replacing the car with something simpler, possibly a Wrangler or another vehicle. The conversation centers on trade-in strategy, leasing, maintenance costs, and the importance of not rushing a new purchase.
Key Arguments: Swift on the server is too new and risky; server software should be old, boring, and widely deployed before being trusted. .NET Core is more plausible than legacy .NET because it preserves C# benefits while avoiding the worst Windows deployment baggage. Apple should slow down feature shipping to improve quality, but not stop making progress; it should fix longstanding bugs and ship fewer unfinished features. Siri is still unreliable, slow, and too limited; Apple needs major improvements in accuracy, consistency, and third-party app integration. A generic SiriKit action system and default-app support would dramatically improve the platform and empower third-party developers. WatchOS should prefer better transport choices and smarter UI behavior, including more useful complications and background audio support. Third-party watch faces would be a huge crowd-pleaser and a major opportunity for personalization and developers. A yearly OS cycle can push Apple to announce things before they are truly ready, which may be part of why features are delayed or incomplete. For personal workflows, cross-device syncing via Git and Dropbox can be practical, but it has limits for large directories and node_modules. When replacing a damaged car, trade-in at a dealer is often smarter than private sale because it reduces risk and can offset purchase cost more efficiently.
Data Points: Messages in iCloud storage usage: 4.6 GB - One speaker checked iCloud storage and found Messages consuming 4.6 GB after enabling Messages in the Cloud. Messages conversations storage: 2.18 GB - Within iCloud storage management, the conversations subcategory showed 2.18 GB. Negative conversation sizes: -1 byte / -6 bytes - A bug-like storage calculation displayed individual conversations with negative byte values. App Camp for Girls fundraising target: $25,000 - The hosts promoted an App Camp for Girls benefit concert and said they were trying to raise this amount. WWDC concert ticket price: $35 - Tickets for the App Camp for Girls concert were described as a $35 donation. Eero promo: Free overnight shipping with code ATP - Eero sponsor offer for overnight shipping in the US or Canada. Casper promotion: $100 off Wave purchase with code ATP100 - Casper sponsor offer for the Wave mattress. BMW repair estimate: $5,000 - Casey’s car was quoted at roughly this amount for several repairs. Car value: about $10,000 - Casey estimated the BMW was worth about this much several months earlier. Immediate repair outlay: about $750 - Casey expected to pay for brake pads, brake fluid, and a cabin air filter. Front differential issue: hum at 75 mph indicated / likely differential failure - The BMW had a hum at highway speed that the dealer suspected came from the front differential. Trade-in strategy: Dealer trade-in preferred over private sale - The hosts recommended using the broken BMW as trade-in leverage rather than selling privately. HomePod count: 2 units - John said he bought two HomePods, one for home and one for the beach. Storage plan: free iCloud plan - One host admitted not paying for iCloud storage despite considering Messages in iCloud. Stickers from Sticker Mule: about 200 made / about 180 left - Marco described printing a large batch of stickers and still having most of them a year later.
Pivotal Quotes: "Swift on the server is not a good idea because it is not ready." — Marco: The core argument against using Swift for server-side development. "You want to be on the boring old technologies that everyone's been using for a long, long time." — Marco: Why stable, mature server tech is preferred over bleeding-edge options. "I want to see a sign of life that the lull that we're seeing in these two major problem areas is not because they're just being neglected forever, but because bigger stuff is coming." — Marco: His WWDC hope for the Mac and Siri.
Implications: Listeners should expect WWDC to emphasize refinement over revolution. For developers, the biggest opportunities are likely in APIs and platform access rather than flashy hardware. For Apple, Siri, Watch, Mac, and notification quality remain key proof points.