277: ‘Polish Stink Eye’ With John Moltz

Episode Summary

Executive Summary: The conversation ranges from a humorous family tech-support story to a broader critique of Apple’s design and software philosophy. The hosts discuss Larry Tesler’s anti-mode legacy, the shortcomings of iPad multitasking, Apple’s security and privacy defaults, Catalina’s file-system/UI inconsistencies, coronavirus-driven Apple supply concerns, a retail worker lawsuit, and the promise/limits of third-party default apps and Apple TV multi-user handling.

Main Topics: Family iPad troubleshooting and the absurdity of 'dark mode' confusion (Priority: 5/5): A long opening anecdote about helping the speaker’s mother fix an iPad brightness issue misdescribed as dark mode. The story becomes a comedic example of how nontechnical users interpret interface states and how hidden UI controls can confuse even experienced helpers. Larry Tesler’s legacy: anti-modes and user-centered design (Priority: 5/5): The hosts discuss Tesler’s death and reflect on his influence at Xerox PARC, Apple, and Newton. The key theme is his resistance to complex modes and his insistence that software should match how people actually think, not how programmers think. Apple iPad multitasking criticism (Priority: 5/5): The speakers argue that iPad multitasking is too modal, inconsistent, and hard to discover. They describe split-screen, multiple instances, merging Safari windows, and the general mismatch between the feature’s complexity and typical user behavior. Malware, antivirus, and Apple’s security model (Priority: 5/5): They examine a Malwarebytes report claiming rising Mac threats and push back against the implication that third-party antivirus is necessary. The hosts argue Apple’s built-in protections and notarization model handle most threats well, while third-party AV often adds friction or confusion. Catalina file-system and UI reliability issues (Priority: 4/5): A substantial critique of macOS Catalina focuses on misleading file-size reporting, hidden storage paths for podcasts, and delayed UI updates (like folder sizes). The hosts argue that user-visible state should never be wrong, even temporarily. Apple policy, defaults, and ecosystem competition (Priority: 4/5): They discuss possible Apple changes allowing third-party default apps for browser/mail/music and debate the pros/cons. The conversation also covers Apple Watch integration, HomePod, Spotify, and how Apple balances user choice with platform integrity. Apple business and product controversies (Priority: 4/5): Additional topics include Apple’s revised revenue outlook due to coronavirus, a California Supreme Court case over Apple Store employee bag checks and off-the-clock security time, and an Apple TV multi-user experience that fails to clearly show which account is active.

Key Arguments: Larry Tesler’s core insight was that software should avoid unnecessary modes and reflect human behavior rather than programmer expectations. iPad multitasking is overly modal and inconsistent: launching, switching, and merging app instances use different gestures and hidden paths. Apple’s built-in security and notarization are generally sufficient for most Mac users; third-party antivirus often causes more problems than it solves. Mac malware today is mostly scamware/adware and social-engineering based, not classic self-spreading viruses. Catalina’s UI should never show stale or incorrect file-system information; wrong numbers undermine trust in the platform. Apple may be justified in controlling default apps and deep system integrations to avoid third-party abuse, but that creates real competitive and user-choice tensions. Apple TV’s multi-user system is too hidden and should more clearly display and preserve the active user, especially in a family/shared-device context. Apple’s retail security policy may be understandable in intent, but making employees wait off the clock is legally and reputationally indefensible.

Data Points: Podcast prep delay: 2 hours 15 minutes - Opening joke about how long the recording was delayed because of a furniture delivery and a coffee run. Coffee shop trip: 5 minutes - Estimated time to get coffee for Amy, contrasted with the actual delay caused by the mom’s iPad call. Temperature: Negative 43°F (claimed), then 36°F / feels like negative 40 - Comedic exaggeration about Philadelphia weather during the discussion. Larry Tesler age at death: 74 - Referenced while discussing his obituary and legacy. Mac malware bytes report claim: More than 400% year-over-year increase - A cited statistic from Malwarebytes’ 2020 Mac threat report. Threats per endpoint claim: Nearly 2 to 1 vs. Windows - Malwarebytes’ report suggested Mac threats outpaced Windows in their dataset. HomePod math limitation example: $500 divided by 12 - A Siri/HomePod calculation failed because currency language was included. Apple retail wait time: Upwards of 20 minutes - Employees allegedly waited in security lines after clocking out. Podcasts missing episodes: 4 episodes - The Catalyst Podcasts app displayed missing episodes 245–248. Catalina hidden container path: 243LU875E5.groups.com.apple.podcasts - The group container directory identified as storing Podcast app data. Default app discussion: 4 categories (web, mail, contacts, calendar) plus music/HomePod - The hosts distinguish URL-handler defaults from Siri/HomePod music defaults.

Pivotal Quotes: "If she would just try. You could figure it out." — John Gruber: A remark about the speaker’s mother and her lack of confidence using computers, despite being smart. "It’s very modal and I think it gets to the sort of heart of Tesler’s life’s work arguing against modes." — John Gruber: Explaining why iPad multitasking feels contrary to Larry Tesler’s design philosophy. "It’s so fundamentally wrong because it casts doubt on the integrity of your file system." — John Gruber: Criticizing Catalina for showing stale or incorrect storage information in the UI.

Implications: The episode reinforces a core Apple theme: great platforms depend on clarity, trust, and sensible defaults. When Apple hides complexity too deeply or shows misleading state, it erodes user confidence and weakens the very usability advantage it built.