Episode Summary
Executive Summary: The episode centers on Apple’s documentation gap, Swift’s improving diagnostics, and the rumored 16-inch MacBook Pro, with a broader discussion of tech companies converging on similar products. The hosts praise a pie-hole shortcut, critique Microsoft’s progress UI, debate Apple’s priorities and laptop design stagnation, and answer listener questions on processors, CarPlay, and Destiny’s evolving business model.
Main Topics: Pie Hole shutdown tools and workflow fix: The hosts follow up on a shortcut/workflow that can temporarily disable Pi-hole on demand. They explain a hostname/firewall issue that prevented it from working and note a community app alternative. Progress indicators and Microsoft’s experimental UI: They discuss a Microsoft-designed progress visualization that tries to convey throughput rather than just a filling bar, but argue it adds complexity without fully solving the basic UX problem. Swift diagnostics and better compiler errors: A Swift.org post on new diagnostic architecture is examined as a meaningful step toward more actionable compiler errors, especially for SwiftUI, though the hosts think more semantic work is still needed. Apple documentation quality and NoOverviewAvailable: The hosts react strongly to a third-party site measuring Apple framework documentation coverage, arguing that Apple’s public APIs—especially older and newer ones—remain under-documented and that this reflects a deeper organizational priority problem. Rumored 16-inch MacBook Pro and the state of Mac laptops: They dissect rumors/images of the 16-inch MacBook Pro, expecting a scissor-switch keyboard with an Escape key but little else changed, and debate whether Apple is doing the minimum fix versus a broader laptop redesign. Tech ecosystems and platform convergence: A comparison of Google, Amazon, Microsoft, and Apple shows how all major tech companies now ship similar hardware categories (earbuds, smart speakers, routers, controllers), raising questions about duplication, competition, and walled gardens. Listener Q&A: processors, CarPlay, and Destiny: Advice is given on choosing Macs based on workload, using wired versus wireless CarPlay, and how Destiny’s seasonal model reflects broader game-industry monetization and content-management trends.
Key Arguments: Pi-hole can now be conveniently disabled via a shortcut, but the initial failure was due to using a hostname that routed through an unforwarded admin port; an IP address fixed it. Microsoft’s progress indicator is clever but overdesigned; more data does not necessarily produce a better user experience. Swift’s improved diagnostics are not just better wording; they require compiler changes that preserve more metadata and continue compilation to produce actionable errors. SwiftUI error messages may improve somewhat, but the framework’s nested-function architecture still makes many errors hard to interpret in plain language. Apple’s documentation situation is bad enough that a third-party site can materially expose the problem; the issue is not technical impossibility but organizational will. The hosts argue Apple should publish its own documentation coverage metrics to motivate change internally and externally. The rumored 16-inch MacBook Pro appears likely to be a minimally revised version of the existing design, focused on fixing the keyboard rather than rethinking the product. Apple laptops have stagnated compared with other platforms; the hosts want a more ambitious “Mac Pro moment” for laptops with better ports, layout, cooling, and flexibility. Other big tech firms all ship overlapping product ecosystems, but Apple’s hardware/software focus makes quality and innovation in its devices especially important. For Mac processor selection, watching whether an app saturates multiple CPU bars in Activity Monitor is the practical way to tell whether more cores will help. For CarPlay, plugging in is inconvenient but not terrible; wireless CarPlay is desirable, but wired CarPlay still works well for navigation and messaging. Destiny’s evolving season-based structure is framed as a response to both content bloat and the need to keep players from falling hopelessly behind while preserving monetization. The current game industry increasingly relies on recurring seasonal content and managed progression rather than simple one-time boxed sales.
Data Points: Pi-hole disable frequency: 10–20 times in the last almost month - One host described how often he had needed to temporarily disable Pi-hole while running it Pi-hole disable duration options: 30 seconds or 5 minutes - The shortcut/workflow can turn Pi-hole off for short intervals Apple docs site name: nooverviewavailable.com - A third-party site surveying Apple developer documentation coverage Audio Toolbox Markov documentation coverage: 48.9% - Example mentioned while discussing poor documentation coverage in Apple frameworks Kernel public symbols: 28,000 symbols with only 2,000 documented - Used to illustrate why raw documentation ratios can be misleading for internal/private APIs MacBook Pro rumored travel: 1 mm vs 0.5 mm - Discussion of the rumored scissor-switch keyboard versus the butterfly keyboard iPhone model referenced: i11 Pro - A speaker referred to their current iPhone as the i11 Pro in casual conversation CarPlay listener use case: 5 miles or less / about 10 minutes - Typical short trips used to explain why plugging in is often unnecessary DoorDash promotion: $5 off first order of $15 or more - Ad read for new users using promo code ATP Linode promotion: $20 credit with promo code ATP2019 - Ad read for new users at linode.com/ATP Linode entry plan: $5/month - Mentioned as an example of the low-cost hosting tier Google documentation example: 2019-era/10.15.1 beta references - The rumored MacBook Pro image was discussed as appearing in a beta/system asset Destiny pricing model: $60 boxed-game legacy transitioning to seasons - The discussion contrasted old upfront purchase models with seasonal ongoing content Destiny legacy scale issue: Hundreds of gigabytes - Used to explain why endlessly adding content to one game becomes unwieldy BMW model note: 2020 - The 3GT/5GT discussion mentioned BMW discontinuing the GT line for 2020 Chevy Bolt range: 238 miles - Compared with other EV options under consideration e-Golf range: 125 miles - Used to characterize the older-generation EV range class e-Golf acceleration: 0 to 60 in about 8.5 seconds - Referenced as a downside relative to the current vehicle under discussion Model 3 range: 300+ miles - Used to contrast Tesla’s EV advantage over competing cars Model 3 acceleration: 0 to 60 in 4.7 seconds - Mentioned while comparing EV options
Pivotal Quotes: "This has been the exit interview/slash funeral for these MacBook Pros." — Marco: A pointed summary of the long-running dissatisfaction with the 2016-era MacBook Pro design "We need Apple writing their own code against these new APIs and sharing it with us." — Marco: Argument that better documentation must be backed by practical sample code and tutorials "It feels like they hate us, honestly." — Marco: Description of how the Mac laptop lineup has felt to users over the last several years
Implications: Listeners should expect Apple to be judged increasingly on execution, not just brand loyalty: better compiler diagnostics, documentation, and laptop fixes are now baseline expectations. The broader industry is converging on similar product categories, making differentiation and polish even more important.