Episode Summary
Executive Summary: The episode centers on three big threads: John’s long-running Mac window-layering preference and the surprisingly positive listener response to it; a deep technical debate about Marco’s attempts to replace a PHP feed crawler with Node, then Go; and Apple’s App Store/App Review direction, including a developer survey and the broader chilling effect on watch app enthusiasm. The hosts also revisit iPad form factors and use cases, concluding the Air 2 restores the iPad as a strong leisure/browsing device.
Main Topics: Mac window layering policies and old-school window management: John explains the classic Mac OS behavior he still prefers: clicking a window should bring all windows from that app forward, with modifier clicks used to isolate a single window. He argues this is essential to how he manages many open windows and notes listeners largely agreed or were intrigued. SSL on brochureware sites and injection protection: The discussion revisits why even simple sites might use HTTPS: to prevent ad injection, tracking insertion, and man-in-the-middle manipulation on hostile networks or within corporate environments. SSL is framed as useful but not a complete security solution. Marco’s programming-language search: Node, PHP, Go, and language philosophy: Marco describes trying Node for a large-scale feed crawler to replace an inefficient PHP process farm, but hitting memory leaks and other issues. The conversation expands into a broader debate over language simplicity, abstraction, generics, and whether Go, Perl, C#, or Swift are better long-term fits. Apple App Store survey and App Review culture: The hosts examine a broad Apple developer survey that appears to be marketing-driven, especially a question listing push notifications as a marketing channel. They debate whether the survey reflects internal uncertainty or just routine data gathering, and then pivot to Apple’s App Review tone and lack of public accountability. WatchKit, developer morale, and Apple’s future relationship with developers: They argue Apple’s recent rejection behavior and restrictive policies risk chilling enthusiasm just as Apple needs developers excited about the Watch. The concern is that big brands may show up, but smaller developers generate the most interesting and innovative apps. iPad Air 2, the mini, and the device’s proper role: The final segment revisits whether the iPad is worth owning, comparing full-size iPads, the mini, and the Air 2. The consensus is that the Air 2’s lightness and speed make it the best current iPad for reading, browsing, gaming, and lounging, though not as a work machine.
Key Arguments: John’s window-layering utility restores an older Mac behavior where clicking one app window brings all windows from that app forward, which fits his workflow better than the default OS X behavior. Listener feedback strongly validated John’s window-management approach; most responses said it matched how they already work or wanted to try it. SSL can protect even simple informational websites from ad injection, tracking, and traffic tampering on hostile Wi‑Fi or corporate networks. Marco’s Node experiment failed mainly because of memory leaks and runtime weirdness, not because the crawler logic itself was wrong; he does not want to invest in a platform that feels fundamentally unreliable. Marco prefers languages that are simple, readable, and low-magic; he dislikes languages and frameworks that encourage clever abstractions, callback-heavy code, or hard-to-trace behavior. The hosts disagree on whether language features like generics and metaprogramming are empowering or harmful; Marco sees them as maintenance risks, while Casey sees them as precision and expressiveness. Apple’s developer survey looks like marketing research more than policy reform; it seems designed to measure app discovery/marketing behavior rather than address App Store pain directly. App Review’s tone and decisions matter because Apple increasingly depends on developers to make the Watch and iPad compelling, and current hostility may suppress that enthusiasm. The iPad is most compelling as a leisure and consumption device—reading, browsing, games—not as a replacement for a phone or as a primary work machine. The iPad Air 2’s lighter weight, speed, and screen improvements make the full-size iPad feel newly viable again, while the mini’s portability is not enough to offset its compromises for some users.
Data Points: Safari windows open: 19 - Used as an example of how many browser windows John keeps open and actively manages. PHP crawler processes: 240 - Current crawler architecture for Overcast uses many PHP processes pulling jobs from a queue. Feeds crawled: ~250,000 - Scale of the Overcast feed crawler that Marco is trying to support. Crawl frequency: No less than once an hour each; popular feeds every few minutes - The crawler has to schedule frequent fetches depending on feed popularity. Node version mentioned: 0.10.35 - Referenced to suggest Node was still pre-1.0 and immature. Memory use in Node test: Over 1 GB in about 20 minutes - Marco reported the Node implementation leaking heavily even when crawling only an eighth of the feeds. T-Mobile trial data: 200 MB per month - Mentioned as a low-cost cellular option for iPad users. iPad Air 2 pricing example: $15 starter set / $8 per month / $10 per image / 10% off with code ATP - Promotional numbers from the mid-episode ad copy for sponsors, included here because they were explicitly stated in the transcript. Harry’s starter set: $15 shipped - Sponsor offer for a razor, shave cream or gel, and three blades. Fracture discount: 20% off with code ATP - Sponsor offer for glass-printed photos. Squarespace starting price: $8 per month - Sponsor offer for website hosting and design. The iPad Air 2 speed upgrade: 2 GB RAM and triple-core chip - Cited as a major reason the Air 2 felt dramatically better than prior full-size iPads. Apple survey length: ~20 screens - The developer survey was described as long and marketing-heavy. Developer feedback sample size: 7 survey emails - Marco said he received seven copies of the survey.
Pivotal Quotes: "If I click any Safari window, all the Safari windows come to the front." — John: Explaining the classic Mac-style window layering utility he still uses. "I just don’t respect it as a language." — Marco: His assessment of JavaScript while discussing why Node was not a good long-term fit. "God, are they working hard to suck the fun out of it?" — John: Summarizing his frustration with Apple’s App Store/App Review climate.
Implications: The episode suggests that workflow preferences, language tooling, and platform policy all shape developer loyalty. Apple’s treatment of developers may affect Watch/iPad adoption, while Marco’s search underscores the need for mature, low-magic tools for large-scale backend tasks.