Episode Summary
Executive Summary: The episode ranges from lively debates over date formats, Celsius/Fahrenheit, and Mac habits to practical Apple troubleshooting, podcast ad targeting, and recent iOS/macOS bugs. The central thread is that Apple’s software and hardware choices often clash with user habits, while the hosts argue that pragmatic workflows, clear logging, and responsible engineering matter more than dogma.
Main Topics: Date formatting and standards: The hosts debate ISO-style year-month-day versus U.S. month-day-year and day-month-year conventions. They agree machine/file sorting favors year-first unambiguous dates, while display preferences are more subjective. Temperature units and cultural defaults: A heated aside argues Fahrenheit is better for ambient human temperatures in the U.S., while Celsius is framed as more scientific but less intuitive for everyday weather. The argument mirrors the date-format dispute: context matters. Apple bug disclosure and security practices: They clarify the distinction between Apple developer forums and support forums, discuss a bug emailed to [email protected], and revisit the debate over responsible disclosure versus public disclosure. Mac/iOS usability complaints and habits: Several long-running user frustrations are discussed: sluggish wake on Macs joined to Active Directory, keyboard autocorrect problems in iOS, the Touch Bar’s limited usefulness, natural scrolling preferences, and preserving old window-management behaviors. Podcast ad targeting and dynamic insertion: The show explains how dynamically inserted podcast ads work: servers splice ads into MP3s based on IP address/user agent and other correlated data, but podcast apps themselves reveal only minimal metadata. Apple software bugs, notifications, and update timing: They revisit the December 2017 iPhone springboard crash caused by local notifications and Apple’s decision to rush out iOS 11.2. They also criticize noisy logs and the recurring 'month 13' console message on macOS. Forecast launch: Marco’s podcast production app: Marco announces Forecast, a free macOS tool for encoding MP3 podcasts, generating chapters, and supporting hidden chapters. He explains the technical stack, the free model, and why he built it outside the Mac App Store.
Key Arguments: Year-month-day is best for filenames and machine sorting because it is unambiguous and sorts correctly across years, but display formats can reasonably vary by region and user habit. Fahrenheit is defended as the most intuitive scale for ambient air temperature because 0 is cold and 100 is hot; Celsius is acceptable for science but not everyday weather. Responsible disclosure is useful, but public disclosure can force vendors to fix bugs faster; the best path is not always clear-cut. Apple’s Mac and iOS bugs around date/time and notifications suggest a deeper QA problem, especially because these issues keep recurring across releases. Dynamic podcast ads are not based on the podcast app knowing much about the listener; they rely on server-side ad splicing plus cross-platform tracking/correlation from IP and other data sources. The iPhone notification crash showed that turning a phone off can be safer than changing the system date, because changing the clock can create sync and data-integrity problems. Apple’s habit-changing features are often worth resisting if old workflows still work and the cost of switching is high; defaults are not inherently superior. Forecast was made free because the likely paid market was small, support burden would be high, and broader adoption benefits the podcast ecosystem and Overcast features.
Data Points: Date standard: ISO 8601 / year-month-day - Recommended for filenames and machine sorting because it is unambiguous and lexicographically sortable. Daily use assumption: 90% - One speaker says in day-to-day computer use, the current year is known by context about 90% of the time. Touch Bar laptop year: 2017 - John refers to his 2017 Touch Bar MacBook Pro when discussing the Touch Bar and keyboard settings. Photos library size saved: 50 GB - The iPhone storage manager claimed enabling iCloud Photo Library would save about 50 gigabytes. iPhone storage capacity: 128 GB - John discovers his iPhone 7 is the 128 GB model and fills it with photos and music. Auto-encoding time: 4–5 minutes - Marco says encoding an episode via command line originally took roughly four or five minutes. Podcast market estimate: ~100 paid customers - Marco estimates a paid version of Forecast would only attract around 100 customers. iOS bug timing: December 2 / around midnight - The notification-related crash was tied to crossing into December 2nd in certain time zones. Update release: iOS 11.2 - Apple expedited this release to address the iPhone springboard crash bug. Potential update cadence: Once a day - Marco describes Sparkle-based Mac app update checks as happening daily or at launch.
Pivotal Quotes: "Absolutely, all of your feelings and feedback around the MacBook you use, we couldn't want to listen more. And we hear, boy, do we hear." — Johnny Ive (quoted in discussion): Used to support the claim that Apple was aware of complaints about its current MacBook/MacBook Pro designs. "The reason why this is better is that it is completely unambiguous because nowhere ever uses year, day, month." — Marco: Explaining why year-month-day is superior for file names and globally readable dates. "The good thing is that it can't ever get as bad as web tracking." — Marco: Describing podcast ad targeting limits compared with the far more invasive tracking possible on the web.
Implications: The episode reinforces a theme of pragmatic computing: defaults and standards should serve real workflows, not ideology. It also highlights how Apple’s ecosystem choices—bugs, logging, storage management, and hardware design—shape both user trust and developer behavior.