272: ‘The Save Twitch’ With Rich Siegel

Episode Summary

Executive Summary: A wide-ranging interview with Bare Bones founder Rich Siegel centers on BBEdit 13’s evolution, the enduring relevance of plain text, dark mode and accessibility, robust autosave/recovery, grep tooling, customer support, documentation, AppleScript and Unix scripting concerns, and the constraints of the Mac App Store subscription model. The conversation also reflects on Apple’s pro hardware direction and the tension between security, usability, and developer needs.

Main Topics: BBEdit’s longevity and text-centric design (Priority: 5/5): Siegel explains BBEdit’s origin in the early Mac era and why it remains relevant: text underlies software, the web, scripting, and modern infrastructure. The app’s core mission—handling plain text as data rather than styled document content—has stayed stable across decades. Dark mode and accessibility (Priority: 5/5): The discussion covers BBEdit’s long-standing support for configurable color schemes, its adaptation to system dark mode, and how dark UI can be an accessibility necessity, not just an aesthetic preference. The host shares a personal example involving cataracts. Pattern Playground and grep usability (Priority: 4/5): BBEdit 13’s Pattern Playground makes regular expressions more understandable by showing matches, groups, and replacements in real time. It lowers the barrier for beginners while also speeding iterative debugging for advanced users. Autosave, recovery, and reliability (Priority: 5/5): The host recounts losing access to a BBEdit document when an external SSD was unplugged, only to find the full article recovered intact. This reinforces BBEdit’s design emphasis on resilience and user trust. AppleScript, Unix tooling, and platform security (Priority: 4/5): The conversation explores AppleScript’s unusual internals, the persistence of Apple events, and Apple’s apparent discomfort with scripting layers and cross-app IPC from a security standpoint. The speakers speculate on the future of bundled Unix scripting languages on macOS. Support, documentation, and release notes (Priority: 4/5): Siegel describes Bare Bones’ customer-support culture and how it grew from early hands-on tech support. The importance of clear manuals, release notes, and customer-facing commit messages is emphasized as part of product quality. Mac App Store economics and pro hardware gaps (Priority: 4/5): They discuss the limitations of App Store pricing and subscriptions versus traditional upgrade sales, plus concerns that Apple’s hardware lineup leaves a gap between the Mac mini and the new Mac Pro for enthusiast/pro users.

Key Arguments: Plain text remains the common substrate of modern computing; as long as software, web, and scripting are text-based, BBEdit stays relevant. BBEdit’s endurance comes from craftsmanship, restraint, and focusing on the needs of people who edit text professionally. Dark mode is not only a style choice; it can be a real accessibility feature for users with vision issues or harsh lighting. Reliable autosave and recovery are essential because crashes, sleep failures, and external-drive mishaps still happen. Regular expressions benefit from interactive, visual tooling because they are effectively a form of programming and deserve live feedback. Customer support and documentation are integral to product quality, not afterthoughts, especially for independent software companies. AppleScript and Unix scripting remain useful but occupy a precarious place due to Apple’s security priorities and changing platform direction. The Mac App Store’s model forces subscriptions where traditional paid upgrades would better fit BBEdit’s business and user expectations. Apple’s pro hardware has improved, but the lineup still lacks a compelling middle-ground standalone desktop for many enthusiasts and developers.

Data Points: Episode number: 272 - The host notes this as the first guest episode involving a former employer. BBEdit first commercial release: 2.5 - Siegel says the first commercial version shipped in May 1993. Uses This interviews: 1040 - The host cites Daniel Bogan’s Uses This site as having 1040 interviews. BBEdit public release year: 1993 - First commercial version of BBEdit shipped in May 1993. Mac OS X dark appearance support: 10.13 - Siegel describes early dark appearance support before the full system dark mode in 10.14. User-visible dark mode in macOS: 10.14 - The host notes 10.14 as the first OS with a user-visible dark mode. Migration time: 7 hours - The host recounts a machine migration that estimated seven hours and was run overnight. Mac Pro repairability score: 9/10 - The host references iFixit’s teardown score for the new Mac Pro. New Mac Pro max configuration: $52,000 - Discussed as evidence of Apple’s professional hardware commitment. New Mac Pro starting price: $6,000 - Used to illustrate the gap between Apple’s pro desktop and a more affordable standalone workstation. Host’s preferred computer price point: $4,400 - The host says this has been his “mystical, magical sweet spot” across multiple purchases. Casper trial length: 100 nights - Mentioned in the sponsor read for Casper mattresses. Squarespace discount: 10% - Mentioned as the discount when using code TALKSHOW. BBEdit evaluation period: 30 days - Siegel notes BBEdit offers a full evaluation period before free mode limitations apply.

Pivotal Quotes: "Underneath it all, there has always been text." — Rich Siegel: Explaining BBEdit’s long-term relevance across programming, the web, and modern tooling. "If you look at something and you think, yeah, I could do that, go ahead and do it." — Rich Siegel: On creative confidence and why BBEdit and software craftsmanship endure. "It is hugely important that when, as an engineer, you're writing commit notes, you must write them for the customer to read." — Rich Siegel: On documentation and change notes as a customer-facing product feature.

Implications: The episode underscores why pro software still matters: durable tools, transparent docs, and trustworthy recovery features build long-term loyalty. It also highlights ongoing tension between Apple’s security-first policies and the needs of developers, power users, and independent Mac software vendors.