Episode Summary
Executive Summary: The episode covered a wide-ranging set of Apple and tech topics: cleaning up legacy Mac installs, Apple Silicon DTK refunds, watch and iPhone OS quirks, SSD wear concerns, virtualized Linux/Docker workflows for M1, Tesla touchscreen recall and self-driving skepticism, new Siri default-app controls, Apple’s headset/display strategy, workplace device management, and listeners’ personal media archives. The hosts repeatedly emphasized usability, control, and the risks of relying on brittle software or overreaching corporate systems.
Main Topics: Mac maintenance, legacy installs, and launch agents: Marco describes how old macOS installations accumulate cruft, break over time, and require deeper cleanup than simply trashing apps. Launch Control and launch agents are discussed as tools for finding dormant system baggage, especially on upgraded Catalina/Big Sur systems. Apple Silicon DTK refund revision: Apple’s revised developer transition kit return offer becomes much better: a full $500 credit, usable on any Apple product through year-end, replacing the earlier restrictive $200 credit. The hosts praise the correction as an unusually good developer-relations move. iOS/watchOS feature gaps and usability: Discussion of iOS 14.5 watch-unlock behavior, Siri’s default music service support, and the Apple Watch timer/always-on-screen shortcomings. The hosts argue Apple’s devices still behave too much like constrained, app-siloed products instead of flexible computers. SSD endurance and write-volume concerns: The hosts examine SSD write totals on M1 and Intel Macs, comparing terabytes written and daily write averages. They conclude that normal laptop usage writes a surprising but not alarming amount, and that swap is unlikely to be the practical SSD-lifetime problem people fear. Local dev environments on M1 and virtualization: A listener asks for a stable way to run local PHP/MySQL/Nginx workloads on M1 Macs. The responses compare Homebrew, standard VMs, virtualization frameworks without kexts, and Docker, emphasizing portability and the desire for an isolated Linux environment that survives macOS changes. Tesla touchscreens, recalls, and self-driving skepticism: The conversation covers Tesla’s touchscreen failure recall, the safety implications of rebooting a car while driving, and broader skepticism that full self-driving is near or that Tesla’s development culture is suited to safety-critical autonomy. App Store ethics and keyword abuse: The hosts criticize using competitors’ names in app keywords and especially in descriptions, calling it dishonest even when it may be common practice. They argue for staying on the honorable side of App Store optimization and avoiding tactics that could trigger rejection.
Key Arguments: Old macOS installations tend to rot over time, especially after Catalina, so cleaning launch agents and removing legacy binaries is often necessary; simply dragging apps to the Trash is insufficient. Apple’s revised DTK refund is unusually generous and responsive for a small developer program, showing better-than-expected developer relations after an initial misread of the room. Apple Watch and iPhone features still often hide useful live status behind blurry or awkward UI states instead of treating timers, workouts, and defaults as first-class system information. SSD write totals look high in isolation, but normal laptop workloads rarely threaten SSD lifespan before other performance or reliability issues become obvious. For local server development on M1, the real need is an isolated, reproducible Linux environment that can mount Mac files while avoiding kexts and surviving OS updates; VMs or Docker are better fits than ad hoc Homebrew setups. Tesla’s mix of reboot-prone infotainment and ambitious autonomy goals is a poor fit for safety-critical self-driving, because the discipline required for full autonomy is very different from convenience features like Autopilot. Using competitor names in search keywords or descriptions is dishonest, risks App Review trouble, and undercuts trust even if it can improve discoverability. Personal and corporate device boundaries matter: if an employer wants profile-based control, employees should know exactly what can be monitored and consider using a separate work phone if possible.
Data Points: DTK refund: $500 - Apple’s revised return credit equals the original purchase price of the developer transition kit Old DTK offer: $200 credit with May 31 expiration - Earlier, more restrictive Apple offer that listeners and developers criticized DTK redemption window: Through the end of the year - Revised credit can be applied to any Apple product until year-end Concert length: About 6 hours - The user’s archived Concert for Charlottesville recording Mac install history: 3 desktop installations since 2004 - Marco describes how few clean macOS installs he has used over decades SSD writes: 13.4 TB written in two months - M1 MacBook Air example from a Twitter thread SSD write rate: 223 GB/day - Computed from the M1 Mac example discussed on the show Internal SSD writes: 246 TB written - Marco’s 2017 MacBook Pro lifetime smartctl result Work laptop write rate: 197 GB/day - Calculated from total writes over the machine’s life Another laptop write rate: 847.2 GB/day - John’s recomputed value from his machine’s SSD stats Power-on hours: 1,295 hours - John’s SSD health figures while discussing drive wear Controller busy time: 21,799 - Marco’s SSD health statistic, unit unspecified in discussion Unsafe shutdowns: 160 - Marco’s SSD health report Data integrity errors: 0 - Marco’s SSD health report showed no errors Power cycles: 26,000 - Marco’s SSD health report; speakers note the value likely reflects something other than manual reboots Alerted work on Apple Watch: 5-minute timer example - Used to illustrate the timer/live display issue on the watch
Pivotal Quotes: "this is a note from one company saying, no, never mind, we're going to double it." — Casey: Reaction to Apple revising the DTK return credit upward after criticism "it feels like Windows." — Marco: Describing how Catalina-era macOS installations accumulate rot and problems over time "why, why is this smart computer watch so dumb?" — Marco: Frustration over Apple Watch timer behavior and always-on display limitations
Implications: Listeners are encouraged to keep systems clean, choose stable dev environments, question overreaching employer profiles, and remain skeptical of safety-critical software promises. The episode also suggests Apple is improving developer relations and platform openness, though slowly and inconsistently.