Congratulations!

[Valid Atom 1.0] This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://daringfireball.net/index.xml

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <feed xmlns="http://www.w3.org/2005/Atom">
  3. <title>Daring Fireball</title>
  4. <subtitle>By John Gruber</subtitle>
  5. <link rel="alternate" type="text/html" href="https://daringfireball.net/" />
  6. <link rel="self" type="application/atom+xml" href="https://daringfireball.net/feeds/main" />
  7. <id>https://daringfireball.net/feeds/main</id>
  8.  
  9.  
  10. <updated>2026-06-09T21:33:17Z</updated><rights>Copyright © 2026, John Gruber</rights><entry>
  11. <title>Apple OS 27: The Small Things</title>
  12. <link rel="alternate" type="text/html" href="https://blog.oneberri.com/posts/wwdc26-the-small-things" />
  13. <link rel="shorturl" type="text/html" href="http://df4.us/x9f" />
  14. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/09/the-small-things" />
  15. <id>tag:daringfireball.net,2026:/linked//6.43107</id>
  16. <published>2026-06-09T21:29:57Z</published>
  17. <updated>2026-06-09T21:33:17Z</updated>
  18. <author>
  19. <name>John Gruber</name>
  20. <uri>http://daringfireball.net/</uri>
  21. </author>
  22. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  23. <p>Rishi Ó:</p>
  24.  
  25. <blockquote>
  26.  <p>My favorite Apple updates are not the flashy new features, but the quiet little touches: annoyances fixed, workflows made smoother, rough edges sanded down, and longstanding flaws thoughtfully reworked. To me, they’re the clearest sign of a company that cares about its craft.</p>
  27.  
  28. <p>Here’s a collection from a WWDC26 screen-grab, organized for easier reading, on improvements coming later this year.</p>
  29. </blockquote>
  30.  
  31. <p>That’s a lot of bullet points.</p>
  32.  
  33. <div>
  34. <a  title="Permanent link to ‘Apple OS 27: The Small Things’"  href="https://daringfireball.net/linked/2026/06/09/the-small-things">&nbsp;★&nbsp;</a>
  35. </div>
  36.  
  37. ]]></content>
  38.  </entry><entry>
  39. <title>The Talk Show Live From WWDC: Tonight, In-Person and Streaming</title>
  40. <link rel="alternate" type="text/html" href="https://ti.to/daringfireball/the-talk-show-live-from-wwdc-2026" />
  41. <link rel="shorturl" type="text/html" href="http://df4.us/x9e" />
  42. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/09/the-talk-show-live-tonight" />
  43. <id>tag:daringfireball.net,2026:/linked//6.43106</id>
  44. <published>2026-06-09T18:53:47Z</published>
  45. <updated>2026-06-09T18:55:12Z</updated>
  46. <author>
  47. <name>John Gruber</name>
  48. <uri>http://daringfireball.net/</uri>
  49. </author>
  50. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  51. <p>If you can make it in person, you should come. The California Theater is a beautiful <em>big</em> theater and tickets <a href="https://ti.to/daringfireball/the-talk-show-live-from-wwdc-2026">are still available</a>.</p>
  52.  
  53. <p>You can <em>also</em> watch tonight’s show in live stereoscopic immersive in the <a href="https://apps.apple.com/us/app/theater-cinema-events/id6502666560">Theater app from Sandwich Vision</a> on Vision Pro. A purchase of the ticket to the live show, the Theater app for $12.99, is also good for replay forever — with surprise bonus features included. It’s a fun, truly immersive way to experience the show.</p>
  54.  
  55. <p>Hope to see you there tonight, one way or the other.</p>
  56.  
  57. <div>
  58. <a  title="Permanent link to ‘The Talk Show Live From WWDC: Tonight, In-Person and Streaming’"  href="https://daringfireball.net/linked/2026/06/09/the-talk-show-live-tonight">&nbsp;★&nbsp;</a>
  59. </div>
  60.  
  61. ]]></content>
  62.  </entry><entry>
  63. <title>Apple WWDC 2026 Keynote</title>
  64. <link rel="alternate" type="text/html" href="https://www.youtube.com/watch?v=hF8swzNR1-o" />
  65. <link rel="shorturl" type="text/html" href="http://df4.us/x9d" />
  66. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/09/apple-wwdc-2026-keynote" />
  67. <id>tag:daringfireball.net,2026:/linked//6.43105</id>
  68. <published>2026-06-09T17:42:32Z</published>
  69. <updated>2026-06-09T17:42:32Z</updated>
  70. <author>
  71. <name>John Gruber</name>
  72. <uri>http://daringfireball.net/</uri>
  73. </author>
  74. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  75. <p>A brisk 76 minutes, including the post-credits Easter egg music video. The past few years ran about a half hour longer.</p>
  76.  
  77. <div>
  78. <a  title="Permanent link to ‘Apple WWDC 2026 Keynote’"  href="https://daringfireball.net/linked/2026/06/09/apple-wwdc-2026-keynote">&nbsp;★&nbsp;</a>
  79. </div>
  80.  
  81. ]]></content>
  82.  </entry><entry>
  83. <title>Apple’s WWDC AI Demos Were Real and in Real Time</title>
  84. <link rel="alternate" type="text/html" href="https://techcrunch.com/2026/06/08/apples-wwdc-ai-demos-looked-more-real-after-250m-false-ad-settlement/" />
  85. <link rel="shorturl" type="text/html" href="http://df4.us/x9c" />
  86. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/09/apple-wwdc-demos" />
  87. <id>tag:daringfireball.net,2026:/linked//6.43104</id>
  88. <published>2026-06-09T17:38:21Z</published>
  89. <updated>2026-06-09T17:38:22Z</updated>
  90. <author>
  91. <name>John Gruber</name>
  92. <uri>http://daringfireball.net/</uri>
  93. </author>
  94. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  95. <p>Julie Bort, TechCrunch:</p>
  96.  
  97. <blockquote>
  98.  <p>But the most telling detail wasn’t what Apple announced. It was
  99. how it chose to show some things off. Many of the Apple
  100. Intelligence demoes featured someone standing, phone in hand,
  101. pressing buttons or using voice commands in real time, while
  102. another camera showed off the phone’s response.</p>
  103.  
  104. <p>These weren’t live onstage, anything-could-go wrong demos; they
  105. were pre-taped. But they looked far more like proof of working
  106. features than what Apple showed at WWDC 2024, when the company
  107. <a href="https://techcrunch.com/2024/06/13/everything-apple-announced-wwdc-2024/">unveiled Apple Intelligence and a new Siri</a> to the world
  108. through slickly produced videos that turned out to be more promise
  109. than product.</p>
  110. </blockquote>
  111.  
  112. <p>The demos were all shot in single takes, with no editing. In fact, I think most of them were single takes of multiple demos back-to-back. That’s the way it should be, even when they feel a little slow. When a demo feels slow, the solution isn’t to edit the video — it’s to make the feature work faster.</p>
  113.  
  114. <div>
  115. <a  title="Permanent link to ‘Apple’s WWDC AI Demos Were Real and in Real Time’"  href="https://daringfireball.net/linked/2026/06/09/apple-wwdc-demos">&nbsp;★&nbsp;</a>
  116. </div>
  117.  
  118. ]]></content>
  119.  </entry><entry>
  120. <title>Apple Introduces Siri AI</title>
  121. <link rel="alternate" type="text/html" href="https://www.apple.com/newsroom/2026/06/apple-introduces-siri-ai-a-profoundly-more-capable-and-personal-assistant/" />
  122. <link rel="shorturl" type="text/html" href="http://df4.us/x9b" />
  123. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/09/apple-introduces-siri-ai" />
  124. <id>tag:daringfireball.net,2026:/linked//6.43103</id>
  125. <published>2026-06-09T17:23:29Z</published>
  126. <updated>2026-06-09T17:46:12Z</updated>
  127. <author>
  128. <name>John Gruber</name>
  129. <uri>http://daringfireball.net/</uri>
  130. </author>
  131. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  132. <p>Apple Newsroom yesterday:</p>
  133.  
  134. <blockquote>
  135.  <p>This new version of Siri is built on Apple Intelligence, allowing
  136. Siri to draw on personal context understanding and help users find
  137. what they need in the moment across messages, emails, photos, and
  138. more. For example, users can ask Siri to find a restaurant
  139. recommendation a friend messaged them about, surface a hotel
  140. confirmation number from an old email, or pull up photos with
  141. friends and family from a recent trip. And personal context
  142. understanding extends to third-party apps when developers
  143. integrate with Spotlight.</p>
  144.  
  145. <p>With even more systemwide app actions, Siri AI lets users get
  146. things done across apps, like drafting an email from scratch, or
  147. editing and sharing a set of photos. Using onscreen awareness,
  148. Siri AI can answer questions related to the content on a user’s
  149. screen. For example, if a user gets a text about a potluck with
  150. friends, they can brainstorm with Siri on what to bring and then
  151. add a recipe to the Notes app.</p>
  152.  
  153. <p>In addition, Siri AI can use broad world knowledge to get
  154. up-to-date information from the web on virtually any topic and
  155. generate a helpful answer, such as when and where to see the next
  156. solar eclipse, or when a musician is coming to town. Users can
  157. extend almost any response from Siri into a rich conversation and
  158. ask follow-up questions.</p>
  159. </blockquote>
  160.  
  161. <p>I like the name “Siri AI”. “New Siri” wouldn’t have legs because eventually this won’t be new. This should be the dividing line between Siri as we know it and Siri as it should be. The demos I’ve seen so far (I still don’t have access on my iOS 27 testing device) are impressive. Well, impressive compared to old Siri. They’re table stakes for generative AI. But Siri AI is the only system that can draw upon your personal data in the apps on your devices, <em>and</em> perform actions based on the app intents supported by the apps on your devices. It is in some ways less capable than ChatGPT or Claude, but in other ways has more potential. It’s a very different approach and I think it’s the right one for Apple.</p>
  162.  
  163. <p>They need to execute, they need to prove this can scale, and most of all, they need to get third-party apps on board with <a href="https://developer.apple.com/videos/play/wwdc2026/345">App Intents</a> and <a href="https://developer.apple.com/videos/play/wwdc2026/240">App Schemas</a>. But it seems like they’re doing all of that. This is not a done deal but it is very realistic.</p>
  164.  
  165. <div>
  166. <a  title="Permanent link to ‘Apple Introduces Siri AI’"  href="https://daringfireball.net/linked/2026/06/09/apple-introduces-siri-ai">&nbsp;★&nbsp;</a>
  167. </div>
  168.  
  169. ]]></content>
  170.  </entry><entry>
  171. <title>Apple’s WWDC Announcement of the New Apple Intelligence System</title>
  172. <link rel="alternate" type="text/html" href="https://www.apple.com/newsroom/2026/06/apple-intelligence-brings-powerful-ai-capabilities-into-everyday-experiences/" />
  173. <link rel="shorturl" type="text/html" href="http://df4.us/x9a" />
  174. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/09/apples-wwdc-apple-intelligence-announcement" />
  175. <id>tag:daringfireball.net,2026:/linked//6.43102</id>
  176. <published>2026-06-09T16:50:33Z</published>
  177. <updated>2026-06-09T17:45:39Z</updated>
  178. <author>
  179. <name>John Gruber</name>
  180. <uri>http://daringfireball.net/</uri>
  181. </author>
  182. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  183. <p>Apple Newsroom:</p>
  184.  
  185. <blockquote>
  186.  <p>These new capabilities are powered by the next generation of Apple
  187. Foundation Models, custom-built in collaboration with Google and
  188. its Gemini models for deeply integrated Apple Intelligence
  189. experiences. These latest models run on device and on servers
  190. using Private Cloud Compute.</p>
  191.  
  192. <p>Every facet of the new Apple Intelligence architecture is built
  193. privacy-first, from the latest Apple Foundation Models to the core
  194. operating system technologies that integrate these models deep
  195. into Apple’s platforms. Apple Intelligence uses on-device
  196. processing and Private Cloud Compute to help protect users’
  197. privacy. Private Cloud Compute gives users access to
  198. frontier-level intelligence, while extending the privacy and
  199. security of iPhone into the cloud.</p>
  200. </blockquote>
  201.  
  202. <p>What’s confusing about this Apple-Google partnership is that Google pretty much calls all things AI “Gemini”. The models are “Gemini”, the assistant is “Gemini”, and the feature integrations are “Gemini”. So Apple is taking pains to emphasize that they’re building atop the Gemini <em>models</em>, not the Gemini <em>assistant</em>.</p>
  203.  
  204. <p>One way to think about it is this. Let’s say you’re a Google Gemini app user. That’s the assistant. Now you start using the new Apple Intelligence (that builds atop the Gemini models) and the new Siri AI (that builds atop the new Apple Intelligence). When you go back to the Google Gemini app, <em>nothing you did</em> using Apple Intelligence and Siri AI is visible to the Gemini app. And nothing you continue to do in the Google Gemini app is visible to Apple Intelligence or Siri AI.</p>
  205.  
  206. <div>
  207. <a  title="Permanent link to ‘Apple’s WWDC Announcement of the New Apple Intelligence System’"  href="https://daringfireball.net/linked/2026/06/09/apples-wwdc-apple-intelligence-announcement">&nbsp;★&nbsp;</a>
  208. </div>
  209.  
  210. ]]></content>
  211.  </entry><entry>
  212. <link rel="alternate" type="text/html" href="https://youtu.be/Dqp_b8GHLXU?t=1074" />
  213. <link rel="shorturl" href="http://df4.us/x99" />
  214. <link rel="related" type="text/html" href="https://daringfireball.net/feeds/sponsors/2026/06/workos_launches_authmd_--_an_o" />
  215. <id>tag:daringfireball.net,2026:/feeds/sponsors//11.43101</id>
  216. <author><name>Daring Fireball Department of Commerce</name></author>
  217. <published>2026-06-09T04:23:05Z</published>
  218. <updated>2026-06-09T04:23:05Z</updated>
  219. <content type="html" xml:base="https://daringfireball.net/feeds/sponsors/" xml:lang="en"><![CDATA[
  220. <p>Sign-up forms were built for humans in browsers, so how do AI agents programmatically register with services?</p>
  221.  
  222. <p>Enter auth.md. By exposing a single, machine-readable Markdown file at your service root, AI agents can dynamically discover your OAuth Protected Resource Metadata, parse required scopes, and authenticate seamlessly.</p>
  223.  
  224. <p>With native support in WorkOS AuthKit, you can now implement this protocol out of the box, giving AI tools a standardized, secure way to log into your application.</p>
  225.  
  226. <p>Read the <a href="https://workos.com/auth-md?utm_source=daringfireball&amp;utm_medium=newsletter&amp;utm_campaign=q22026">auth.md docs</a>.</p>
  227.  
  228. <div>
  229. <a  title="Permanent link to ‘WorkOS Launches auth.md — an Open Protocol for Agent Registration’"  href="https://daringfireball.net/feeds/sponsors/2026/06/workos_launches_authmd_--_an_o">&nbsp;★&nbsp;</a>
  230. </div>
  231.  
  232. ]]></content>
  233. <title>[Sponsor] WorkOS Launches auth.md — an Open Protocol for Agent Registration</title></entry><entry>
  234. <title>From the Annals of People Having Knowledge of the Matter, Siri AI Extensions Edition</title>
  235. <link rel="alternate" type="text/html" href="https://www.bloomberg.com/news/articles/2026-03-26/apple-plans-to-open-up-siri-to-rival-ai-assistants-beyond-chatgpt-in-ios-27" />
  236. <link rel="shorturl" type="text/html" href="http://df4.us/x98" />
  237. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/08/gurman-siri-ai-extensions" />
  238. <id>tag:daringfireball.net,2026:/linked//6.43100</id>
  239. <published>2026-06-09T01:37:27Z</published>
  240. <updated>2026-06-09T04:29:43Z</updated>
  241. <author>
  242. <name>John Gruber</name>
  243. <uri>http://daringfireball.net/</uri>
  244. </author>
  245. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  246. <p>Mark Gurman, reporting (?) for Bloomberg two short months ago:</p>
  247.  
  248. <blockquote>
  249.  <p>Apple Inc. plans to open Siri to outside artificial intelligence
  250. assistants, a major move aimed at bolstering the iPhone as an AI
  251. platform. The company is preparing to make the change as part of a
  252. Siri overhaul in its upcoming iOS 27 operating system update,
  253. according to people with knowledge of the matter. The assistant
  254. can already tap into ChatGPT through a partnership with OpenAI,
  255. but Apple will now allow competing services to do the same.</p>
  256.  
  257. <p>The company is developing new tools to allow AI chatbot apps
  258. installed via the App Store to integrate with the Siri assistant,
  259. said the people, who asked not to be identified because the plans
  260. haven’t been announced. The chatbots will also work with an
  261. upcoming Siri app and other features in the Apple Intelligence
  262. platform.</p>
  263.  
  264. <p>That means, for instance, if users have Alphabet Inc.’s Google
  265. Gemini or Anthropic PBC’s Claude installed, they’d be able to send
  266. queries to those services from within the Siri voice assistant,
  267. just like they have been able to with ChatGPT since Apple
  268. Intelligence launched in 2024.</p>
  269. </blockquote>
  270.  
  271. <p>Maybe Apple ran out of time today, and will announce this tomorrow? Maybe they forgot to announce it? Maybe they scrapped the next-generation Siri that existed two months ago and in the last month rebuilt another entirely new next-generation Siri? I’ll bet something like that is what happened.</p>
  272.  
  273. <p>I mean, people had knowledge of the matter.</p>
  274.  
  275. <div>
  276. <a  title="Permanent link to ‘From the Annals of People Having Knowledge of the Matter, Siri AI Extensions Edition’"  href="https://daringfireball.net/linked/2026/06/08/gurman-siri-ai-extensions">&nbsp;★&nbsp;</a>
  277. </div>
  278.  
  279. ]]></content>
  280.  </entry><entry>
  281. <title>Mux — Video for Developers</title>
  282. <link rel="alternate" type="text/html" href="https://www.mux.com/?utm_campaign=fireball&amp;utm_source=DF" />
  283. <link rel="shorturl" type="text/html" href="http://df4.us/x95" />
  284. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/07/mux" />
  285. <id>tag:daringfireball.net,2026:/linked//6.43097</id>
  286. <published>2026-06-08T01:47:03Z</published>
  287. <updated>2026-06-08T01:47:09Z</updated>
  288. <author>
  289. <name>John Gruber</name>
  290. <uri>http://daringfireball.net/</uri>
  291. </author>
  292. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  293. <p>My thanks to Mux for sponsoring last week at DF. Mux is what developers reach for when they need to do more with video. Video files are packed with data and context waiting to be unlocked.</p>
  294.  
  295. <p>Mux Robots are AI workflows that unlock that data inside your video for summarization, caption translation, moderation, and more. Configure once and your workflows run automatically on new uploads.</p>
  296.  
  297. <p>Mux is video infrastructure trusted by Patreon, Substack, and Synthesia. Start building for free. Use code <strong>FIREBALL</strong> at signup for an extra $50 credit.</p>
  298.  
  299. <div>
  300. <a  title="Permanent link to ‘Mux — Video for Developers’"  href="https://daringfireball.net/linked/2026/06/07/mux">&nbsp;★&nbsp;</a>
  301. </div>
  302.  
  303. ]]></content>
  304.  </entry><entry>
  305.    
  306.    <link rel="alternate" type="text/html" href="https://daringfireball.net/2026/06/swiftui_only_makes_it_easy_to_develop_bad_apps" />
  307. <link rel="shorturl" href="http://df4.us/x97" />
  308. <id>tag:daringfireball.net,2026://1.43099</id>
  309. <published>2026-06-08T01:30:00Z</published>
  310. <updated>2026-06-09T01:40:05Z</updated>
  311. <author>
  312. <name>John Gruber</name>
  313. <uri>http://daringfireball.net/</uri>
  314. </author>
  315. <summary type="text">Apple’s developer message used to be that it was not just easy to develop apps for their platforms, but that it was easy to develop good idiomatically native apps. That’s still true for AppKit and UIKit, but it’s never been true for SwiftUI, and SwiftUI is now seven years old.</summary>
  316. <content type="html" xml:base="https://daringfireball.net/" xml:lang="en"><![CDATA[
  317. <p>Paulo Andrade, last month, “<a href="https://pfandrade.me/blog/mac-assed-swiftui-app/">Using SwiftUI to Build a Mac-Assed App in 2026</a>”:</p>
  318.  
  319. <blockquote>
  320.  <p>I recently launched the macOS version of <a href="https://shopie.io/">Shopie</a>, an app I first
  321. released on the iOS App Store late last year. Shopie helps you
  322. keep track of products you’re interested in by letting you create
  323. wishlists and notifying you whenever a product’s price,
  324. availability, and other details change.</p>
  325.  
  326. <p>Unlike my other apps, where I typically blend AppKit (or UIKit)
  327. with SwiftUI, Shopie is built entirely in SwiftUI. I wanted to
  328. keep it that way to maximize code reuse across iOS, iPadOS, and
  329. now macOS. This post explores how far SwiftUI can take you on the
  330. Mac in 2026, especially if your goal is to build an app that feels
  331. truly native to the platform. It’s not meant to be an exhaustive
  332. review of SwiftUI on macOS. It’s simply a collection of recipes
  333. and issues I ran into while porting <a href="https://shopie.io/">Shopie</a>, a fairly small app,
  334. and keeping it 100% SwiftUI.</p>
  335. </blockquote>
  336.  
  337. <p>Andrade’s examples are copious. His conclusion is damning:</p>
  338.  
  339. <blockquote>
  340.  <p>Apple dropped the ball here. AppKit was ahead of its time and
  341. UIKit was a more polished version of AppKit. A serious
  342. cross-platform framework that unified the two should have happened
  343. long before SwiftUI. Instead, Apple left AppKit to fossilize and
  344. then tried to leapfrog the problem.</p>
  345.  
  346. <p>You can see the result everywhere. SwiftUI is productive, modern,
  347. and often delightful, right up until you try to make a really good
  348. Mac app. Then suddenly you’re fighting the framework for things
  349. the Mac solved 20 years ago.</p>
  350. </blockquote>
  351.  
  352. <p>There’s something really wrong with SwiftUI. Amongst the apps I use, the best example is Apple Journal. Basic stuff that’s worked reliably for decades — some things that heretofore had worked forever — are dangerously broken. If you’re running MacOS 26 Tahoe, open Journal and make a new dummy entry. Type something like “The quick brown fox.” Then double-click on the word “brown” and delete it. Now invoke Undo.</p>
  353.  
  354. <p>What you expect is for the word “brown” to reappear. What happens is ... <em>the whole sentence disappears</em>. Gone. Invoke Redo and you only get back to “The quick fox.” The word “brown” is just gone forever. It’s nowhere in the Undo stack. That’s just profoundly fucked up. I’ve never seen anything like this with an AppKit app, ever. (I’ve never seen it with a UIKit app either — and the same thing happens on iOS with Journal. It’s just that you notice it less often because we don’t invoke Undo and Redo nearly as often there.)</p>
  355.  
  356. <p>I actually use the Journal app and I’ve lost entire sentences of text to this incompetent implementation of Undo. Editing text in Journal is <em>dangerous</em> because SwiftUI is so bad at something as fundamental as text editing. AppKit has had this solved since 1989 or so, a decade before Apple reunified with NeXT. And my example here is just one of many. Andrade documents a whole bunch more in his post. [Shopie is a good modern Mac app — you can practically see from reading his post that Andrade’s hands are scarred from dozens of paper cuts.</p>
  357.  
  358. <p>So while the world is largely focused on Apple’s AI-related announcements at WWDC tomorrow, I’ve got SwiftUI (on all platforms) and Mac-assed Mac development high on my list. Apple’s developer message used to be that it was not just easy to develop apps for their platforms, but that it was easy to develop <em>good idiomatically native</em> apps. You got the correct complex behavior — for things like Undo/Redo — out of the box. That’s still true for AppKit and UIKit, but it’s never been true for SwiftUI, and <a href="https://www.apple.com/newsroom/2019/06/apple-unveils-groundbreaking-new-technologies-for-app-development/">SwiftUI is now seven years old</a>. That’s too long for any excuses to hold water. </p>
  359.  
  360.    ]]></content>
  361.  <title>★ SwiftUI Only Makes It Easy to Develop Bad Apps</title></entry><entry>
  362. <title>Alberto Romero on Apple’s AI Spending</title>
  363. <link rel="alternate" type="text/html" href="https://www.thealgorithmicbridge.com/p/what-apple-knows-about-ai-that-silicon" />
  364. <link rel="shorturl" type="text/html" href="http://df4.us/x96" />
  365. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/07/alberto-romero-on-apples-ai-spending" />
  366. <id>tag:daringfireball.net,2026:/linked//6.43098</id>
  367. <published>2026-06-08T01:00:00Z</published>
  368. <updated>2026-06-08T01:49:17Z</updated>
  369. <author>
  370. <name>John Gruber</name>
  371. <uri>http://daringfireball.net/</uri>
  372. </author>
  373. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  374. <p>Alberto Romero:</p>
  375.  
  376. <blockquote>
  377.  <p>AI is like religion. Either you believe it changes everything, or
  378. you don’t believe at all. There is no moderate position; nobody
  379. believes in AGI “more or less,” just like nobody is “casually
  380. religious.” If God exists, the only coherent response is to
  381. reorganize your entire life around that fact, as priests do. If
  382. you pray sometimes, then you are just an atheist who’s also
  383. fearful. When tech companies spend hundreds of billions on capital
  384. expenditures to add sparkly AI features to Office, Gmail, and
  385. Instagram, I only see fearful atheists — guys who don’t believe
  386. in AI but pretend just in case.</p>
  387.  
  388. <p>In 2026, the four largest cloud and AI infrastructure providers — Amazon, Google, Meta, Microsoft — committed to <a href="https://www.wsj.com/tech/ai/big-tech-strikes-gold-with-ai-but-at-a-steep-cost-f6d82a22">spending $670
  389. billion on CapEx</a>. Apple, in contrast, spent $12.7 billion on
  390. capex last fiscal year and projects <a href="https://www.forbes.com/sites/greatspeculations/2026/02/20/apples-ai-gamble-can-a-14b-budget-compete-in-a-700b-arms-race/">$14 billion for 2026</a>, 2%
  391. of what its peers are spending. The conventional reading in
  392. Silicon Valley is, naturally, that Apple is losing. Siri has been
  393. a punchline for years — an internal executive <a href="https://www.bloomberg.com/news/articles/2025-03-14/apple-s-siri-chief-calls-ai-delays-ugly-and-embarrassing-promises-fixes">called the delays
  394. ugly and embarrassing</a> — and critics say that Apple has not
  395. been the same without Steve Jobs. It is <a href="https://www.wsj.com/tech/ai/apple-ai-siri-development-behind-9ea65ee8">falling behind</a>, they
  396. say, and moving way too slowly for AI.</p>
  397.  
  398. <p>I disagree with this portrayal: Apple is the most powerful tech
  399. company in the world right now because it’s acting according to
  400. what it believes.</p>
  401. </blockquote>
  402.  
  403. <p>Some of you, I bet, will object to Romero’s notion that no one is “casually religious”. <em>Almost everyone I know is casually religious</em>, you might be thinking. But read the whole piece. What he’s saying is that if you’re “casually religious” those are just words. You’re not living your life according to your professed beliefs (casual or not). And that’s how most of Apple’s peer companies seem to be approaching AI.</p>
  404.  
  405. <p>I’m not sure he’s right, but he might be, and I think his take is at least closer to right than wrong. Apple <em>is</em> making an enormous bet on AI — but their bet is that they don’t need to spend hundreds of billions per year on AI infrastructure (most of it fattening Nvidia’s bottom line) to reap the benefits. If Apple’s right we should start seeing it come together tomorrow.</p>
  406.  
  407. <p>(Arguably we’ve already seen it coming together — demand for Apple’s products and services has gone up, not down, so far in the AI era. Entrenched leaders often grow during the initial stages of extinctive disruptions — BlackBerry’s biggest year for sales (revenue) and investor confidence (market cap) <a href="https://www.statista.com/statistics/266240/blackberry-revenue/">was 2011</a>, four years after the iPhone debuted — but the disruptors are there. There’s not yet a single threat on the market to the iPhone, iPad, Mac, Apple Watch, or AirPods — nor to Apple’s services revenue.)</p>
  408.  
  409. <div>
  410. <a  title="Permanent link to ‘Alberto Romero on Apple’s AI Spending’"  href="https://daringfireball.net/linked/2026/06/07/alberto-romero-on-apples-ai-spending">&nbsp;★&nbsp;</a>
  411. </div>
  412.  
  413. ]]></content>
  414.  </entry><entry>
  415. <title>Halide Mark III</title>
  416. <link rel="alternate" type="text/html" href="https://www.lux.camera/halide-mark-iii/" />
  417. <link rel="shorturl" type="text/html" href="http://df4.us/x94" />
  418. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/06/halide-mark-iii" />
  419. <id>tag:daringfireball.net,2026:/linked//6.43096</id>
  420. <published>2026-06-07T00:49:15Z</published>
  421. <updated>2026-06-07T03:17:01Z</updated>
  422. <author>
  423. <name>John Gruber</name>
  424. <uri>http://daringfireball.net/</uri>
  425. </author>
  426. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  427. <p>Ben Sandofsky, writing on the Lux Camera blog:</p>
  428.  
  429. <blockquote>
  430.  <p>After decades of shooting digital, I returned to analog
  431. photography in 2023. I thought it would be challenging, given the
  432. limited selection of film stocks, only to be surprised by how
  433. freeing it felt. It felt so much better to have a handful of
  434. amazing choices rather than photo-editor with thousands of
  435. presets. We owe that to film engineers who spent years developing
  436. versatile film stocks that work in a variety of situations.</p>
  437.  
  438. <p>Inspired by “Less, but better,” we partnered with the renowned
  439. Hollywood colorist <a href="https://cullenkellycolor.com/">Cullen Kelly</a> to develop a
  440. succinct set of gorgeous, <em>physically accurate</em> processes
  441. exclusive to Halide. Each look was engineered with a specific
  442. intent. We verified every look thousands of times on real-world
  443. reference photos.</p>
  444.  
  445. <p>Put another way: every look is a banger.</p>
  446. </blockquote>
  447.  
  448. <p>Halide has always been a great — maybe <em>the</em> great — iPhone camera app for shooting RAW, with the intention of developing your images by hand in post. It’s a great <em>camera</em> technically and a great <em>app</em> UI-wise. <a href="https://www.lux.camera/introducing-process-zero-for-iphone/">Mark II introduced Process Zero</a>, which, in their own description, “uses zero AI and zero computational photography to produce beautiful, film-like natural photos”. Process Zero was the first step toward the new built-in “looks” in Halide Mark III. I’ve been shooting with Mark III for a few weeks now, and they are, indeed, all bangers. And I <em>really</em> like that there aren’t that many of them. I wanted more looks than just Process Zero (which remains available, of course), but I feel a bit overwhelmed when faced with a dozen (or worse, dozen<em>s</em>) of choices for processing. I feel conflicted enough having to choose between <a href="https://daringfireball.net/2026/03/the_iphone_17e#fn2-2026-03-09">a handful</a> of <a href="https://daringfireball.net/2025/10/not_boring_camera_and_adobe_project_indigo">really good</a> third-party camera apps with which to shoot in the first place — it’s worse when I have to make too many choices within the camera app itself.</p>
  449.  
  450. <p>What I want is to just point and shoot and be able to instantly share images with the look I want already applied. I’m picky but I’m also really lazy, and don’t want to do any editing in post on most of the shots I keep. But I do want to be able to edit in post if I want to, including changing the look losslessly. This mixture of point-and-shoot ease and pro-level control didn’t use to be possible. Now, though, it is, with apps like <a href="https://apps.apple.com/us/app/not-boring-camera/id6737783441">Not Boring Camera</a>, <a href="https://apps.apple.com/us/app/analogue-film-camera/id6748702405">Analogue</a>, and, now, <a href="https://apps.apple.com/us/app/halide-mark-iii-pro-camera/id885697368">Halide Mark III</a>.</p>
  451.  
  452. <p>It’s been a <a href="https://www.macrumors.com/2026/03/21/apple-wanted-to-buy-halide-to-boost-iphone-18-pro/">turbulent</a> couple of months for Lux (to say the least), so I’m glad to see Sandofsky and team get Mark III out the door. If you, like me, had previously been impressed by Halide but didn’t use it because it required too much work in post, you should check out Mark III.</p>
  453.  
  454. <div>
  455. <a  title="Permanent link to ‘Halide Mark III’"  href="https://daringfireball.net/linked/2026/06/06/halide-mark-iii">&nbsp;★&nbsp;</a>
  456. </div>
  457.  
  458. ]]></content>
  459.  </entry><entry>
  460. <title>60 Minutes Correspondents Lesley Stahl, Bill Whitaker, and the Other Guy Will Stay at Show</title>
  461. <link rel="alternate" type="text/html" href="https://www.nytimes.com/2026/06/05/business/media/60-minutes-cbs-stahl-whitaker-wertheim.html?unlocked_article_code=1.oFA.xooG.Pz8cQv8odz7Z" />
  462. <link rel="shorturl" type="text/html" href="http://df4.us/x93" />
  463. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/06/stahl-whitaker-60-minutes" />
  464. <id>tag:daringfireball.net,2026:/linked//6.43095</id>
  465. <published>2026-06-06T20:04:06Z</published>
  466. <updated>2026-06-06T20:04:06Z</updated>
  467. <author>
  468. <name>John Gruber</name>
  469. <uri>http://daringfireball.net/</uri>
  470. </author>
  471. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  472. <p>Lesley Stahl, Bill Whitaker, and Jon Wertheim, <a href="https://www.nytimes.com/interactive/2026/06/05/business/media/60-minutes-stahl-wertheim-whittaker-memo.html?unlocked_article_code=1.oFA.flOX.fSw9JEqNoaU9">in a memo to the 60 Minutes staff</a> obtained by The New York Times (gift links):</p>
  473.  
  474. <blockquote>
  475.  <p>We have had a hard time deciding whether to stay at 60 Minutes.
  476. We’re still deeply upset by the firings of Tanya and Draggan,
  477. strong leaders who everyone respected. As far as we can tell — because no explanation has ever been offered, they were expelled
  478. because they fought for our 60 Minutes values and stood up to
  479. protect our independence and integrity.</p>
  480.  
  481. <p>Newsrooms are not supposed to be run like dictatorships.
  482. Collaboration and argument are the way we have always worked at
  483. 60. Don Hewitt actually encouraged loud passionate advocacy for
  484. our pieces. [...]</p>
  485.  
  486. <p>We feared that our returning might be construed as an endorsement
  487. of the existing power structure. That is simply, categorically not
  488. the case.</p>
  489.  
  490. <p>Here’s why we’re are staying:</p>
  491.  
  492. <p>We don’t want to see 60 Minutes die.</p>
  493. </blockquote>
  494.  
  495. <p>We’ll see how long this lasts.</p>
  496.  
  497. <div>
  498. <a  title="Permanent link to ‘60 Minutes Correspondents Lesley Stahl, Bill Whitaker, and the Other Guy Will Stay at Show’"  href="https://daringfireball.net/linked/2026/06/06/stahl-whitaker-60-minutes">&nbsp;★&nbsp;</a>
  499. </div>
  500.  
  501. ]]></content>
  502.  </entry><entry>
  503. <title>Trump Lawyer Argues Trump Can Tear Down Statue of Liberty</title>
  504. <link rel="alternate" type="text/html" href="https://talkingpointsmemo.com/edblog/trump-can-tear-down-statue-of-liberty-says-trump-lawyer" />
  505. <link rel="shorturl" type="text/html" href="http://df4.us/x92" />
  506. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/06/trump-statue-of-liberty" />
  507. <id>tag:daringfireball.net,2026:/linked//6.43094</id>
  508. <published>2026-06-06T19:56:01Z</published>
  509. <updated>2026-06-06T19:56:02Z</updated>
  510. <author>
  511. <name>John Gruber</name>
  512. <uri>http://daringfireball.net/</uri>
  513. </author>
  514. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  515. <p>Josh Marshall:</p>
  516.  
  517. <blockquote>
  518.  <p>In a hearing today about the president’s bulldozing of the East
  519. Wing of the White House and plans to build a vast ballroom, a
  520. judge asked if the president could also bulldoze the Statue of
  521. Liberty and be subject to no legal challenge. The DOJ lawyer,
  522. Yaakov Roth, <a href="https://www.politico.com/news/2026/06/05/white-house-ballroom-donald-trump-00951892">said that yes, President Trump could decide tomorrow
  523. to bulldoze the Statue of Liberty</a> and no one could
  524. stop him.</p>
  525.  
  526. <p>It was a good question from DC Court of Appeals Judge Patricia
  527. Millett since it brings the arguments and their implications
  528. clearly into the open. Reframe the question and the absurdity of
  529. this proposition becomes even more clear. If you hire someone to
  530. administer your estate, can they burn down the buildings on your
  531. estate or chop it up into parcels and sell it off? Presumably not.
  532. You hired them to run it, not to destroy it or sell it. It’s not
  533. theirs. They were hired for a specific task. That person is your
  534. employee. The president is hired to administer the country and
  535. enforce its laws for four years. He doesn’t own the country or its
  536. properties.</p>
  537. </blockquote>
  538.  
  539. <p>Pathetic lickspittles, one and all.</p>
  540.  
  541. <div>
  542. <a  title="Permanent link to ‘Trump Lawyer Argues Trump Can Tear Down Statue of Liberty’"  href="https://daringfireball.net/linked/2026/06/06/trump-statue-of-liberty">&nbsp;★&nbsp;</a>
  543. </div>
  544.  
  545. ]]></content>
  546.  </entry><entry>
  547. <title>Nieman Journalism Lab: Twitter/X Punishes Accounts That Post Links</title>
  548. <link rel="alternate" type="text/html" href="https://www.niemanlab.org/2026/04/do-links-hurt-news-publishers-on-twitter-our-analysis-suggests-yes/" />
  549. <link rel="shorturl" type="text/html" href="http://df4.us/x91" />
  550. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/05/nieman-journalism-lab-twitter-links" />
  551. <id>tag:daringfireball.net,2026:/linked//6.43093</id>
  552. <published>2026-06-05T20:46:56Z</published>
  553. <updated>2026-06-05T20:46:57Z</updated>
  554. <author>
  555. <name>John Gruber</name>
  556. <uri>http://daringfireball.net/</uri>
  557. </author>
  558. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  559. <p>Laura Hazard Owen, writing for Nieman Journalism Lab back in April:</p>
  560.  
  561. <blockquote>
  562.  <p>I used Claude to help me scrape the 200 most recent tweets from 18
  563. large publishers’ X accounts and track the engagement (likes +
  564. comments + retweets) on each. Six of those publishers have
  565. paywalls: <a href="https://x.com/business">Bloomberg</a>, <a href="https://x.com/cnn">CNN</a>, <a href="https://x.com/Forbes">Forbes</a>, <a href="https://x.com/nytimes">The New
  566. York Times</a>, <a href="https://x.com/WSJ">The Wall Street Journal</a>, and <a href="https://x.com/washingtonpost">The
  567. Washington Post</a>. Nine don’t: <a href="https://x.com/AJEnglish">Al Jazeera English</a>,
  568. <a href="https://x.com/AP">AP</a>, <a href="https://x.com/BBCNews">BBC</a>, <a href="https://x.com/BreitbartNews">Breitbart News</a>, <a href="https://x.com/CBSNews">CBS News</a>,
  569. <a href="https://x.com/realDailyWire">Daily Wire</a>, <a href="https://x.com/FoxNews">Fox News</a>, <a href="https://x.com/NBCNews">NBC News</a>, and
  570. <a href="https://x.com/Reuters">Reuters</a>. The last three accounts I looked at — <a href="https://x.com/LeadingReport">Leading
  571. Report</a>, <a href="https://x.com/unusual_whales">unusual_whales,</a> and <a href="https://x.com/GlobeEyeNews">Globe Eye News</a> — are not news publishers, but aggregate breaking news in tweets
  572. without links. (Here, for example, is an example of a Leading
  573. Report <a href="https://x.com/LeadingReport/status/2041534947249242192">tweet</a>: “BREAKING: Iran has halted direct talks with
  574. the US, per WSJ.” They’re sometimes referred to as
  575. engagement-maxing accounts.</p>
  576.  
  577. <p>These charts make it pretty clear that links in tweets hurt
  578. engagement. The connection was so apparent in my analysis that a
  579. graph including all 18 publishers is almost unreadable: The
  580. traditional, link-loving publishers are clustered in the bottom
  581. left corner (lots of links, little engagement) in a nearly
  582. indistinguishable mass of bubbles, no matter how large their
  583. followings are.</p>
  584. </blockquote>
  585.  
  586. <p>Musk’s Twitter/X is not an aggregator for news. It’s a walled garden. But the type of garden where you need to keep your eyes open and your hand on your wallet. Sometimes it’s fun to visit a seedy neighborhood. But let’s not pretend it isn’t a seedy neighborhood just because, long ago, it used to be nice.</p>
  587.  
  588. <div>
  589. <a  title="Permanent link to ‘Nieman Journalism Lab: Twitter/X Punishes Accounts That Post Links’"  href="https://daringfireball.net/linked/2026/06/05/nieman-journalism-lab-twitter-links">&nbsp;★&nbsp;</a>
  590. </div>
  591.  
  592. ]]></content>
  593.  </entry><entry>
  594. <title>Elon Musk’s X Is a Freak Show</title>
  595. <link rel="alternate" type="text/html" href="https://www.natesilver.net/p/social-media-has-become-a-freak-show" />
  596. <link rel="shorturl" type="text/html" href="http://df4.us/x90" />
  597. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/05/musk-x-freak-show" />
  598. <id>tag:daringfireball.net,2026:/linked//6.43092</id>
  599. <published>2026-06-05T20:24:58Z</published>
  600. <updated>2026-06-05T20:32:32Z</updated>
  601. <author>
  602. <name>John Gruber</name>
  603. <uri>http://daringfireball.net/</uri>
  604. </author>
  605. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  606. <p>Nate Silver, back in April, under the headline “Social Media Is Turning Into a Freak Show”, where by “social media” he mostly discusses Twitter/X:</p>
  607.  
  608. <blockquote>
  609.  <p>But what does that remaining traffic consist of? I recently came
  610. across a <a href="https://x.com/kylewilsontharp/status/2037171182407999663">bubble chart</a> depicting the Twitter accounts that
  611. had received the most “engagement” in February 2026. It was
  612. depressing: most of the top accounts were extremely low-quality
  613. and highly partisan. I hadn’t even heard of many of them and only
  614. follow a handful of the top accounts. So I <a href="https://dashboards.cluvio.com/dashboards/qxny-9e5q-k65v/shared?filters=%7B%22platform_filter%22%3A%5B%5D%2C%22political_content%22%3A%5B%5D%2C%22political_lean%22%3A%5B%5D%7D&amp;reportId=k6zq-g911-3m2o&amp;sharingToken=78eb1196-5766-429d-acf8-edcfd96b7067&amp;timerange=1767225600~">tracked down the
  615. original data myself</a> and, with help from Claude, made my
  616. own improved version of the chart. Here, <em>voilà</em>, are the Twitter
  617. accounts with the most engagement so far in 2026:</p>
  618.  
  619. <p><a href="/misc/2026/05/nate-silver-twitter-account-cloud.png" class="noborder">
  620. <img
  621.  src = "/misc/2026/05/nate-silver-twitter-account-cloud.png"
  622.  alt = "Data from Cluvio showing most engagements among X accounts from Jan. 1 to Apr. 4, 2026."
  623.  width = 500
  624. /></a></p>
  625.  
  626. <p>It’s not hard to notice that Twitter has become extremely
  627. right-leaning. But I’d argue there’s an equally important trend:
  628. the top accounts are of incredibly low quality. Elon, with the
  629. <a href="https://www.theguardian.com/technology/2023/feb/15/elon-musk-changes-twitter-algorithm-super-bowl-slump-report">algorithmic boost</a> he built in for himself, is at the eye of
  630. the storm, of course. But “Catturd” literally gets far more
  631. engagement than the New York Times, for instance.</p>
  632. </blockquote>
  633.  
  634. <p>There’s a common argument from proponents of the Musk-era X that the only problem is that left-leaning people have abandoned the platform. That the X algorithm is a contest and if only right-leaning accounts are playing, of course they’re winning. This is nonsense. The whole thing is rigged. Elon Musk’s outsized prominence as the most-engaged-with account is proof of that. Twitter existed for 16 years before Musk bought it. He wasn’t even close to the biggest account during that era. Then he bought it. Now his account is the biggest.</p>
  635.  
  636. <p>As Silver’s data analysis shows, Musk’s X is not just dominated by right-wing accounts, it’s dominated by “<em>who the hell is that?</em>” right-wing slop accounts.</p>
  637.  
  638. <p>The only way not to lose a rigged game is to refuse to play. X is still a thing. A lot of people, companies, and organizations still post there — treat it like their blogs — exclusively. I still wind up linking to posts on X because that’s where they are. That’s a whole separate discussion. But anyone who’s trying to “compete” there with subject matter that is even vaguely political has no chance of success unless what they’re posting is what Elon Musk wants to see promoted. It’s not like his thumb is on the scale, it’s like an anvil is on the scale. The conundrum is that there are still a lot interesting people posting interesting things there.</p>
  639.  
  640. <div>
  641. <a  title="Permanent link to ‘Elon Musk’s X Is a Freak Show’"  href="https://daringfireball.net/linked/2026/06/05/musk-x-freak-show">&nbsp;★&nbsp;</a>
  642. </div>
  643.  
  644. ]]></content>
  645.  </entry><entry>
  646. <title>Checking in on Perplexity</title>
  647. <link rel="alternate" type="text/html" href="https://daringfireball.net/linked/2025/08/05/regarding-those-rumors-of-apple-pursuing-an-acquisition-of-perplexity" />
  648. <link rel="shorturl" type="text/html" href="http://df4.us/x8z" />
  649. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/05/checking-in-on-perplexity" />
  650. <id>tag:daringfireball.net,2026:/linked//6.43091</id>
  651. <published>2026-06-05T15:26:29Z</published>
  652. <updated>2026-06-05T15:26:30Z</updated>
  653. <author>
  654. <name>John Gruber</name>
  655. <uri>http://daringfireball.net/</uri>
  656. </author>
  657. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  658. <p>Yours truly, last August:</p>
  659.  
  660. <blockquote>
  661.  <p>I can’t see why Apple would want to get involved with a company
  662. like this though. Gurman’s report makes it sound like his sources
  663. are inside Apple, but man, this “Apple + Perplexity” thing feels
  664. more like something Perplexity would be seeding than one that
  665. Apple executives would be leaking.</p>
  666. </blockquote>
  667.  
  668. <p>Perplexity is still <a href="https://www.techmeme.com/search/query?q=perplexity&amp;wm=false">occasionally in the news</a> (often <a href="https://daringfireball.net/linked/2026/04/04/perplexity-class-action-sham">not in good ways</a>), but it seems to me they’ve slipped into the “afterthought” tier of AI startups — which is exactly why they started leaning into <a href="https://daringfireball.net/linked/2025/08/12/perplexity-jumps-shark-stunt-offer-to-buy-chrome">clownish stunts last year</a>. Everyone who previously suggested Apple should — or even might — buy them has gone silent.</p>
  669.  
  670. <div>
  671. <a  title="Permanent link to ‘Checking in on Perplexity’"  href="https://daringfireball.net/linked/2026/06/05/checking-in-on-perplexity">&nbsp;★&nbsp;</a>
  672. </div>
  673.  
  674. ]]></content>
  675.  </entry><entry>
  676. <title>Some People Rooted for The Empire in ‘Star Wars’, Too</title>
  677. <link rel="alternate" type="text/html" href="https://hotair.com/ed-morrissey/2026/06/03/cbs-fires-scott-pelley-after-trying-very-hard-to-get-fired-n3815553" />
  678. <link rel="shorturl" type="text/html" href="http://df4.us/x8y" />
  679. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/04/some-people-rooted-for-the-empire" />
  680. <id>tag:daringfireball.net,2026:/linked//6.43090</id>
  681. <published>2026-06-05T00:43:33Z</published>
  682. <updated>2026-06-05T00:43:33Z</updated>
  683. <author>
  684. <name>John Gruber</name>
  685. <uri>http://daringfireball.net/</uri>
  686. </author>
  687. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  688. <p>Ed Morrissey, writing for Hot Air, thinks Scott Pelley got what he deserved and Bari Weiss is doing a good job running CBS News:</p>
  689.  
  690. <blockquote>
  691.  <p>And Pelley forgot the Golden Rule: <em>He who has the gold makes the
  692. rules</em>. Instead, Pelley convinced himself of his own virtue and
  693. torched his own position — and if Bilton’s letter is accurate, in
  694. as mean-spirited and conceited a manner as possible. Pelley could
  695. have chosen a dignified resignation under protest, but instead
  696. pulled a power move in an attempt to intimidate Bilton, Weiss, and
  697. Ellison, only to discover that no one feared his absence. In fact,
  698. they’re probably happy to cut him loose.</p>
  699.  
  700. <p>There’s always at least <em>one</em> person in these situations who
  701. thinks they’re untouchable. A wise executive knows to start by
  702. making an example of that person, and then see how many other
  703. people think they’re indispensable. It’s not as if TV news jobs
  704. are expanding these days, after all. Pelley’s going to find out
  705. the hard way that no one’s paying $5 million a year to emote into
  706. a camera from other people’s copy.</p>
  707. </blockquote>
  708.  
  709. <p>It doesn’t even enter this man’s little mind that Pelley wasn’t concerned about his job, wasn’t concerned about his salary, but was concerned only with the integrity of the institution to which he’d committed decades of his career, and that he saw as his duty the need to stand up for his remaining and former colleagues. That Pelley himself has integrity. To the Trump lickspittles, everything is performative. They don’t just lack integrity, they don’t believe integrity is real.</p>
  710.  
  711. <p><a href="https://x.com/katienotopoulos/status/2062229659966697857">Katie Notopoulos</a>:</p>
  712.  
  713. <blockquote>
  714.  <p>The Scott Pelley story to me is a lesson in how if you work hard
  715. enough in your career to get Fuck You Money, the real reward is
  716. the day you need to say it, you can.</p>
  717. </blockquote>
  718.  
  719. <div>
  720. <a  title="Permanent link to ‘Some People Rooted for The Empire in ‘Star Wars’, Too’"  href="https://daringfireball.net/linked/2026/06/04/some-people-rooted-for-the-empire">&nbsp;★&nbsp;</a>
  721. </div>
  722.  
  723. ]]></content>
  724.  </entry><entry>
  725. <title>The Talk Show Live From WWDC 2026: Tuesday in San Jose</title>
  726. <link rel="alternate" type="text/html" href="https://ti.to/daringfireball/the-talk-show-live-from-wwdc-2026" />
  727. <link rel="shorturl" type="text/html" href="http://df4.us/x8x" />
  728. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/04/the-talk-show-live-tickets-2026" />
  729. <id>tag:daringfireball.net,2026:/linked//6.43089</id>
  730. <published>2026-06-04T22:05:05Z</published>
  731. <updated>2026-06-04T22:50:57Z</updated>
  732. <author>
  733. <name>John Gruber</name>
  734. <uri>http://daringfireball.net/</uri>
  735. </author>
  736. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  737. <p><strong>Location:</strong> The California Theatre, San Jose <br />
  738. <strong>Showtime:</strong> Tuesday, 9 June 2026, 7pm PT (Doors open 6pm) <br />
  739. <strong>Special Guest(s):</strong> For sure <br />
  740. <strong>Price:</strong> $45</p>
  741.  
  742. <p>The annual live audience episode of The Talk Show during the week of WWDC. If you can make it, you should come. You’ll even enjoy the prelude, mingling with fellow DF readers and listeners.</p>
  743.  
  744. <div>
  745. <a  title="Permanent link to ‘The Talk Show Live From WWDC 2026: Tuesday in San Jose’"  href="https://daringfireball.net/linked/2026/06/04/the-talk-show-live-tickets-2026">&nbsp;★&nbsp;</a>
  746. </div>
  747.  
  748. ]]></content>
  749.  </entry><entry>
  750. <title>‘The Insider’</title>
  751. <link rel="alternate" type="text/html" href="https://letterboxd.com/film/the-insider/" />
  752. <link rel="shorturl" type="text/html" href="http://df4.us/x8w" />
  753. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/04/the-insider" />
  754. <id>tag:daringfireball.net,2026:/linked//6.43088</id>
  755. <published>2026-06-04T20:42:35Z</published>
  756. <updated>2026-06-04T20:42:36Z</updated>
  757. <author>
  758. <name>John Gruber</name>
  759. <uri>http://daringfireball.net/</uri>
  760. </author>
  761. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  762. <p>All this Sturm und Drang surrounding 60 Minutes has me thinking about a re-watch of <em>The Insider</em>, Michael Mann’s great 1999 movie. Letterboxd’s synopsis:
  763. “A research chemist comes under personal and professional attack when he decides to appear in a 60 Minutes exposé on Big Tobacco.” It’s a great movie, and feels apt AF at the moment. <a href="https://www.youtube.com/watch?v=1_-Vu8LrUDk">Here’s the original segment on 60 Minutes</a>, which ran an entire half hour.</p>
  764.  
  765. <p>What’s going on today is like if — instead of getting shady, threatening, and litigious — the tobacco companies had just purchased CBS, purged the staff at 60 Minutes, and hired a bunch of pro-cigarette stooges to replace them.</p>
  766.  
  767. <div>
  768. <a  title="Permanent link to ‘‘The Insider’’"  href="https://daringfireball.net/linked/2026/06/04/the-insider">&nbsp;★&nbsp;</a>
  769. </div>
  770.  
  771. ]]></content>
  772.  </entry><entry>
  773. <title>‘Microsoft and OpenAI Broke Up — Now They’re Ready to Fight’</title>
  774. <link rel="alternate" type="text/html" href="https://www.theverge.com/ai-artificial-intelligence/942242/microsoft-build-ai-agents-openai-competition?view_token=eyJhbGciOiJIUzI1NiJ9.eyJpZCI6IjdiRHFjMlJadmgiLCJwIjoiL2FpLWFydGlmaWNpYWwtaW50ZWxsaWdlbmNlLzk0MjI0Mi9taWNyb3NvZnQtYnVpbGQtYWktYWdlbnRzLW9wZW5haS1jb21wZXRpdGlvbiIsImV4cCI6MTc4MTAzNjQ2OSwiaWF0IjoxNzgwNjA0NDY5fQ.jP0KO9OVCO-fGkk1Utt0NIEn97JWaI8zs0zhjf2V2MQ" />
  775. <link rel="shorturl" type="text/html" href="http://df4.us/x8v" />
  776. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/04/microsoft-openai" />
  777. <id>tag:daringfireball.net,2026:/linked//6.43087</id>
  778. <published>2026-06-04T20:25:27Z</published>
  779. <updated>2026-06-04T22:35:40Z</updated>
  780. <author>
  781. <name>John Gruber</name>
  782. <uri>http://daringfireball.net/</uri>
  783. </author>
  784. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  785. <p>Hayden Field and Tom Warren, writing for The Verge (gift link):</p>
  786.  
  787. <blockquote>
  788.  <p>This year’s Build had the vibe of a freshly single divorcée
  789. posting a thirst trap on Instagram. “It’s always fun to be at
  790. developer conferences in times of great change,” Microsoft CEO
  791. Satya Nadella said onstage Tuesday, adding that events like this
  792. are about “coming to grips with the new opportunity.”</p>
  793.  
  794. <p>AI chief Mustafa Suleyman, in an interview with The Verge, put it
  795. even more bluntly.</p>
  796.  
  797. <p>“The goal is to prove that we can become one of the top four labs
  798. in the world,” Suleyman said. “There’s three labs that matter,
  799. Google DeepMind, OpenAI, and Anthropic. We are not one of them at
  800. the moment, and that’s always been my intention. It’s why I came
  801. here. I want to build the very best frontier models in the world,
  802. fully multimodal, and in order to do that, we have to prove that
  803. we can do everything that we need to from the ground up, and we’re
  804. not just going to take from others.”</p>
  805. </blockquote>
  806.  
  807. <p>Refreshingly blunt.</p>
  808.  
  809. <p>But hasn’t that been Microsoft’s plan for Bing since it was announced in 2009? I mean I guess you can say that Bing is one of the top four search engines in the world. Maybe you can even say it’s one of the top two. But it’s irrelevant and uncompetitive with Google Search.</p>
  810.  
  811. <div>
  812. <a  title="Permanent link to ‘‘Microsoft and OpenAI Broke Up — Now They’re Ready to Fight’’"  href="https://daringfireball.net/linked/2026/06/04/microsoft-openai">&nbsp;★&nbsp;</a>
  813. </div>
  814.  
  815. ]]></content>
  816.  </entry><entry>
  817. <title>Lingon and Lingon Pro 10</title>
  818. <link rel="alternate" type="text/html" href="https://www.peterborgapps.com/lingon/" />
  819. <link rel="shorturl" type="text/html" href="http://df4.us/x8u" />
  820. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/04/lingon" />
  821. <id>tag:daringfireball.net,2026:/linked//6.43086</id>
  822. <published>2026-06-04T18:43:47Z</published>
  823. <updated>2026-06-04T18:44:13Z</updated>
  824. <author>
  825. <name>John Gruber</name>
  826. <uri>http://daringfireball.net/</uri>
  827. </author>
  828. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  829. <p>Peter Borg:</p>
  830.  
  831. <blockquote>
  832.  <p>Lingon makes scheduling apps, scripts, shortcuts, and commands
  833. feel simple. Create a task in minutes, run it on a schedule, and
  834. stay in control.</p>
  835.  
  836. <p>Lingon helps you run whatever you want whenever you want without
  837. living in Terminal. Schedule apps, scripts, shortcuts, and
  838. commands with a clear, friendly UI.</p>
  839.  
  840. <p>Run tasks at specific times, on intervals or at login. Optional
  841. notifications make it easy to keep control.</p>
  842.  
  843. <p>Two separate apps. Lingon is the simpler Mac App Store version and
  844. free to use, while Lingon Pro is the advanced one-time purchase
  845. with extra power.</p>
  846. </blockquote>
  847.  
  848. <p><a href="https://www.peterborgapps.com/lingon/">Lingon and Lingon Pro</a> are great apps. I’ve been meaning to recommend them for a while.</p>
  849.  
  850. <p>Back in 2023 <a href="https://daringfireball.net/2023/07/nerding_out_with_maestral_launchcontrol_and_keyboard_maestro">I wrote about a problem I was having with Maestral</a>, the incredible “works like Dropbox in the old days” open-source Dropbox client, where Maestral would just silently crash once in a while and I wouldn’t notice for a while. Then I would notice, manually re-launch Maestral, and have to wait while Maestral synced. Or, worse, I’d put a podcast recording in a shared folder and walk away from my computer, and my editor would never get the file because Maestral wasn’t running. My write-up described how I solved the problem with a Keyboard Maestro macro that runs once an hour — it checks if Maestral is running, and if it isn’t, launches it (and writes to a log, to satisfy my own curiosity). Borg wrote to me after I posted that and — very politely — explained that Lingon would make that much simpler.</p>
  851.  
  852. <p>In addition to creating your own scripts and rules that run periodically, Lingon is great for inspecting all the login items and background agents on your system — whether they’re from Apple or third parties. Poking around at everything Google Gemini installed is what made me think to recommend Lingon today. At the very least you should install the free regular version. It’s just a great Mac utility from a great Mac developer. There’s nothing else like it.</p>
  853.  
  854. <div>
  855. <a  title="Permanent link to ‘Lingon and Lingon Pro 10’"  href="https://daringfireball.net/linked/2026/06/04/lingon">&nbsp;★&nbsp;</a>
  856. </div>
  857.  
  858. ]]></content>
  859.  </entry><entry>
  860. <title>Remember When Chrome Went Bad on MacOS?</title>
  861. <link rel="alternate" type="text/html" href="https://chromeisbad.com/" />
  862. <link rel="shorturl" type="text/html" href="http://df4.us/x8t" />
  863. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/04/remember-when-chrome-went-bad-on-macos" />
  864. <id>tag:daringfireball.net,2026:/linked//6.43085</id>
  865. <published>2026-06-04T18:10:19Z</published>
  866. <updated>2026-06-04T22:44:42Z</updated>
  867. <author>
  868. <name>John Gruber</name>
  869. <uri>http://daringfireball.net/</uri>
  870. </author>
  871. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  872. <p><a href="https://daringfireball.net/search/tweetie+brichter">Loren Brichter</a>, back in 2020:</p>
  873.  
  874. <blockquote>
  875.  <p>Short story: Google Chrome installs an updater called Keystone on
  876. your computer, which is <a href="https://twitter.com/lorenb/timelines/1338892756752732169">bizarrely correlated</a> to massive
  877. unexplained CPU usage in WindowServer (a system process)<a href="https://chromeisbad.com/#hiding">[1]</a>, and
  878. <em>made my whole computer slow even when Chrome wasn’t running</em>.
  879. Deleting Chrome and Keystone made my computer <em>way, way faster,
  880. all the time</em>.</p>
  881.  
  882. <p>Long story: I noticed my brand new 16” MacBook Pro started acting
  883. sluggishly doing even trivial things like scrolling. Activity
  884. Monitor showed <em>nothing</em> from Google using the CPU, but
  885. <em>WindowServer</em> was taking ~80%, which is abnormally high (it
  886. should use &lt; 10% normally).</p>
  887.  
  888. <p>Doing all the normal things (quitting apps, logging out other
  889. users, restarting, zapping PRAM/SMC, etc) did nothing, then I
  890. remembered I had installed Chrome a while back to test a website.</p>
  891.  
  892. <p>I deleted Chrome, and noticed Keystone while deleting some of
  893. Chrome’s other preferences and caches. I deleted everything from
  894. Google I could find, restarted the computer, and it was like
  895. night-and-day. <em>Everything was instantly and noticeably faster,
  896. and WindowServer CPU was well under 10% again.</em></p>
  897. </blockquote>
  898.  
  899. <p>Not all Mac users, but many, found that just having Chrome installed slowed down their Macs dramatically. Completely uninstalling Chrome — and its pernicious background agents — solved the problem. This years-old “Chrome Is Bad” saga came to mind when <a href="https://daringfireball.net/linked/2026/06/04/google-gemini-mac">I wrote about Google’s Gemini Mac app’s background agents</a>.</p>
  900.  
  901. <p>It seems as though Google eventually fixed these Chrome bugs — or Apple changed something in a MacOS update that fixed the bugs for them — but I’ve never seen a full explanation of the problem and eventual solution. Does anyone know what happened here?</p>
  902.  
  903. <p>The main point is it never should have happened in the first place. A third-party app should just be a third-party app — not add components to your system software just so it can update itself when it isn’t running. Background agents and extensions are <a href="https://rogueamoeba.com/">sometimes necessary</a> to the functionality of a product. Checking for software updates to a browser or AI chatbot, when those apps aren’t running, is not necessary. The golden rule applies: imagine if every app on your system installed its own background agent to check for software updates. Chrome is a popular browser on the Mac, but it’s just a web browser. Other web browsers do just fine checking for updates from the browser itself when they’re running. If the user is actually using an app regularly, it’ll get plenty of chances to check for updates when it’s running. If the user isn’t regularly using an app, why in the world should that seldom-used app have software running all the time in the background?</p>
  904.  
  905. <p>This sort of chaos is <a href="https://daringfireball.net/2021/06/annotating_apples_anti-sideloading_white_paper">why Apple keeps iOS locked down</a>. There are no third-party login items on iOS that run in the background — let alone ones with no option to disable. No third-party app can do anything that causes the iOS window manager to consume 80 percent of the CPU while ostensibly idle. There are obviously trade-offs here. I rely on a Mac for my workstation because the Mac gives me the power to potentially shoot myself in the foot. But one major reason why iOS is an order of magnitude more popular than MacOS is because you cannot shoot yourself in the foot with it, even though that means you can’t use it to do things that would require that power.</p>
  906.  
  907. <div>
  908. <a  title="Permanent link to ‘Remember When Chrome Went Bad on MacOS?’"  href="https://daringfireball.net/linked/2026/06/04/remember-when-chrome-went-bad-on-macos">&nbsp;★&nbsp;</a>
  909. </div>
  910.  
  911. ]]></content>
  912.  </entry><entry>
  913. <title>Google’s Gemini Mac App Is Native, in a Distinctly Google Way, But Annoyingly Presumptuous</title>
  914. <link rel="alternate" type="text/html" href="https://gemini.google/mac/" />
  915. <link rel="shorturl" type="text/html" href="http://df4.us/x8s" />
  916. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/04/google-gemini-mac" />
  917. <id>tag:daringfireball.net,2026:/linked//6.43084</id>
  918. <published>2026-06-04T17:29:26Z</published>
  919. <updated>2026-06-04T18:20:44Z</updated>
  920. <author>
  921. <name>John Gruber</name>
  922. <uri>http://daringfireball.net/</uri>
  923. </author>
  924. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  925. <p>Two months ago Google launched a new native Mac app for Gemini. I’ve been trying it, on and off, since. It’s ... not bad. Certainly better than Claude’s Electron shitbox. But the Gemini app isn’t all that good, either. I’m sticking with ChatGPT, which remains far and away the best native Mac client to an LLM. (And ChatGPT is not that great of a Mac app — it’s just the closest to good of the bunch.)</p>
  926.  
  927. <p>The thing that really turns me off about the Gemini Mac app is Google’s gall. The Gemini app installs a background helper named “GeminiAppLauncher” in your login items. It also installs “GoogleUpdater” as a process with the privilege to launch in the background whenever it wants. Gemini never asks for permission to install either of these, and, most arrogantly, if you, as an informed user, remove either of them, the Gemini app silently adds them back. There is no setting in Gemini to disable this. There’s a mindset from some big companies that your system is theirs to play with at the system software level. Fuck that. <a href="https://mjtsai.com/blog/2026/04/16/gemini-app-for-mac/">Michael Tsai’s post</a> on the Gemini Mac app links to <a href="https://forums.macrumors.com/threads/google-launches-native-gemini-ai-app-for-mac.2481037/?post=34543484#post-34543484">this thread on MacRumors</a> regarding this pernicious auto-installed and auto-reinstalled login item. <a href="https://www.reddit.com/r/mac/comments/1smaz0b/the_gemini_app_is_now_on_mac/">Here’s another on Reddit</a>.</p>
  928.  
  929. <p>Google’s approach to its Mac software is disrespectful and entitled.</p>
  930.  
  931. <p>I’d have been happy to keep the Gemini app installed if it just sat in my Applications folder when I wasn’t using it. But it doesn’t, and Google shows no signs of caring, so I just deleted it and uninstalled its background launch agents (in <code>~/Library/LaunchAgents/</code>). Feels great, like I took a much needed shower.</p>
  932.  
  933. <p>(<strong>Sidenote:</strong> The Gemini Mac app is a native Mac app, but it is ... weird. <a href="https://mastodon.social/@ccgus/116410242771350931">Gus Mueller poked around at it</a> and found that it’s the product of a Java-to-Objective-C converter that Google made, and much of it was originally written for Android.)</p>
  934.  
  935. <div>
  936. <a  title="Permanent link to ‘Google’s Gemini Mac App Is Native, in a Distinctly Google Way, But Annoyingly Presumptuous’"  href="https://daringfireball.net/linked/2026/06/04/google-gemini-mac">&nbsp;★&nbsp;</a>
  937. </div>
  938.  
  939. ]]></content>
  940.  </entry><entry>
  941. <title>The AI-Driven Resurgence of Native Mac App Development</title>
  942. <link rel="alternate" type="text/html" href="https://sixcolors.com/post/2026/06/road-to-wwdc-2026-whats-a-developer/" />
  943. <link rel="shorturl" type="text/html" href="http://df4.us/x8r" />
  944. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/04/the-ai-driven-resurgence-of-mac-app-development" />
  945. <id>tag:daringfireball.net,2026:/linked//6.43083</id>
  946. <published>2026-06-04T13:43:26Z</published>
  947. <updated>2026-06-04T13:47:33Z</updated>
  948. <author>
  949. <name>John Gruber</name>
  950. <uri>http://daringfireball.net/</uri>
  951. </author>
  952. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  953. <p>Jason Snell at Six Colors, looking ahead to WWDC next week:</p>
  954.  
  955. <blockquote>
  956.  <p>These days, I’m getting emails pitching me for an endless stream
  957. of new Mac apps. It’s quite remarkable because there was a
  958. period five or ten years ago when it seemed like all app
  959. development on Apple’s platforms was focused on iOS. Even more
  960. interesting, these are all indie Mac apps that seem to be built
  961. using native Mac frameworks, not the product of big corporations
  962. that are just rolling their cross-platform development system
  963. out everywhere. These apps seem to have a point of view and are
  964. focused on the Mac.</p>
  965.  
  966. <p>Of course, it’s happening because of AI. [...]</p>
  967.  
  968. <p>Mac users — some of them developers, some of them people who have
  969. never written software in their lives — are building apps that
  970. fulfill their imaginations.</p>
  971.  
  972. <p>We now live in an era where, if you can dream an app, you can
  973. probably build it. Especially Mac utilities. And who cares more
  974. about native Mac software than Mac users? Certainly not those
  975. companies that gave up on Mac development and focused all their
  976. energies on giant cross-platform code bases to attract venture
  977. investment and big payouts.</p>
  978. </blockquote>
  979.  
  980. <p>There are pros and cons to everything, but on the whole, AI-assisted programming has rejuvenated Mac development. It wasn’t moribund, but it was stagnant. And stagnation is the first step toward decline. Now it’s resurgent, and that’s a fun thing to see. And, I think, genuinely important for the future of the platform. I’ve been concerned for years that the biggest problem the Mac faces is that so many new apps for the platform <a href="https://daringfireball.net/2018/12/electron_and_the_decline_of_native_apps">weren’t Mac apps</a>. The Mac has never faced a decline in popularity, but truly native Mac application development (and the skills) did. Now it’s turning around. Mac users are thirsty for Mac apps, and with AI, they can quench their own thirst and tell the dullards promulgating Electron bundles to pound sand.</p>
  981.  
  982. <p>(And Snell, it turns out, <a href="https://www.theincomparable.com/doubleender/">has joined the party</a>.)</p>
  983.  
  984. <div>
  985. <a  title="Permanent link to ‘The AI-Driven Resurgence of Native Mac App Development’"  href="https://daringfireball.net/linked/2026/06/04/the-ai-driven-resurgence-of-mac-app-development">&nbsp;★&nbsp;</a>
  986. </div>
  987.  
  988. ]]></content>
  989.  </entry><entry>
  990. <title>Another Gem From the Annals of Nick Bilton Jackassery</title>
  991. <link rel="alternate" type="text/html" href="https://daringfireball.net/linked/2015/03/20/bilton-pseudoscience" />
  992. <link rel="shorturl" type="text/html" href="http://df4.us/x8q" />
  993. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/03/another-gem-from-the-annals-of-nick-bilton-jackassery" />
  994. <id>tag:daringfireball.net,2026:/linked//6.43082</id>
  995. <published>2026-06-04T02:26:50Z</published>
  996. <updated>2026-06-04T02:26:50Z</updated>
  997. <author>
  998. <name>John Gruber</name>
  999. <uri>http://daringfireball.net/</uri>
  1000. </author>
  1001. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1002. <p>I look forward to pseudoscience like this finally getting some airtime on 60 Minutes. For 58 long years the program has been hopelessly biased toward actual science.</p>
  1003.  
  1004. <div>
  1005. <a  title="Permanent link to ‘Another Gem From the Annals of Nick Bilton Jackassery’"  href="https://daringfireball.net/linked/2026/06/03/another-gem-from-the-annals-of-nick-bilton-jackassery">&nbsp;★&nbsp;</a>
  1006. </div>
  1007.  
  1008. ]]></content>
  1009.  </entry><entry>
  1010. <title>If There’s One Thing Nick Bilton Knows, It’s Television</title>
  1011. <link rel="alternate" type="text/html" href="https://daringfireball.net/linked/2011/10/27/bilton-itv" />
  1012. <link rel="shorturl" type="text/html" href="http://df4.us/x8p" />
  1013. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/03/nick-bilton-tv-genius" />
  1014. <id>tag:daringfireball.net,2026:/linked//6.43081</id>
  1015. <published>2026-06-04T02:23:25Z</published>
  1016. <updated>2026-06-04T20:18:40Z</updated>
  1017. <author>
  1018. <name>John Gruber</name>
  1019. <uri>http://daringfireball.net/</uri>
  1020. </author>
  1021. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1022. <p>Back in 2011, when he was a tech columnist at The New York Times, Nick Bilton figured out that Apple was soon going to launch an Apple branded-television set, with no remote control. You’d just talk to it. This made no sense of course, <a href="https://daringfireball.net/linked/2011/10/27/bilton-itv">as I pointed out</a>.</p>
  1023.  
  1024. <p><a href="https://daringfireball.net/linked/2011/10/27/bilton-itv">Bilton closed his column thus</a>:</p>
  1025.  
  1026. <blockquote>
  1027.  <p>The company is now close enough that it could announce the product
  1028. by late 2012, releasing it to consumers by 2013.</p>
  1029.  
  1030. <p>It is coming though. It’s not a matter of if, it’s a matter
  1031. of when.</p>
  1032. </blockquote>
  1033.  
  1034. <p>Maybe it’ll launch in time for Bilton’s first season at the helm of 60 Minutes this fall, <a href="https://bsky.app/profile/nytpitchbot.bsky.social/post/3mnfmdyaers2h">with his all-new lineup of correspondents</a>.</p>
  1035.  
  1036. <div>
  1037. <a  title="Permanent link to ‘If There’s One Thing Nick Bilton Knows, It’s Television’"  href="https://daringfireball.net/linked/2026/06/03/nick-bilton-tv-genius">&nbsp;★&nbsp;</a>
  1038. </div>
  1039.  
  1040. ]]></content>
  1041.  </entry><entry>
  1042. <title>Scott Pelley on Leaving ‘60 Minutes’: ‘Incompetence and Unprofessionalism in the New Management Have Wreaked Havoc’</title>
  1043. <link rel="alternate" type="text/html" href="https://www.instagram.com/p/DZHlWAoG3_3/?img_index=1" />
  1044. <link rel="shorturl" type="text/html" href="http://df4.us/x8o" />
  1045. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/03/pelley-statement" />
  1046. <id>tag:daringfireball.net,2026:/linked//6.43080</id>
  1047. <published>2026-06-03T23:19:28Z</published>
  1048. <updated>2026-06-04T00:56:53Z</updated>
  1049. <author>
  1050. <name>John Gruber</name>
  1051. <uri>http://daringfireball.net/</uri>
  1052. </author>
  1053. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1054. <p>Scott Pelley, in a statement posted on Instagram (which I’ll quote in full, as the original is locked behind a <a href="https://daringfireball.net/2026/05/what_is_a_dickover">dickwall</a> if you’re not signed in to an Instagram account):</p>
  1055.  
  1056. <blockquote>
  1057.  <p>There has never been anything in America like 60 Minutes.</p>
  1058.  
  1059. <p>The Sunday tradition is the most successful program of any kind in
  1060. history. For more than a decade, its innovative growth on every
  1061. major online platform has extended its reach to countless millions
  1062. around the world. This spring, at the end of our 58th season, 60
  1063. Minutes grew rapidly with an unheard-of 9% jump in viewers on CBS.</p>
  1064.  
  1065. <p>“60” has been the number-one program in America for decades
  1066. because our beloved audience finds integrity, quality, and
  1067. humanity in our stories. When stewardship of the program passed to
  1068. my colleagues and me, our responsibility was to expand
  1069. energetically into a new age of media technology while preserving
  1070. the values our audience expects. Now, the new owner of our network
  1071. is casting this legend aside, apparently to curry a moment of
  1072. favor with the Trump administration.</p>
  1073.  
  1074. <p>The waste is heartbreaking.</p>
  1075.  
  1076. <p>Last month, 60 Minutes lost its DNA when our entire senior
  1077. leadership and two of our best on-air correspondents were cruelly
  1078. fired without cause. Good people were silenced because they stood
  1079. up for our audience. They stood for fairness against the forces of
  1080. political bias; they stood for professionalism against chaos.</p>
  1081.  
  1082. <p>For my part, new management has instructed me to inject falsehoods
  1083. and bias into a politically sensitive story. I’ve been told to
  1084. include assertions that are unverified. To date, in every case, I
  1085. have managed to ignore these instructions or refuse them.</p>
  1086.  
  1087. <p>Recently, politicians have been invited to choose correspondents
  1088. for interviews on the broadcast. Giving politicians control over
  1089. 60 Minutes interviews is not how honest journalism is done.
  1090. Finally, incompetence and unprofessionalism in the new
  1091. management have wreaked havoc. In a case involving one of my
  1092. stories, the entire program came within 19 minutes of not
  1093. getting on the air at all.</p>
  1094.  
  1095. <p>At 60 Minutes, we have fought harder than anyone knows to save the
  1096. program that became an American icon. We owed that to our millions
  1097. of viewers. I am deeply moved by the thousands of wishes we have
  1098. received to “keep up the good fight.” Most of my colleagues at CBS
  1099. News are still in that fight. But now the collapse of values at
  1100. the top has become untenable. The leadership of 60 Minutes is no
  1101. longer recognizable. The principles I hold dear are gone, and so I
  1102. must leave as well.</p>
  1103.  
  1104. <p>I depart after 37 years at CBS with one emotion — a heart
  1105. brimming with gratitude for the men and women of CBS News who
  1106. encouraged and enriched my work, very often at the risk of
  1107. their own lives. I pray for a day when those people and their
  1108. ideals are honored again — a day when sanity, competence, and
  1109. courage return.</p>
  1110. </blockquote>
  1111.  
  1112. <div>
  1113. <a  title="Permanent link to ‘Scott Pelley on Leaving ‘60 Minutes’: ‘Incompetence and Unprofessionalism in the New Management Have Wreaked Havoc’’"  href="https://daringfireball.net/linked/2026/06/03/pelley-statement">&nbsp;★&nbsp;</a>
  1114. </div>
  1115.  
  1116. ]]></content>
  1117.  </entry><entry>
  1118. <title>The ‘60 Minutes’ Purge</title>
  1119. <link rel="alternate" type="text/html" href="https://www.paramountpressexpress.com/cbs-news-and-stations/shows/60-minutes/talent/" />
  1120. <link rel="shorturl" type="text/html" href="http://df4.us/x8n" />
  1121. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/03/the-60-minutes-purge" />
  1122. <id>tag:daringfireball.net,2026:/linked//6.43079</id>
  1123. <published>2026-06-03T21:32:52Z</published>
  1124. <updated>2026-06-04T20:44:18Z</updated>
  1125. <author>
  1126. <name>John Gruber</name>
  1127. <uri>http://daringfireball.net/</uri>
  1128. </author>
  1129. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1130. <p>Paramount’s “Press Express” page promoting 60 Minutes still lists all eight correspondents from the 2025–2026 season, the program’s 58th. (Perhaps they fired the person responsible for keeping the cast page up to date.) In the order they appear on Paramount’s listing:</p>
  1131.  
  1132. <ul>
  1133. <li>Lesley Stahl</li>
  1134. <li><s>Scott Pelley</s> — <a href="https://daringfireball.net/linked/2026/06/03/cbs-news-fires-scott-pelley">fired today</a></li>
  1135. <li>Bill Whitaker</li>
  1136. <li><s>Anderson Cooper</s> — <a href="https://deadline.com/2026/05/anderson-cooper-signs-off-60-minutes-1236913958/">left on his own after 20 years</a></li>
  1137. <li><s>Sharyn Alfonsi</s> — <a href="https://www.poynter.org/commentary/2026/60-minutes-tanya-simon-fired/">fired last week</a></li>
  1138. <li>L. Jon Wertheim</li>
  1139. <li><s>Cecilia Vega</s> — <a href="https://www.poynter.org/commentary/2026/60-minutes-tanya-simon-fired/">fired last week</a></li>
  1140. <li>Norah O’Donnell</li>
  1141. </ul>
  1142.  
  1143. <p>A big part of the brand for 60 Minutes is that the show doesn’t change. Someone who last saw it 40 years ago would instantly recognize it today. There’s no silly fucking theme song. There’s no glossy set. There’s a ticking stopwatch, a logotype set in Microgramma/Eurostile, and correspondents sit against a black background. And correspondents measure their tenure not by years but by decades. <a href="https://en.wikipedia.org/wiki/60_Minutes#Correspondents_and_hosts">Of the original hosts</a>, Harry Reasoner was there for 23 years (and left the cast only upon his death at 68 in 1991), Dan Rather was there for 38 years, Mike Wallace for 40, and Morley Safer for 48. 48 years! Of the current hosts, <a href="https://www.cbsnews.com/news/60-minutes-40-years-at-the-top/">Lesley Stahl has been there since 1991</a>. I graduated high school that year.</p>
  1144.  
  1145. <p>In just six months since David Ellison bought CBS and <a href="https://www.newyorker.com/magazine/2026/01/26/inside-bari-weisss-hostile-takeover-of-cbs-news">installed Bari Weiss as editor-in-chief of CBS News</a>, they’ve fired or lost half their on-air talent, and of the four who remain, Wertheim and O’Donnell are only part-time (O’Donnell’s title is “CBS News senior correspondent”, not “60 Minutes correspondent”), Whitaker is 74 years old, and Stahl is 84.</p>
  1146.  
  1147. <p>Behind the cameras, longtime executive producer <a href="https://daringfireball.net/linked/2025/04/28/60-minutes-last-minute">Bill Owens resigned in protest of corporate interference</a> a year ago, in the cowardly run-up to Ellison’s acquisition of CBS. Last week Weiss fired Owens’s successor, <a href="https://www.poynter.org/commentary/2026/60-minutes-tanya-simon-fired/">Tanya Simon</a>, who had been with the program for 30 years, replacing her with Nick Bilton, who not only had never worked at 60 Minutes, but has never worked in TV news period. Weiss also fired executive editor Draggan Mihailovich, <a href="https://deadline.com/2025/08/draggan-mihailovich-60-minutes-executive-editor-1236494670/">who’d been at the show for 28 years</a>.</p>
  1148.  
  1149. <p>It seems untenable for Stahl or Whitaker to remain on the show. Pelley called it what it was in Bilton’s ham-fisted staff meeting Monday: the murder of the institution.</p>
  1150.  
  1151. <div>
  1152. <a  title="Permanent link to ‘The ‘60 Minutes’ Purge’"  href="https://daringfireball.net/linked/2026/06/03/the-60-minutes-purge">&nbsp;★&nbsp;</a>
  1153. </div>
  1154.  
  1155. ]]></content>
  1156.  </entry><entry>
  1157. <title>CBS News Fires Scott Pelley of ‘60 Minutes’</title>
  1158. <link rel="alternate" type="text/html" href="https://www.nytimes.com/2026/06/02/business/media/scott-pelley-cbs-bari-weiss.html" />
  1159. <link rel="shorturl" type="text/html" href="http://df4.us/x8m" />
  1160. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/03/cbs-news-fires-scott-pelley" />
  1161. <id>tag:daringfireball.net,2026:/linked//6.43078</id>
  1162. <published>2026-06-03T19:49:56Z</published>
  1163. <updated>2026-06-03T19:50:42Z</updated>
  1164. <author>
  1165. <name>John Gruber</name>
  1166. <uri>http://daringfireball.net/</uri>
  1167. </author>
  1168. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1169. <p>Benjamin Mullin and Michael M. Grynbaum:</p>
  1170.  
  1171. <blockquote>
  1172.  <p>In a <a href="https://static01.nyt.com/newsgraphics/documenttools/bb744b828c885269/9642cb98-full.pdf">formal letter</a> to Mr. Pelley, which was obtained by The
  1173. New York Times, Mr. Bilton wrote that the correspondent had been
  1174. “terminated for cause effective immediately.”</p>
  1175. </blockquote>
  1176.  
  1177. <p>The letter is a must-read. No summary of it can capture just how pathetic a man Nick Bilton is. He disputes nothing Pelley said in the Monday staff meeting, and firing Pelley proves that Pelley was exactly right.</p>
  1178.  
  1179. <blockquote>
  1180.  <p>Mr. Pelley, in a telephone interview on Tuesday evening shortly
  1181. after he was fired, said he had devoted decades of his life to “60
  1182. Minutes,” which he said he still cared about deeply.</p>
  1183.  
  1184. <p>“I have been in combat in Afghanistan,” Mr. Pelley said. “I have
  1185. been in combat in Iraq. I have been in the war zone in Ukraine
  1186. multiple times, risking my life and the happiness of my family
  1187. because of my devotion to the broadcast.” [...]</p>
  1188.  
  1189. <p>Earlier on Tuesday, Mr. Pelley sent a statement to The Times that
  1190. assailed the new leadership of CBS News, writing that
  1191. “incompetence and unprofessionalism in the new management have
  1192. wreaked havoc” at the network.” He added, “The collapse of values
  1193. at the top has become untenable.” Mr. Pelley also wrote that
  1194. senior managers at CBS News had pressured him to insert bias into
  1195. stories for “60 Minutes” this past season, though he did not
  1196. provide details about specific segments.</p>
  1197. </blockquote>
  1198.  
  1199. <p>I look forward to hearing those segment-specific details. It’s not hard to guess the direction that bias went.</p>
  1200.  
  1201. <div>
  1202. <a  title="Permanent link to ‘CBS News Fires Scott Pelley of ‘60 Minutes’’"  href="https://daringfireball.net/linked/2026/06/03/cbs-news-fires-scott-pelley">&nbsp;★&nbsp;</a>
  1203. </div>
  1204.  
  1205. ]]></content>
  1206.  </entry><entry>
  1207. <title>The Underworld Market to Remove the Recording Indicator Light on Meta Glasses</title>
  1208. <link rel="alternate" type="text/html" href="https://www.youtube.com/watch?v=EaJSPeJmqis" />
  1209. <link rel="shorturl" type="text/html" href="http://df4.us/x8l" />
  1210. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/03/the-underworld-market-to-remove-the-recording-indicator-light-on-meta-glasses" />
  1211. <id>tag:daringfireball.net,2026:/linked//6.43077</id>
  1212. <published>2026-06-03T19:39:13Z</published>
  1213. <updated>2026-06-03T19:39:14Z</updated>
  1214. <author>
  1215. <name>John Gruber</name>
  1216. <uri>http://daringfireball.net/</uri>
  1217. </author>
  1218. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1219. <p>Joanna Stern, on YouTube:</p>
  1220.  
  1221. <blockquote>
  1222.  <p>People across the country are offering a service on Facebook
  1223. Marketplace to disable the recording light on Ray-Ban Meta
  1224. glasses. They call it “Stealth Mode.” Joanna paid $100 for the
  1225. modification and went inside the growing business of turning smart
  1226. glasses into covert cameras. She investigates who is doing it,
  1227. whether it’s legal and what some are doing to try and stop it.</p>
  1228. </blockquote>
  1229.  
  1230. <p>Of course there’s a market for this. But the true chef’s kiss is that the market to find people who offer the service is on ... Facebook Marketplace. Using a Meta platform to find people to hack a Meta device so you can surreptitiously record strangers. So perfectly Meta.</p>
  1231.  
  1232. <div>
  1233. <a  title="Permanent link to ‘The Underworld Market to Remove the Recording Indicator Light on Meta Glasses’"  href="https://daringfireball.net/linked/2026/06/03/the-underworld-market-to-remove-the-recording-indicator-light-on-meta-glasses">&nbsp;★&nbsp;</a>
  1234. </div>
  1235.  
  1236. ]]></content>
  1237.  </entry><entry>
  1238. <title>Meta Reportedly Has a Slew of New Smart Glasses Planned for This Year</title>
  1239. <link rel="alternate" type="text/html" href="https://gizmodo.com/meta-has-a-ridiculous-amount-of-smart-glasses-planned-for-this-year-2000765741" />
  1240. <link rel="shorturl" type="text/html" href="http://df4.us/x8k" />
  1241. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/02/meta-glasses-this-year" />
  1242. <id>tag:daringfireball.net,2026:/linked//6.43076</id>
  1243. <published>2026-06-02T21:54:43Z</published>
  1244. <updated>2026-06-02T21:54:43Z</updated>
  1245. <author>
  1246. <name>John Gruber</name>
  1247. <uri>http://daringfireball.net/</uri>
  1248. </author>
  1249. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1250. <p>James Pero, summarizing for Gizmodo <a href="https://www.theinformation.com/articles/meta-memo-outlines-ambitious-hardware-plans-including-new-ai-pendant">this paywalled report by Jyoti Mann</a> for The Information:</p>
  1251.  
  1252. <blockquote>
  1253.  <p>But, wait, there’s more: in addition to the fall releases, The
  1254. Information reports that Meta also has a pair slated for December,
  1255. codenamed “Mojito VIP.” There are also two prototypes being tested
  1256. in the fall, according to the report, including one called
  1257. “Artemis” and another called “SSG,” which is short for
  1258. “supersensing glasses.”</p>
  1259.  
  1260. <p>The Information <a href="https://www.theinformation.com/articles/meta-renews-work-facial-recognition-tech-privacy-worries-fade">previously reported</a> that the “supersensing”
  1261. pair would have always-on cameras capable of looking at your
  1262. surroundings without you having to prompt the voice assistant or
  1263. activate the camera with a button. The idea here is that, with a
  1264. constant stream of visual information, the smart glasses could be
  1265. a kind of ambient virtual assistant that remembers where you left
  1266. your keys or other vision-based reminders.</p>
  1267. </blockquote>
  1268.  
  1269. <p>Spitball: Meta’s entire business is predicated on knowing as much about people as possible. Their interest in building out a virtual “metaverse” world was motivated by the fact they could track everything people do, see, say, and hear there. That <a href="https://daringfireball.net/linked/2026/06/01/the-metaverse-fever-dream">didn’t play out</a> so they’re pivoting to building out devices that will let them track everything people do, see, say, and hear in the real world.</p>
  1270.  
  1271. <div>
  1272. <a  title="Permanent link to ‘Meta Reportedly Has a Slew of New Smart Glasses Planned for This Year’"  href="https://daringfireball.net/linked/2026/06/02/meta-glasses-this-year">&nbsp;★&nbsp;</a>
  1273. </div>
  1274.  
  1275. ]]></content>
  1276.  </entry><entry>
  1277. <title>Apple, the Anti-‘Metaverse’ VR Company</title>
  1278. <link rel="alternate" type="text/html" href="https://daringfireball.net/2025/12/meta_says_fuck_that_metaverse_shit" />
  1279. <link rel="shorturl" type="text/html" href="http://df4.us/x8j" />
  1280. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/02/apple-the-anti-metaverse-vr-company" />
  1281. <id>tag:daringfireball.net,2026:/linked//6.43075</id>
  1282. <published>2026-06-02T20:48:08Z</published>
  1283. <updated>2026-06-02T20:48:09Z</updated>
  1284. <author>
  1285. <name>John Gruber</name>
  1286. <uri>http://daringfireball.net/</uri>
  1287. </author>
  1288. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1289. <p>One <a href="https://daringfireball.net/linked/2026/06/02/the-metaverse-was-snake-oil-for-isolation">more</a> bit of “<a href="https://daringfireball.net/linked/2026/06/01/the-metaverse-fever-dream">metaverse fever dream</a>” follow-up. The one company in the field that Nick Heer doesn’t mention is Apple, makers of the best-known (albeit not best-selling) virtual reality headset. Think and say what you want about the Vision platform (<a href="https://daringfireball.net/2026/04/on_the_future_of_apples_vision_platform">I still think</a> it’s the first inning of a long game), but no one at Apple ever once gave a hint of endorsing “metaverse” hype. In fact, <a href="https://daringfireball.net/2025/12/meta_says_fuck_that_metaverse_shit">as I’ve noted before</a>, at a 2022 WSJ event, seven months before Vision Pro was <em>announced</em> and over a year before it was released, <a href="https://www.youtube.com/watch?v=m-ugwoEOMvg&amp;t=1770s">Joanna Stern asked Greg Joswiak and Craig Federighi</a>:</p>
  1290.  
  1291. <blockquote>
  1292.  <p><strong>Stern:</strong> You have to finish this sentence, both of you. The
  1293. metaverse is...</p>
  1294.  
  1295. <p><strong>Joz:</strong> A word I’ll never use.</p>
  1296. </blockquote>
  1297.  
  1298. <p>“Fever dream” is right.</p>
  1299.  
  1300. <div>
  1301. <a  title="Permanent link to ‘Apple, the Anti-‘Metaverse’ VR Company’"  href="https://daringfireball.net/linked/2026/06/02/apple-the-anti-metaverse-vr-company">&nbsp;★&nbsp;</a>
  1302. </div>
  1303.  
  1304. ]]></content>
  1305.  </entry><entry>
  1306. <title>The Metaverse Was Snake Oil for Isolation</title>
  1307. <link rel="alternate" type="text/html" href="https://daringfireball.net/linked/2026/06/01/the-metaverse-fever-dream" />
  1308. <link rel="shorturl" type="text/html" href="http://df4.us/x8i" />
  1309. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/02/the-metaverse-was-snake-oil-for-isolation" />
  1310. <id>tag:daringfireball.net,2026:/linked//6.43074</id>
  1311. <published>2026-06-02T20:42:33Z</published>
  1312. <updated>2026-06-04T20:49:52Z</updated>
  1313. <author>
  1314. <name>John Gruber</name>
  1315. <uri>http://daringfireball.net/</uri>
  1316. </author>
  1317. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1318. <p>A follow-up point from <a href="https://daringfireball.net/linked/2026/06/01/the-metaverse-fever-dream">my post yesterday linking to</a> Nick Heer’s blockbuster “<a href="https://pxlnv.com/blog/metaverse-fever-dream/">The Metaverse Fever Dream</a>”. In particular, the connection Heer draws between the rise of “metaverse” hype and the pandemic.</p>
  1319.  
  1320. <p>I always sort of knew that metaverse hype roughly coincided with the Covid lockdown and our collective period of isolation and loneliness, a year-plus stretch when we relied mostly on computer platforms for nearly all socializing. But here in 2026 it’s now clear that metaverse hype and lockdown-induced isolation coincided precisely. They didn’t roughly overlap; they exactly overlapped. So much so that I’m now wondering if any of the “metaverse” hype would have happened if Covid hadn’t happened. Facebook still likely would’ve renamed itself, <a href="https://om.co/2025/04/28/no-gruber-this-is-why-facebook-renamed-itself/">because they’d so poisoned the “Facebook” brand itself</a>, but maybe to <a href="https://daringfireball.net/linked/2025/04/28/om-malik-facebook-rename">something other than “Meta”</a>.</p>
  1321.  
  1322. <p>We allowed the necessary <em>initial</em> emergency lockdown to extend indefinitely because it seemed like <em>maybe we could get by</em> for a long stretch using technology. The extended lockdown never would have happened if the Covid pandemic had broken out 20 or more years earlier. In 2020 and 2021, we could squint and say, sure, maybe kids can “go to school” via Zoom. We never would have kept all kids home for an entire year pre-Zoom. But the truth is Zoom “school” <a href="https://www.nationsreportcard.gov/highlights/ltt/2022/">wasn’t much better than no school at all</a>. Same for Zoom “work collaboration”, and Zoom “friend gatherings”. It was an illusion that today’s technology is even close to a sufficient substitute for being in each others’ physical presence. The siren call of “the metaverse” was exactly what we craved — technology that <em>would</em> be a sufficient substitute for real-world experiences and socializing. The best audience for snake oil are people with actual ailments. And during Covid, we were all ailing socially.</p>
  1323.  
  1324. <div>
  1325. <a  title="Permanent link to ‘The Metaverse Was Snake Oil for Isolation’"  href="https://daringfireball.net/linked/2026/06/02/the-metaverse-was-snake-oil-for-isolation">&nbsp;★&nbsp;</a>
  1326. </div>
  1327.  
  1328. ]]></content>
  1329.  </entry><entry>
  1330. <title>Scott Pelley Accuses CBS News Boss of ‘Murdering’ ‘60 Minutes’</title>
  1331. <link rel="alternate" type="text/html" href="https://www.nytimes.com/2026/06/01/business/media/cbs-60-minutes-scott-pelley-nick-bilton.html?unlocked_article_code=1.nFA.TDGJ.HbBmlXuQWmcQ&amp;smid=url-share" />
  1332. <link rel="shorturl" type="text/html" href="http://df4.us/x8h" />
  1333. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/02/pelley-60-minutes-murder" />
  1334. <id>tag:daringfireball.net,2026:/linked//6.43073</id>
  1335. <published>2026-06-02T19:53:47Z</published>
  1336. <updated>2026-06-02T21:22:20Z</updated>
  1337. <author>
  1338. <name>John Gruber</name>
  1339. <uri>http://daringfireball.net/</uri>
  1340. </author>
  1341. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1342. <p>Michael M. Grynbaum and Benjamin Mullin, reporting for The New York Times (gift link):</p>
  1343.  
  1344. <blockquote>
  1345.  <p>CBS News faced a fresh wave of turmoil on Monday after Scott
  1346. Pelley, the “60 Minutes” correspondent, laced into the show’s
  1347. newly hired executive producer during a staff meeting and accused
  1348. Bari Weiss, the network’s editor in chief, of “murdering” the
  1349. longstanding Sunday news program.</p>
  1350.  
  1351. <p>In an extraordinary exchange, Mr. Pelley, his newscaster’s
  1352. baritone sometimes shaking in anger, told Nick Bilton, the new
  1353. executive producer, that he had “slender” qualifications for his
  1354. new job and questioned the network’s commitment to the future of
  1355. the program, according to a recording of the meeting obtained by
  1356. The New York Times.</p>
  1357.  
  1358. <p>The 10 a.m. gathering, held at the program’s Midtown Manhattan
  1359. headquarters, was intended as a formal introduction to Mr. Bilton,
  1360. a tech journalist and filmmaker who was appointed last week as
  1361. part of a major shake-up at “60 Minutes.” CBS fired Tanya Simon,
  1362. the previous executive producer, and her deputy, along with Sharyn
  1363. Alfonsi and Cecilia Vega, two of the show’s correspondents — an
  1364. event that Mr. Pelley referred to as “Black Thursday.”</p>
  1365. </blockquote>
  1366.  
  1367. <p>It’s worth noting that the night before the firings, 60 Minutes won two news Emmys. It’s even more worth noting that 60 Minutes’s TV ratings <a href="https://barrettmedia.com/2026/05/22/60-minutes-ratings-increase-2026-season/">were <em>up</em> 9 percent</a> year-over-year, and <a href="https://www.paramountpressexpress.com/cbs-news-and-stations/shows/60-minutes/releases/?view=112909-60-minutes-makes-television-history-by-marking-52-straight-seasons-as-americas-1-news-program">digital video views doubled</a>. In both quality and popularity, the show is thriving, not struggling. (See also: The Late Show With Stephen Colbert was, by far, <a href="https://latenighter.com/news/ratings/late-night-tv-ratings-q4-2025/">the top-rated late night talk show</a>.)</p>
  1368.  
  1369. <blockquote>
  1370.  <p>“Broadcast is an ice cube that is melting, OK?” Mr. Bilton said,
  1371. saying the show had to adapt. “Bari loves this institution,” he
  1372. added. “She loves ’60 Minutes.’”</p>
  1373.  
  1374. <p>At that, Mr. Pelley interrupted.</p>
  1375.  
  1376. <p>“She is murdering ‘60 Minutes,’” the correspondent said. “She does
  1377. not love this place. She was brought in to kill it, and she’s been
  1378. doing exactly that.”</p>
  1379.  
  1380. <p>Mr. Pelley added: “She has no qualifications for her job; you have
  1381. slender qualifications for this job. The changes that she’s made
  1382. at the ‘Evening News’ have been catastrophic, so why should we
  1383. expect that any of this is going to be any better?”</p>
  1384. </blockquote>
  1385.  
  1386. <p>Oof.</p>
  1387.  
  1388. <p>Oliver Darcy obtained a recording of the entire Bilton-Pelley exchange, and transcribed much of it, but <a href="https://www.status.news/p/scott-pelley-60-minutes-nick-bilton-bari-weiss">it’s behind the (worth it!) Status paywall</a>.</p>
  1389.  
  1390. <div>
  1391. <a  title="Permanent link to ‘Scott Pelley Accuses CBS News Boss of ‘Murdering’ ‘60 Minutes’’"  href="https://daringfireball.net/linked/2026/06/02/pelley-60-minutes-murder">&nbsp;★&nbsp;</a>
  1392. </div>
  1393.  
  1394. ]]></content>
  1395.  </entry><entry>
  1396. <title>Three Ways to Get Paid</title>
  1397. <link rel="alternate" type="text/html" href="https://jasonzweig.com/three-ways-to-get-paid/" />
  1398. <link rel="shorturl" type="text/html" href="http://df4.us/x8g" />
  1399. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/02/zweig-three-ways-to-get-paid" />
  1400. <id>tag:daringfireball.net,2026:/linked//6.43072</id>
  1401. <published>2026-06-02T16:10:24Z</published>
  1402. <updated>2026-06-02T16:10:25Z</updated>
  1403. <author>
  1404. <name>John Gruber</name>
  1405. <uri>http://daringfireball.net/</uri>
  1406. </author>
  1407. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1408. <p>Jason Zweig, back in 2018:</p>
  1409.  
  1410. <blockquote>
  1411.  <p><em><a href="http://jasonzweig.com/on-fathers-day/">My father</a>, who died in 1981, was an inexhaustible font of
  1412. wisdom and wit. I don’t know when he told me this particular
  1413. three-part rule, but I’ve never forgotten it. I tweeted it
  1414. three years ago, but people keep asking for it in one place, so
  1415. here it is.</em></p>
  1416.  
  1417. <p>There are three ways to make a living:</p>
  1418.  
  1419. <ol>
  1420. <li><p>Lie to people who want to be lied to, and you’ll get rich.</p></li>
  1421. <li><p>Tell the truth to those who want the truth, and you’ll make a
  1422. living.</p></li>
  1423. <li><p>Tell the truth to those who want to be lied to, and you’ll go
  1424. broke.</p></li>
  1425. </ol>
  1426.  
  1427. <p><em>The rest is commentary.</em></p>
  1428. </blockquote>
  1429.  
  1430. <p>Pairs well with Om Malik’s remarkable line about the success of “the grifters and the hucksters and the influencers selling impossible things” in his “<a href="https://om.co/2026/05/25/we-are-living-in-pinocchios-world/">We Are Living in Pinocchio’s World</a>” essay that I <a href="https://daringfireball.net/linked/2026/06/01/pinocchios-world">linked to yesterday</a>.</p>
  1431.  
  1432. <div>
  1433. <a  title="Permanent link to ‘Three Ways to Get Paid’"  href="https://daringfireball.net/linked/2026/06/02/zweig-three-ways-to-get-paid">&nbsp;★&nbsp;</a>
  1434. </div>
  1435.  
  1436. ]]></content>
  1437.  </entry><entry>
  1438. <title>The First-Time-Buyer-Discount Dickover Scheme</title>
  1439. <link rel="alternate" type="text/html" href="https://x.com/usgraphics/status/2060559523585355986" />
  1440. <link rel="shorturl" type="text/html" href="http://df4.us/x8f" />
  1441. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/02/blueball-dickovers" />
  1442. <id>tag:daringfireball.net,2026:/linked//6.43071</id>
  1443. <published>2026-06-02T15:08:12Z</published>
  1444. <updated>2026-06-02T15:56:30Z</updated>
  1445. <author>
  1446. <name>John Gruber</name>
  1447. <uri>http://daringfireball.net/</uri>
  1448. </author>
  1449. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1450. <p>Neil Panchal, on Twitter/X (<a href="https://xcancel.com/usgraphics/status/2060559523585355986">XCancel link</a>):</p>
  1451.  
  1452. <blockquote>
  1453.  <p>Of all the dickovers, the dickover that blueballs you with some
  1454. first-time buyer incentive. “Sign up and get 10% discount, new
  1455. accounts only”, the dickover boasts.</p>
  1456.  
  1457. <p>Never understood why you’d ever penalize returning customers with
  1458. a dickover, blue-balling them with 10% off teaser that they’re
  1459. ineligible for. wtf?</p>
  1460.  
  1461. <p>And for first time buyers, they’d always feel left out if they
  1462. don’t shove their email address in the dickover. The choice is
  1463. an illusion with a penalty of 10%. But wait… there’s more! You
  1464. only get a discount code if you, after clicking the confirmation
  1465. email link, also sign up for their SMS marketing. You just got
  1466. double dicked.</p>
  1467. </blockquote>
  1468.  
  1469. <p>I fell for this racket once, albeit with my eyes open. Last year I bought a cap from New Era’s website. They offered me some sort of discount for giving them my email address. I knew they were going to get my email anyway because I was going to buy the hat, so I figured why not. Only then — exactly as Panchal describes — did they say I also needed to give them my phone number and grant permission to text me marketing messages. Now I was pissed. I did it anyway, just to see what happened (and get the discount). As soon as I bought the hat, discount applied, I rescinded their permission to send me text messages <em>and</em> marketing emails. (They had already texted me like two marketing messages, in addition to the ones confirming my phone number.) Overall I’d have rather paid a few more dollars than go through the hassle, which is why my standard operating procedure is to decline all such entreaties. A real discount is just offering a lower price. Anything else is a scam of some sort.</p>
  1470.  
  1471. <p>But the real problem is that it completely soured my impression of New Era. I am far less likely to purchase from them again. I will eventually buy a New Era cap again — their actual products are excellent, and they are the exclusive maker of official MLB on-field caps — but if I can buy it elsewhere, I will. I’ll go out of my way to avoid buying direct from New Era for the rest of my life.</p>
  1472.  
  1473. <p>The marketing shitbirds who press for these schemes — and insist on adding <a href="https://daringfireball.net/2026/05/what_is_a_dickover">dickovers</a> and dickbars to websites — do so by pointing to data that shows that they do convert some number of users. “It works” they claim, pointing to data. What doesn’t show up in their data are interactions like mine. They don’t have analytics that measure that I now consider their website an antagonist to avoid at all costs.</p>
  1474.  
  1475. <div>
  1476. <a  title="Permanent link to ‘The First-Time-Buyer-Discount Dickover Scheme’"  href="https://daringfireball.net/linked/2026/06/02/blueball-dickovers">&nbsp;★&nbsp;</a>
  1477. </div>
  1478.  
  1479. ]]></content>
  1480.  </entry><entry>
  1481. <link rel="alternate" type="text/html" href="https://www.mux.com/?utm_campaign=fireball&amp;utm_source=DF" />
  1482. <link rel="shorturl" href="http://df4.us/x8e" />
  1483. <link rel="related" type="text/html" href="https://daringfireball.net/feeds/sponsors/2026/06/mux_video_for_developers" />
  1484. <id>tag:daringfireball.net,2026:/feeds/sponsors//11.43070</id>
  1485. <author><name>Daring Fireball Department of Commerce</name></author>
  1486. <published>2026-06-02T01:45:43Z</published>
  1487. <updated>2026-06-02T01:45:44Z</updated>
  1488. <content type="html" xml:base="https://daringfireball.net/feeds/sponsors/" xml:lang="en"><![CDATA[
  1489. <p>Mux is what developers reach for when they need to do more with video. Video files are packed with data and context waiting to be unlocked.</p>
  1490.  
  1491. <p>Mux Robots are AI workflows that unlock that data inside your video for summarization, caption translation, moderation, and more. Configure once and your workflows run automatically on new uploads.</p>
  1492.  
  1493. <p>Mux is video infrastructure trusted by Patreon, Substack, and Synthesia. Start building for free. Use code <strong>FIREBALL</strong> at signup for an extra $50 credit.</p>
  1494.  
  1495. <div>
  1496. <a  title="Permanent link to ‘Mux — Video for Developers’"  href="https://daringfireball.net/feeds/sponsors/2026/06/mux_video_for_developers">&nbsp;★&nbsp;</a>
  1497. </div>
  1498.  
  1499. ]]></content>
  1500. <title>[Sponsor] Mux — Video for Developers</title></entry><entry>
  1501. <title>‘The Metaverse Fever Dream’</title>
  1502. <link rel="alternate" type="text/html" href="https://pxlnv.com/blog/metaverse-fever-dream/" />
  1503. <link rel="shorturl" type="text/html" href="http://df4.us/x8d" />
  1504. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/01/the-metaverse-fever-dream" />
  1505. <id>tag:daringfireball.net,2026:/linked//6.43069</id>
  1506. <published>2026-06-02T00:24:39Z</published>
  1507. <updated>2026-06-02T20:43:16Z</updated>
  1508. <author>
  1509. <name>John Gruber</name>
  1510. <uri>http://daringfireball.net/</uri>
  1511. </author>
  1512. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1513. <p>Nick Heer, at Pixel Envy, last week published a remarkable essay surveying — with copious receipts — the rise and fall of “metaverse” hype:</p>
  1514.  
  1515. <blockquote>
  1516.  <p>The obsession with the metaverse seems to have solidified in
  1517. Silicon Valley after <a href="https://www.matthewball.co/all/themetaverse">Matthew Ball published</a> an essay in
  1518. January 2020 in which he forecasted that, at the very least…</p>
  1519.  
  1520. <blockquote>
  1521.  <p>…it is likely to produce trillions in value as a new computing
  1522. platform or content medium. But in its full vision, the Metaverse
  1523. becomes the gateway to most digital experiences, a key component
  1524. of all physical ones, and the next great labor platform. [...]</p>
  1525. </blockquote>
  1526.  
  1527. <p>Ball published this essay with darkly fortuitous timing. A week
  1528. earlier, Chinese health authorities had isolated a new strain of
  1529. coronavirus aggressively spreading in Wuhan; a day before, they
  1530. <a href="https://www.thelancet.com/journals/laninf/article/PIIS1473-3099(20)30011-6/fulltext">published its genetic sequence</a>. Within a couple of
  1531. months, the world had turned upside down and many of us were
  1532. suddenly spending our days in a space that felt more virtual than
  1533. physical. We may have only been working from home — or, at least,
  1534. those of us who had the option and were not laid off — and
  1535. socializing over Zoom, all while remembering the last concert we
  1536. went to or the last time we ate a meal in a restaurant.</p>
  1537. </blockquote>
  1538.  
  1539. <p>Just a tremendous piece of writing and reporting from Heer. What a pile of horseshit “the metaverse” as promulgated by Zuckerberg was. To call what Heer has assembled here, in a compelling narrative to boot, “comprehensive” is a vast understatement. These hucksters were selling a bill of goods and now they’re trying to whistle past their own hype:</p>
  1540.  
  1541. <blockquote>
  1542.  <p>As for the futurists like Hackl, who confidently proclaimed the
  1543. metaverse was “for certain”, they have found an out thanks to its
  1544. flexible definition. Jeff Barrett, of the Shorty Awards’ “It’s No
  1545. Fluke” podcast, published a <a href="https://creators.yahoo.com/lifestyle/story/why-cathy-hackl-keeps-getting-the-future-right-and-why-global-companies-are-paying-attention-155835963.html">glowing profile of “the Godmother of
  1546. the Metaverse”</a> earlier this year under the headline “Why
  1547. Cathy Hackl Keeps Getting the Future Right”. “When enthusiasm
  1548. cooled and narratives collapsed, many distanced themselves from
  1549. the space”, writes Barrett, noting with seeming approval that
  1550. “Hackl did the opposite. She reframed it”. Many people — perhaps
  1551. everyone, come to think of it — could predict the future if they
  1552. got to retcon their predictions to fit reality.</p>
  1553. </blockquote>
  1554.  
  1555. <p>Bravo.</p>
  1556.  
  1557. <p><strong>Follow-up:</strong> “<a href="https://daringfireball.net/linked/2026/06/02/the-metaverse-was-snake-oil-for-isolation">The Metaverse Was Snake Oil for Isolation</a>”.</p>
  1558.  
  1559. <div>
  1560. <a  title="Permanent link to ‘‘The Metaverse Fever Dream’’"  href="https://daringfireball.net/linked/2026/06/01/the-metaverse-fever-dream">&nbsp;★&nbsp;</a>
  1561. </div>
  1562.  
  1563. ]]></content>
  1564.  </entry><entry>
  1565. <title>‘If You Take the Weasel Job Then You Must Be the Weasel’</title>
  1566. <link rel="alternate" type="text/html" href="https://www.hamiltonnolan.com/p/if-you-take-the-weasel-job-then-you?r=qy6gq" />
  1567. <link rel="shorturl" type="text/html" href="http://df4.us/x8c" />
  1568. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/01/weasel-job-60-minutes" />
  1569. <id>tag:daringfireball.net,2026:/linked//6.43068</id>
  1570. <published>2026-06-01T23:31:54Z</published>
  1571. <updated>2026-06-01T23:31:54Z</updated>
  1572. <author>
  1573. <name>John Gruber</name>
  1574. <uri>http://daringfireball.net/</uri>
  1575. </author>
  1576. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1577. <p>Hamilton Nolan, writing at How Things Work:</p>
  1578.  
  1579. <blockquote>
  1580.  <p>There are only a few reasons why you might be hired for a
  1581. prestigious job that you are obviously not qualified for. One is
  1582. “they have recognized you for the genius that you are.” The urge
  1583. to conclude that this is, in fact, the reason must be
  1584. overwhelming, if you are the person in question. But this is
  1585. rarely the explanation.</p>
  1586.  
  1587. <p>Another possibility is “the person who hired you is a fucking
  1588. idiot.” This happens. A number of current United States cabinet
  1589. secretaries got their jobs this way.</p>
  1590.  
  1591. <p>The most likely reason, though — one that often overshadows the
  1592. other ones — is, “you are willing to carry out the dirty and
  1593. distasteful things to come.” This is why weird hirings at the top
  1594. always provoke dread among all the other employees. Maybe you are
  1595. a hidden gem, sure, but Occam’s Razor says that you are probably
  1596. just a hatchet man.</p>
  1597.  
  1598. <p>Nick Bilton, a former tech writer for the New York Times and
  1599. Vanity Fair and maker of a few documentaries, was <a href="https://www.hamiltonnolan.com/p/if-you-take-the-weasel-job-then-you?r=qy6gq">just hired</a> as
  1600. the new head of 60 Minutes.</p>
  1601. </blockquote>
  1602.  
  1603. <p>Bilton tried to introduce himself to the (remaining) staff at 60 Minutes this morning and <a href="https://www.status.news/p/scott-pelley-60-minutes-nick-bilton-bari-weiss">it did not go well</a>.</p>
  1604.  
  1605. <div>
  1606. <a  title="Permanent link to ‘‘If You Take the Weasel Job Then You Must Be the Weasel’’"  href="https://daringfireball.net/linked/2026/06/01/weasel-job-60-minutes">&nbsp;★&nbsp;</a>
  1607. </div>
  1608.  
  1609. ]]></content>
  1610.  </entry><entry>
  1611. <title>‘We Are Living in Pinocchio’s World’</title>
  1612. <link rel="alternate" type="text/html" href="https://om.co/2026/05/25/we-are-living-in-pinocchios-world/" />
  1613. <link rel="shorturl" type="text/html" href="http://df4.us/x8b" />
  1614. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/01/pinocchios-world" />
  1615. <id>tag:daringfireball.net,2026:/linked//6.43067</id>
  1616. <published>2026-06-01T20:05:17Z</published>
  1617. <updated>2026-06-02T16:03:07Z</updated>
  1618. <author>
  1619. <name>John Gruber</name>
  1620. <uri>http://daringfireball.net/</uri>
  1621. </author>
  1622. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1623. <p>Om Malik:</p>
  1624.  
  1625. <blockquote>
  1626.  <p><em>The Adventures of Pinocchio</em> was published in serial form in
  1627. 1881, aimed at Italian children in the way the 19th century
  1628. aimed things at children, full of suffering, consequence, and
  1629. moral instruction delivered through catastrophe. The puppet is
  1630. hanged. He is swallowed by a giant fish. He watches companions
  1631. degrade into beasts of burden. The world he moves through is
  1632. predatory at every level, and the institutions that should
  1633. protect him are either absent, corrupted, or actively hostile to
  1634. his interests. [...]</p>
  1635.  
  1636. <p>Most people remember <em>Pinocchio</em> as a story about lying. The nose
  1637. grows. You get caught. Lesson learned. But that reading misses
  1638. almost everything Collodi was actually doing. The book is a close
  1639. study of a society where deception has gone ambient, woven into
  1640. every institution, every transaction. Courts punish victims.
  1641. Authority figures perform competence without exercising it.
  1642. Experts are decorative. Society holds together through spectacle
  1643. and habit rather than accountability. Into this environment, a
  1644. naive creature is released, constitutionally unable to resist a
  1645. good story about easy reward.</p>
  1646.  
  1647. <p>The nose is the least interesting lie in the book. The interesting
  1648. lies are the ones that work.</p>
  1649. </blockquote>
  1650.  
  1651. <p>I’m not sure which sphere of interest this essay applies better to: post-AI tech, or post-Trump politics. I mean, goddamn, what a paragraph this one is:</p>
  1652.  
  1653. <blockquote>
  1654.  <p>The grifters and the hucksters and the influencers selling
  1655. impossible things succeed because audiences reward certainty and
  1656. punish doubt. They honor confidence and resist complication. A
  1657. clean story about a genius who will fix everything travels faster
  1658. than a difficult story about tradeoffs. The Field of Miracles
  1659. stays open because people keep wanting to bury their coins there.</p>
  1660. </blockquote>
  1661.  
  1662. <div>
  1663. <a  title="Permanent link to ‘‘We Are Living in Pinocchio’s World’’"  href="https://daringfireball.net/linked/2026/06/01/pinocchios-world">&nbsp;★&nbsp;</a>
  1664. </div>
  1665.  
  1666. ]]></content>
  1667.  </entry><entry>
  1668. <title>Amazon Made AI Podcasts for Products</title>
  1669. <link rel="alternate" type="text/html" href="https://www.businessinsider.com/amazon-ai-generated-podcasts-products-2026-4" />
  1670. <link rel="shorturl" type="text/html" href="http://df4.us/x8a" />
  1671. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/06/01/amazon-made-ai-podcasts-for-products" />
  1672. <id>tag:daringfireball.net,2026:/linked//6.43066</id>
  1673. <published>2026-06-01T16:41:51Z</published>
  1674. <updated>2026-06-01T18:22:54Z</updated>
  1675. <author>
  1676. <name>John Gruber</name>
  1677. <uri>http://daringfireball.net/</uri>
  1678. </author>
  1679. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1680. <p>Katie Notopoulos, a month ago at Business Insider:</p>
  1681.  
  1682. <blockquote>
  1683.  <p>Amazon has launched a new <a href="https://www.aboutamazon.com/news/retail/amazon-hear-the-highlights-join-the-chat">feature</a> that uses AI to generate a
  1684. short, podcast-like audio segment where two “hosts” discuss the
  1685. merits and reviews of a specific product.</p>
  1686.  
  1687. <p>I think it could be one of the funniest, closest endpoints to
  1688. human civilization we’ve seen yet in our new AI-enabled world. If
  1689. this sounds a little confusing, here’s an example. I tried it out
  1690. for diaper rash cream, and, voila! A podcast! (Sound on.)</p>
  1691. </blockquote>
  1692.  
  1693. <p>I don’t know what’s worse: that anyone at Amazon thought actual people would really listen to these, or if actual people really are listening to them.</p>
  1694.  
  1695. <div>
  1696. <a  title="Permanent link to ‘Amazon Made AI Podcasts for Products’"  href="https://daringfireball.net/linked/2026/06/01/amazon-made-ai-podcasts-for-products">&nbsp;★&nbsp;</a>
  1697. </div>
  1698.  
  1699. ]]></content>
  1700.  </entry><entry>
  1701. <title>The Talk Show Live From WWDC 2026: Tuesday June 9</title>
  1702. <link rel="alternate" type="text/html" href="https://ti.to/daringfireball/the-talk-show-live-from-wwdc-2026" />
  1703. <link rel="shorturl" type="text/html" href="http://df4.us/x88" />
  1704. <link rel="related" type="text/html" href="https://daringfireball.net/linked/2026/05/31/the-talk-show-live-tickets-2026" />
  1705. <id>tag:daringfireball.net,2026:/linked//6.43064</id>
  1706. <published>2026-06-01T01:59:00Z</published>
  1707. <updated>2026-06-04T19:10:02Z</updated>
  1708. <author>
  1709. <name>John Gruber</name>
  1710. <uri>http://daringfireball.net/</uri>
  1711. </author>
  1712. <content type="html" xml:base="https://daringfireball.net/linked/" xml:lang="en"><![CDATA[
  1713. <p><strong>Location:</strong> The California Theatre, San Jose <br />
  1714. <strong>Showtime:</strong> Tuesday, 9 June 2026, 7pm PT (Doors open 6pm) <br />
  1715. <strong>Special Guest(s):</strong> For sure <br />
  1716. <strong>Price:</strong> $45</p>
  1717.  
  1718. <p>The annual live audience episode of The Talk Show during the week of WWDC. If you can make it, you should come. You’ll even enjoy the prelude, mingling with fellow DF readers and listeners.</p>
  1719.  
  1720. <p>Also: at least one sponsorship slot is still available. If you’ve got a product or service you’d like to see me promote at the start of the show, <a href="https://daringfireball.net/contact/">shoot me an email</a>.</p>
  1721.  
  1722. <div>
  1723. <a  title="Permanent link to ‘The Talk Show Live From WWDC 2026: Tuesday June 9’"  href="https://daringfireball.net/linked/2026/05/31/the-talk-show-live-tickets-2026">&nbsp;★&nbsp;</a>
  1724. </div>
  1725.  
  1726. ]]></content>
  1727.  </entry><entry>
  1728.    
  1729.    <link rel="alternate" type="text/html" href="https://daringfireball.net/2026/05/what_is_a_dickover" />
  1730. <link rel="shorturl" href="http://df4.us/x83" />
  1731. <id>tag:daringfireball.net,2026://1.43059</id>
  1732. <published>2026-05-29T20:58:56Z</published>
  1733. <updated>2026-05-31T22:58:20Z</updated>
  1734. <author>
  1735. <name>John Gruber</name>
  1736. <uri>http://daringfireball.net/</uri>
  1737. </author>
  1738. <summary type="text">dickover — a modal panel, popover, or curtain presented by a website or app, deliberately obscuring its own content to frustrate the user with an unwanted, unnecessary, mandatory interaction; e.g. asking the user to accept “cookies”, subscribe to a newsletter, install the website’s mobile app, agree to terms of service, or anything else that the user couldn’t give two shits about.</summary>
  1739. <content type="html" xml:base="https://daringfireball.net/" xml:lang="en"><![CDATA[
  1740. <p><em><a href="/2026/05/what_is_a_dickover">Please enjoy this article on its own webpage</a>. Trust me.</em></p>
  1741.  
  1742.    ]]></content>
  1743.  <title>★ What Is a Dickover?</title></entry><entry>
  1744.    
  1745.    <link rel="alternate" type="text/html" href="https://daringfireball.net/2026/05/the_fonts_of_the_us_federal_courts" />
  1746. <link rel="shorturl" href="http://df4.us/x7s" />
  1747. <id>tag:daringfireball.net,2026://1.43048</id>
  1748. <published>2026-05-22T20:30:18Z</published>
  1749. <updated>2026-05-25T18:22:13Z</updated>
  1750. <author>
  1751. <name>John Gruber</name>
  1752. <uri>http://daringfireball.net/</uri>
  1753. </author>
  1754. <summary type="text">The Supreme Court’s typographic style has been stunningly consistent for — no pun intended — well over a century.</summary>
  1755. <content type="html" xml:base="https://daringfireball.net/" xml:lang="en"><![CDATA[
  1756. <p>The 13 circuits of <a href="https://en.wikipedia.org/wiki/United_States_courts_of_appeals">the U.S. federal courts of appeals</a> operate with a fair amount of independence, including <a href="https://www.findlaw.com/legalblogs/greedy-associates/5-non-times-new-roman-fonts-courts-use-in-their-opinions/">their typographic choices</a>. I was reminded of this today while reading the <a href="https://daringfireball.net/linked/2026/05/22/ninth-circuit-epic-v-apple">aforelinked</a> decision <a href="https://cdn.ca9.uscourts.gov/datastore/opinions/2025/12/11/25-2935.pdf">from the Ninth Circuit in <em>Epic v. Apple</em></a>, because the Ninth Circuit sets their decisions in <a href="https://daringfireball.net/linked/2025/12/15/a-brief-history-of-timesnewroman">Times New Roman</a> — a font that <a href="https://daringfireball.net/linked/2025/12/10/">came up back in December</a> in the context of the Trump State Department.</p>
  1757.  
  1758. <p>Long argument short, Times New Roman isn’t bad, but it isn’t good. It is the median choice. But <a href="https://www.reddit.com/r/LawSchool/comments/ge4tzq/different_fonts_used_by_us_court_of_appeals/">most of the circuit courts use it</a>: the Third, Fourth, Sixth, Eighth, Ninth, Tenth, and Eleventh. It could be worse: the <a href="https://media.ca1.uscourts.gov/pdf.opinions/14-1043P-01A.pdf">First</a> circuit not only uses Courier New (<a href="https://daringfireball.net/linked/2026/01/14/clintons-letter">the worst version of Courier</a>, so of course it’s the one Microsoft shipped with Windows), but fully justifies their text — contrary to the nature of a monospaced font. (The Fourth circuit only recently switched <a href="https://www.ca4.uscourts.gov/Opinions/Published/131839A.P.pdf">from Courier New</a> <a href="https://www.ca4.uscourts.gov/opinions/251012.P.pdf">to Times New Roman</a> — an upgrade, to be sure, but a disappointingly mediocre one.) It could be better: the <a href="https://ww3.ca2.uscourts.gov/decisions/OPN/24-341_opn.pdf">Second</a> and <a href="https://media.ca7.uscourts.gov/cgi-bin/OpinionsWeb/processWebInputExternal.pl?Submit=Display&amp;Path=Y2026/D05-20/C:24-2015:J:Hamilton:aut:T:fnOp:N:3544786:S:0">Seventh</a> use Palatino. (Note how much better that Seventh Circuit decision looks than the Second’s, with its wider margins creating a narrower column of text.)</p>
  1759.  
  1760. <p>But it can be <em>much</em> better. The Fifth Circuit was long typographically superior to its peers, using <a href="https://en.wikipedia.org/wiki/Century_type_family">Century Schoolbook</a> — a highly legible font with great tradition and the right vibe. But in 2020, the Fifth Circuit upgraded, switching to <a href="https://typographyforlawyers.com/equity.html">Equity</a>, Matthew Butterick’s excellent type family (which, of course, is used throughout Butterick’s own web book, <a href="https://typographyforlawyers.com/"><em>Typography for Lawyers</em></a>). Here’s a <a href="https://x.com/E_A_Young/status/1285354790176935936">before and after tweet</a> noting the change. The <a href="https://www.ca5.uscourts.gov/opinions/pub/25/25-11006-CV1.pdf">results</a> are typographically sublime (including improved margins).</p>
  1761.  
  1762. <p>The gold standard is the U.S. Supreme Court, which uses Century Schoolbook. Yes, I just praised the Fifth Circuit’s change from Century Schoolbook to Equity as an upgrade, but tradition and consistency have their place. The Supreme Court’s typographic style has been stunningly consistent for — no pun intended — well over a century. (If only that were true of their recent decisions. <em>Rimshot.</em>) Here is last month’s <a href="https://www.supremecourt.gov/opinions/25pdf/24-109_new_jifl.pdf"><em>Louisiana v. Callais</em> decision</a> — the gerrymandering / redistricting case. Here is <a href="https://tile.loc.gov/storage-services/service/ll/usrep/usrep347/usrep347483/usrep347483.pdf">1954’s <em>Brown v. Board of Education</em></a>. I’d give the nod to the older one, which made better use of proper small caps, but the overall consistency is obvious.</p>
  1763.  
  1764. <p>Here is <a href="https://www.supremecourt.gov/filingandrules/2026RulesoftheCourt_WEB.pdf">the 2026 edition of the Rules of the Supreme Court</a>. Not only does the Court use Century Schoolbook for its own decisions, it requires submissions to the Court to use the same (p. 44):</p>
  1765.  
  1766. <blockquote>
  1767.  <p>The text of every booklet-format document, including any appendix
  1768. thereto, shall be typeset in a Century family (e. g., Century
  1769. Expanded, New Century Schoolbook, or Century Schoolbook) 12-point
  1770. type with 2-point or more leading between lines. Quotations in
  1771. excess of 50 words shall be indented. The typeface of footnotes
  1772. shall be 10-point type with 2-point or more leading between lines.
  1773. The text of the document must appear on both sides of the page.</p>
  1774.  
  1775. <p>Every booklet-format document shall be produced on paper that is
  1776. opaque, unglazed, and not less than 60 pounds in weight, and
  1777. shall have margins of at least three-fourths of an inch on all
  1778. sides. The text field, including footnotes, may not exceed 4⅛
  1779. by 7⅛ inches.</p>
  1780. </blockquote>
  1781.  
  1782. <p>Why the extra one-eighths of an inch instead of just 4 × 7? I don’t know. But 4⅛ × 7⅛ is exactly the size of the text field in the court’s own decisions.</p>
  1783.  
  1784. <p>Now compare the current 2026 rulebook to <a href="https://www.supremecourt.gov/pdfs/rules/rules_1910.pdf">this edition printed in 1910</a> (with rules adopted in 1884). The consistency is striking — but, once again, the older version makes better use of small caps and just has a bit more vim and vigor to it. <a href="https://daringfireball.net/misc/2026/05/scotus-1910-rules-p-44.jpeg">Just look at page 44</a>, for example. It’s perfect. The current Court’s document formatters should aspire only to more closely ape the confidence and sturdiness of this older one. A century from now, U.S. Supreme Court decisions should look as similar to today’s as today’s do to those from a century ago.</p>
  1785.  
  1786. <hr />
  1787.  
  1788. <p>The various circuit courts using lesser typefaces, looser margins, and lazier formatting should follow the Fifth’s lead and get their shit together. Tuck your shirt in, comb your hair, straighten your tie, and pop a mint in your mouth. If you’re a United States federal court, your typographic style should reflect that.</p>
  1789.  
  1790. <p>Back in 2020, <a href="https://matthewbutterick.com/chron/choose-wisely-2020-edition.html">Butterick took a well-deserved victory lap</a> when the Fifth Circuit adopted Equity.<sup id="fnr1-2026-05-22-f"><a href="#fn1-2026-05-22-f">1</a></sup> He quoted Fifth Circuit Judge <a href="https://x.com/justicewillett">Don Willett</a>, a typography fan who spearheaded the restyling project, on its rationale. Willett wrote:</p>
  1791.  
  1792. <blockquote>
  1793.  <p>[Why] did the circuit devote finite judicial energy to swapping
  1794. typefaces and widening margins? Simple answer: Our job is not
  1795. just to present clear opinions, but to present our opinions
  1796. clearly. Getting the law right is, of course, our tip-top
  1797. priority. Nothing matters more. ... But good enough is never good
  1798. enough. Our work is consequential, impacting the lives and
  1799. livelihoods of real people walloped by real problems in the real
  1800. world. The stakes are high, and we must present our best opinion,
  1801. not merely a passable one. And that presentation begins before
  1802. the first word is ever read.</p>
  1803. </blockquote>
  1804.  
  1805. <div class="footnotes">
  1806. <hr />
  1807. <ol>
  1808. <li id="fn1-2026-05-22-f">
  1809. <p>In the very same post, Butterick sings the praises of the Apple Extended Keyboard II, and notes that he has several spares in reserve. I do keenly intend to take Butterick up on <a href="https://practicaltypography.com/effluents-influence-affluence.html#:~:text=Musso%20%26%20Frank">his standing offer</a> to dine when next I’m in Los Angeles, but I worry that if we meet, we’ll trigger some sort of calamitous singularity of aligned taste.&nbsp;<a href="#fnr1-2026-05-22-f"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1810. </li>
  1811. </ol>
  1812. </div>
  1813.  
  1814.    ]]></content>
  1815.  <title>★ The Fonts of the U.S. Federal Courts</title></entry><entry>
  1816.    
  1817.    <link rel="alternate" type="text/html" href="https://daringfireball.net/2026/05/ai_is_technology_not_a_product" />
  1818. <link rel="shorturl" href="http://df4.us/x72" />
  1819. <id>tag:daringfireball.net,2026://1.43022</id>
  1820. <published>2026-05-16T20:32:51Z</published>
  1821. <updated>2026-05-18T16:48:28Z</updated>
  1822. <author>
  1823. <name>John Gruber</name>
  1824. <uri>http://daringfireball.net/</uri>
  1825. </author>
  1826. <summary type="text">It’s not even a feature. It’s just technology.</summary>
  1827. <content type="html" xml:base="https://daringfireball.net/" xml:lang="en"><![CDATA[
  1828. <p>Steven Levy, writing for Wired last month after Apple’s CEO transition was announced, under the provocative headline “<a href="https://www.wired.com/story/apples-next-ceo-needs-to-launch-a-killer-ai-product/">Apple’s Next CEO Needs to Launch a Killer AI Product</a>” (<a href="https://apple.news/AdCC7y43rTQq6SZH2bDmqxA">News+ link</a> to get around Wired’s miserly paywall):</p>
  1829.  
  1830. <blockquote>
  1831.  <p>Much more recently, <a href="https://www.wired.com/story/apple-50-year-anniversary-artificial-intelligence-iphone/">I quizzed Ternus</a> and global marketing
  1832. head Greg Joswiak about Apple’s future, specifically its plans to
  1833. get ahead of the AI transformation. Ternus acknowledged that AI is
  1834. “an immense kind of inflection point,” but couched it as one of
  1835. many leaps that Apple has navigated. Each hit product — the Apple
  1836. II, the Mac, iTunes, the iPod, the iPhone, iPad — piggybacked on
  1837. a previous product. “We never think about shipping a technology,”
  1838. he said. “We want to ship amazing products, features, and
  1839. experiences, and we don’t want our customers to think about what
  1840. [underlying] technology makes it possible. That’s the way we think
  1841. about AI.”</p>
  1842.  
  1843. <p>That’s fine, but I look back to the mid-2000s when everybody was
  1844. waiting for Apple to come out with a phone. When Jobs finally
  1845. delivered in January 2007, the product defined the mobile era.
  1846. It’s a big ask for Ternus to do something similar for the AI age — but it’s an opportunity that must be seized. AI threatens to
  1847. disrupt the entire iPhone ecosystem. By the end of this decade,
  1848. it’s unlikely that people will swipe on their phones to tap on
  1849. Uber or Lyft. They will just tell their always-on AI agent to get
  1850. them home. Or that agent will have already figured out where they
  1851. need to go, and the car will be waiting without the friction of a
  1852. request. “There’s an app for that,” may be replaced by “Let the
  1853. agent do that.”</p>
  1854. </blockquote>
  1855.  
  1856. <p>I’m a huge longtime Steven Levy fan, but this is nonsense. It’s hard to read this and not worry that he too has lost his mind to the AI snake-oil hypesters. What Ternus told him is exactly right. The Apple way is never to ship a technology. The iPod wasn’t about MP3 files. It wasn’t about <a href="https://www.wired.com/2006/10/straight-dope-on-the-ipods-birth/">1.8-inch hard drives</a>. It was about music. The iPhone did define the mobile era (which we’re still very much in), but Apple doesn’t need to capitalize on every single market the mobile era opened up. Social media is a defining component of the mobile era. It comprises the entirety of Meta’s value and a sizable slice of Google’s (via YouTube). Apple doesn’t have a social network business. It’s fine — because the way people consume and create social media is using their phones.</p>
  1857.  
  1858. <p>Does AI “threaten to disrupt the entire iPhone ecosystem”? It’s possible, but it doesn’t seem nearly as likely to me as Levy asserts. <em>Changing</em> the iPhone ecosystem? Sure — that’s already true. <em>Obviating</em> the iPhone ecosystem? I don’t see it. Levy’s argument reminds me of the hype around “the cloud” when that first became a term. It’s so meaningless when used broadly (e.g. “<em>Everything will soon be in the cloud</em>”) that it could mean anything. It’s step #2 in the <a href="https://southpark.fandom.com/wiki/Underpants_Gnomes">gnomes-stealing-underpants</a> master plan.</p>
  1859.  
  1860. <p>The idea that AI agents “will have already figured out where [we] need to go, and the car will be waiting without the friction of a request” strikes me as pure fever dream high-on-the-hype fantasy. I’m just going to step outside a restaurant when I’m done eating a meal and a ride-share is going to be there, waiting for me, without my having hailed it? Every time? And I’m going to find this pleasing, not creepy? And ride-share drivers are going to respond to all these requests, because the requests will never be wrong? And this is going to happen, somehow, without my carrying a phone with me? And this is going to happen in the next four years? I don’t think I’d want this even if it were plausible, but it doesn’t sound plausible.</p>
  1861.  
  1862. <p>Actual products have to be real. Actual experiences have to rely on actual products. How exactly in Levy’s end-of-this-decade scenario will we tell our “always-on AI agent” to get us home? What microphone is listening to the command? What speaker is telling us the request was understood and acted upon? What screen do we look at to see how far away the hailed car is? I’d bet a pretty large sum of money that in 2030, when someone hails a ride-share vehicle to take them home, the most common product they’ll use to do that will be their phone. Whether they’re doing it via a verbal command issued to an “always-on AI agent” or good old tapping and swiping, it’ll be a phone.</p>
  1863.  
  1864. <p>If you think that people will buy smaller devices to replace their phones, and use those to talk to “always-on AI agents” instead, you have to answer some questions. What company is the best in the world at making smaller-than-phone personal computing devices? What device will people use as their camera? What device will people use as their screen, for watching videos, playing games, texting, and (one hopes) reading? My answers to those three questions: Apple, phone, phone. Why would smaller devices — you know, like watches, earbuds, and, say, glasses — work independently rather than pair with the phone that you’re almost certainly still going to be carrying with you?</p>
  1865.  
  1866. <p>Only a fool would argue that Apple can stand on the sidelines and ignore AI. It’s very different from, say, social media that way. Social media doesn’t pervade everything in technology. You can ignore social media as a user. (And you’re probably more productive, and happier, if you do.) A company can eschew social media as a business. AI, on the other hand, is pervasive. It can’t be ignored. But it’s just technology.</p>
  1867.  
  1868. <p>Wireless networking is pervasive too. But Apple doesn’t have “a killer wireless networking product”.<sup id="fnr1-2026-05-16"><a href="#fn1-2026-05-16">1</a></sup> Wireless networking simply pervades everything Apple makes. I’m hard pressed to think of a single product Apple makes that doesn’t use some combination of Wi-Fi, cellular, Bluetooth, and proprietary wireless protocols. There was a time, not <em>too</em> long ago, when Apple didn’t make a single product with wireless connectivity. Now it’s pervasive in all their devices. That’s more what AI is going to be like. There’s not going to be one “killer AI device”. Everything is going to be an AI device, to some extent, just like how everything today is a wireless connectivity device, to some extent.</p>
  1869.  
  1870. <p><strong>Postscript:</strong> “<a href="https://daringfireball.net/linked/2026/05/18/existing-stakeholders-have-a-say-in-the-future">Existing Stakeholders Have a Say in the Future</a>”.</p>
  1871.  
  1872. <div class="footnotes">
  1873. <hr />
  1874. <ol>
  1875. <li id="fn1-2026-05-16">
  1876. <p>AirPort qualified, arguably. But Apple walked away from it, alas.&nbsp;<a href="#fnr1-2026-05-16"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1877. </li>
  1878. </ol>
  1879. </div>
  1880.  
  1881.    ]]></content>
  1882.  <title>★ AI Is Technology, Not a Product</title></entry><entry>
  1883.    
  1884.    <link rel="alternate" type="text/html" href="https://daringfireball.net/2026/05/nextpad" />
  1885. <link rel="shorturl" href="http://df4.us/x6j" />
  1886. <id>tag:daringfireball.net,2026://1.43003</id>
  1887. <published>2026-05-13T02:22:16Z</published>
  1888. <updated>2026-06-04T23:55:35Z</updated>
  1889. <author>
  1890. <name>John Gruber</name>
  1891. <uri>http://daringfireball.net/</uri>
  1892. </author>
  1893. <summary type="text">Nextpad++ feels like a fever dream. Like what Mac apps would be if the Nazis had won WWII.</summary>
  1894. <content type="html" xml:base="https://daringfireball.net/" xml:lang="en"><![CDATA[
  1895. <p>Windows Notepad is, more or less, the Windows peer to MacOS’s TextEdit — the built-in system text editor. For years, it was really basic — so much more basic than TextEdit that it engendered no affection. You don’t see paeans to Notepad <a href="https://daringfireball.net/linked/2026/01/26/chayka-textedit">in The New Yorker</a>. Recently though, Microsoft has started beefing it up, culminating last year <a href="https://daringfireball.net/linked/2025/06/06/markdown-support-in-windows-notepad">when they added fucking Markdown support</a>. Which still blows my mind.</p>
  1896.  
  1897. <p><a href="https://notepad-plus-plus.org/">Notepad++</a> is a longstanding open source (GPL) Windows text editor <a href="https://notepad-plus-plus.org/author/">by Don Ho</a>, which <a href="https://notepad-plus-plus.org/">debuted back in 2003</a>. Just adding “++” to the name might be misleading. The name implies that it’s like Microsoft’s Notepad <a href="https://www.waltdisney.org/blog/walts-own-words-plussing-disneyland">plus</a> a little more. But Notepad++ is in fact a wholly independent programming text editor, with a rich plugin library. It doesn’t resemble Microsoft’s Notepad much at all anymore. It’s over two decades old but remains quite popular. To some extent Notepad++ is sorta kinda the Windows peer to <a href="https://www.barebones.com/products/bbedit/">BBEdit</a>.</p>
  1898.  
  1899. <p><a href="https://nextpad.org/author/">Nextpad++</a> is something new, <a href="https://nextpad.org/author/">from Andrey Letov</a>. It’s a Mac port of the Notepad++ GPL code. It launched a few weeks ago under the name “Notepad++ for Mac”, but Letov had <a href="https://notepad-plus-plus.org/news/npp-trademark-infringement/">no right or permission to the name</a>. That dispute has been settled, and Letov has renamed this project Nextpad++. The website’s <a href="https://nextpad.org/about/">About page</a> has entire sections for “How Nextpad++ for Mac Was Built” and “Technology Stack”, and neither of those mentions AI, but this thing <em>has</em> to have been built using AI vibe-coding agents. That same About page also says the project only started on March 10, and the 1.0 version (under the defunct “Notepad++ for Mac” name) shipped just a few weeks after that. Something of the scope of this port couldn’t happen at that pace without AI. <strong>Update:</strong> On <a href="https://nextpad.org/author/">the Author page</a>, not the About page, it states, “multi-agent AI development workflows are what make a one-person project at this scale practical.” <em>Possible</em>, sure, but I wouldn’t call this <em>practical</em>.</p>
  1900.  
  1901. <p>Nextpad++ feels like a fever dream. Like what Mac apps would be if the Nazis had won WWII. Look, there are all sorts of foreign apps on the Mac. <a href="https://daringfireball.net/2018/12/electron_and_the_decline_of_native_apps">Electron</a> apps. Apps ported with <a href="https://www.winehq.org/">Wine</a>. Web apps running in browser tabs or <a href="https://support.apple.com/guide/safari/add-to-dock-ibrw9e991864/mac">saved to the Dock</a>. The <a href="https://shapeof.com/archives/2026/4/tolaria_ai_and_rust.html">curious new generation</a> of lean-and-mean apps that are, in a technical sense, “native”, but are decidedly not Mac-assed apps, like <a href="https://zed.dev/">Zed</a> and <a href="https://tolaria.md/">Tolaria</a>. All those types of apps feel alien on MacOS. Like different species. They are apps for the Mac but aren’t Mac apps. The Mac, however, is welcoming to them all, <a href="https://daringfireball.net/2026/04/we_dont_serve_their_kind_here">like the Mos Eisley cantina</a>. We do serve their kind here. Nextpad++ isn’t like that. It doesn’t feel like an alien. It feels like Vincent D’Onofrio’s alien-bug-in-human-skin character from <em>Men in Black</em>.</p>
  1902.  
  1903. <p>Letov’s website describes Nextpad++ as “A real Mac app, not a Wine wrapper: Objective-C++ on top of Scintilla and Cocoa, shipped as a Universal Binary for Apple Silicon (M1–M5) and Intel Macs.” Ostensibly that’s a good thing. The download is only 14 MB. But Nextpad++ looks and feels like something that should not exist. The promotional screenshots on the app’s own website show it <a href="https://daringfireball.net/misc/2026/05/nextpad++.png">with 50 inscrutable toolbar buttons</a>. It closes document tabs on mousedown, not mouseup. Its default font is 10-point Courier New. <a href="https://daringfireball.net/misc/2026/05/nextpad-editing-contextmenu.png">This</a> is a real dialog box. It offers <a href="https://daringfireball.net/misc/2026/05/nextpad-antialiasing.png">four settings for font antialiasing</a> — “Default”, “None”, “Antialiased”, and “LCD Optimized” — but the default is not “Default”. No human being would port a complex Windows app like Notepad++ to the Mac like this.</p>
  1904.  
  1905. <p>I’m not anti-AI. I’m very much intrigued by the whole incipient vibe-coding phenomenon. But this app feels <em>unholy</em>.</p>
  1906.  
  1907.    ]]></content>
  1908.  <title>★ Nextpad++</title></entry><entry>
  1909.    
  1910.    <link rel="alternate" type="text/html" href="https://daringfireball.net/2026/05/software_as_the_product_of_obsession_times_voice" />
  1911. <link rel="shorturl" href="http://df4.us/x5v" />
  1912. <id>tag:daringfireball.net,2026://1.42979</id>
  1913. <published>2026-05-05T21:01:05Z</published>
  1914. <updated>2026-05-05T21:01:06Z</updated>
  1915. <author>
  1916. <name>John Gruber</name>
  1917. <uri>http://daringfireball.net/</uri>
  1918. </author>
  1919. <summary type="text">You might think it counterintuitive that a movement obsessed with software would be spearheading a severe decline in the design quality of software, but in Patel’s definition, there’s no concept of software as art, as a practice, as a craft. Software brain is purely an obsession with software as a medium in and of itself. A means with no consideration for the end.</summary>
  1920. <content type="html" xml:base="https://daringfireball.net/" xml:lang="en"><![CDATA[
  1921. <p>Back in 2009, Merlin Mann and I jointly gave a talk at SxSW titled “<a href="https://daringfireball.net/2009/03/obsession_times_voice">Obsession Times Voice</a>”. Regarding how it turned out, <a href="https://daringfireball.net/2009/03/obsession_times_voice">I wrote</a>:</p>
  1922.  
  1923. <blockquote>
  1924.  <p>My muse for the session was this quote from Walt Disney: <em>“We
  1925. don’t make movies to make money; we make money to make more
  1926. movies.”</em> To me, that’s it. That’s the thing.</p>
  1927. </blockquote>
  1928.  
  1929. <p>Merlin and I were talking about independent writers and podcasters, because that’s what we were (and remain), but the concept applies just as perfectly to independent developers. This came to my mind after reading (<a href="https://daringfireball.net/linked/2026/05/05/pedometer-plus-plus-8">and linking to</a>) David Smith’s description of the new Pedometer++ today. Not just what it does, but why he spent <a href="https://david-smith.org/blog/2026/04/29/maps-on-watchos/">six years making it</a>. That’s the sort of productive obsession that fascinates me.</p>
  1930.  
  1931. <p>Ice water is always refreshing, but it tastes better when you’re on a road trip to hell. It feels like the world of software is bifurcating quality-wise. This <a href="https://daringfireball.net/linked/2026/05/04/photoshop-modern-user-interface">whole</a> <a href="https://daringfireball.net/linked/2026/05/04/adobe-modern-webpages">thing</a> about <a href="https://mjtsai.com/blog/2026/04/30/photoshops-modern-spectrum-user-interface/">Adobe’s new craptacular “modern” UI language</a> (a.k.a. “<a href="https://spectrum.adobe.com/">Spectrum</a>”) exemplifies one side of that bifurcation — the bad-and-getting-worse side. Software that is the product not just of an ignorance of <a href="https://asktog.com/atc/principles-of-interaction-design/">long-established principles of interaction design</a>, but of a <a href="https://daringfireball.net/2025/12/bad_dye_job#:~:text=the%20key%20window">willful disdain for those principles</a>. What Adobe is now shipping is just inexplicably bad UI, ignoring literally decades of great work and long-mastered concepts — a lot of which work was <a href="https://daringfireball.net/linked/2026/05/04/adobe-modern-webpages">pioneered by Adobe itself</a>!</p>
  1932.  
  1933. <p>The <a href="https://daringfireball.net/linked/2026/04/13/tahoe-reduce-transparency">whole</a> <a href="https://daringfireball.net/2026/03/what_to_do_about_those_menu_item_icons_in_macos_26_tahoe">thing</a> with <a href="https://daringfireball.net/2025/12/bad_dye_job">MacOS 26 Tahoe</a> is similar. To be clear, the UI crimes in Tahoe are deeply worrisome, but they are nowhere near as severe as those in Adobe’s Spectrum. But the problems with Tahoe are steps down the same fork in the road that Adobe took years ago. Spectrum is where Tahoe suggests that MacOS was headed under Alan Dye’s leadership: cross-platform sameness for the sake of sameness, with a complete disregard for longstanding platform nuances and idioms. In Spectrum’s case those platforms are MacOS and Windows and <a href="https://helpx.adobe.com/account/individual/subscriptions-and-plans/plan-types-and-eligibility/cc-app-web-mobile-access.html">the web</a>. In Tahoe’s case it’s MacOS and iOS.<sup id="fnr1-2026-05-05"><a href="#fn1-2026-05-05">1</a></sup></p>
  1934.  
  1935. <p>The other side of the software fork is not deserted. It’s just populated, more than ever, by the products of small independent developers who obsess, first and foremost, over quality and artistic vision. Remarkable new software gems exhibiting spectacular UI design <a href="https://www.currentreader.app/">appear</a> <a href="https://daringfireball.net/linked/2026/05/04/chess-peace">all</a> the <a href="https://daringfireball.net/linked/2026/04/15/so-close-to-getting-it">time</a>. They’re just not coming from the biggest companies, the ones whose apps, <a href="https://daringfireball.net/linked/2026/03/28/netflix-wrecked-their-tvos-video-player">alas</a>, dominate not just our desktops and pockets but our entire culture today.<sup id="fnr2-2026-05-05"><a href="#fn2-2026-05-05">2</a></sup></p>
  1936.  
  1937. <p>There’s always been software with poorly designed user interfaces. Much of it has been successful financially, sometimes spectacularly so. I’d argue, in all seriousness, that that’s the story of Microsoft in a nutshell. What’s new today is poorly designed software from developers <a href="https://daringfireball.net/linked/2026/04/16/miller-netflix-tvos">from whom we expect better</a>. In the old days there were people who would argue that prioritizing good user interface design was a waste of time — like spending hours decorating cupcakes destined for kindergarteners who are simply going to mash them into their mouths. (Again: cf. Microsoft’s undeniable market success.) What’s new today is people holding up objectively bad interaction design and proclaiming it to be good, and the product of teams that purportedly prioritize “design”, when it’s clear they have no idea what they’re talking about. It’s one thing to make something poorly designed and shrug on the grounds that it doesn’t matter. It’s another thing to make something poorly designed and hold it up as good design.</p>
  1938.  
  1939. <p>We are justified to expect nothing short of <a href="https://www.folklore.org/How_to_Hire_Insanely_Great_Employees.html">insane greatness</a> from Apple, and solidly good design from Adobe. In principle, all software ought to have well-designed user interfaces. That’s never going to be the case. But software for designers — Adobe’s <em>raison d’être</em> — absolutely demands to be well-designed itself, like how <a href="https://daringfireball.net/linked/2009/03/31/zinsser">a book on writing</a> must itself <a href="https://daringfireball.net/linked/2009/03/23/strunk-and-white">be well-written</a>.</p>
  1940.  
  1941. <p>Perhaps I was wrong, though, to describe Adobe’s new UI as inexplicable. It’s just indefensible. The explanation for so much software going so rotten from a UI-design perspective is, the more I think about it, related to <a href="https://www.theverge.com/podcast/917029/software-brain-ai-backlash-databases-automation">Nilay Patel’s “Software Brain”</a> theory, which I’ve commented on both <a href="https://daringfireball.net/linked/2026/04/23/patel-software-brain">directly</a> and <a href="https://daringfireball.net/2026/04/we_dont_serve_their_kind_here">indirectly</a>. Here’s Patel’s definition of “software brain”:</p>
  1942.  
  1943. <blockquote>
  1944.  <p>The simplest definition I’ve come up with is that it’s when you
  1945. see the whole world as a series of databases that can be
  1946. controlled with the structured language of software code. Like I
  1947. said, this is a powerful way of seeing things. So much of our
  1948. lives run through databases, and a bunch of important companies
  1949. have been built around maintaining those databases and providing
  1950. access to them.</p>
  1951.  
  1952. <p>Zillow is a database of houses. Uber is a database of cars and
  1953. riders. YouTube is a database of videos. The Verge’s website is a
  1954. database of stories. You can go on and on and on. Once you start
  1955. seeing the world as a bunch of databases, it’s a small jump to
  1956. feeling like you can control everything if you can just control
  1957. the data.</p>
  1958.  
  1959. <p>But that doesn’t always work.</p>
  1960. </blockquote>
  1961.  
  1962. <p>You might think it counterintuitive that a movement obsessed with software would be spearheading a severe decline in the design quality of software, but in Patel’s definition, there’s no concept of software as art, as a practice, as a craft. Software brain is purely an obsession with software as a medium in and of itself. A means with no consideration for the end.</p>
  1963.  
  1964. <p>Framed in Walt Disney’s adage, software brain makes software only to make more money. The idea of making money in order to make more software — to afford the time and talent to <em>craft</em> it — does not compute. Framed in the metaphor that Steve Jobs used to <a href="https://www.youtube.com/watch?v=OesY-denV8k">close his introduction of the original iPad</a>, and returned to again <a href="https://www.youtube.com/watch?v=sUCpuaqlISQ">to close his final keynote at WWDC 2011</a>, software brain is nowhere near the intersection of technology and the liberal arts. Software brain is so far down Technology Street that it’s no longer in the same zip code as Liberal Arts Avenue. Another way, perhaps, to define <em>software brain</em> is that it’s the utter rejection of Jobs’s maxim that “technology is not enough”. With software brain, technology is all there is.</p>
  1965.  
  1966. <div class="footnotes">
  1967. <hr />
  1968. <ol>
  1969.  
  1970. <li id="fn1-2026-05-05">
  1971. <p>I don’t want to belabor the similarities between Adobe’s Spectrum UI system and Apple’s Liquid Glass, because there are significant differences. Foremost, <a href="https://unsung.aresluna.org/photoshops-challenges-with-focus-pt-2/">what’s wrong with Spectrum</a> is wrong everywhere. Photoshop with Adobe’s new “modern” UI is, I suspect, just as bad a Windows app as it is a Mac app. Whereas the usability problems with Liquid Glass are lopsided platform-wise. It’s a litany of disasters on MacOS 26 Tahoe, but actually pretty good on Apple’s other version 26 OSes, especially iOS. There are aspects of Liquid Glass on iOS 26 that some people don’t like, but they’re literally skin-deep. Cosmetic details. Functionally, iOS 26 is pretty strong, and Apple made some very nice changes regarding the placement of things like search fields to improve consistency system-wide. I still have iOS 18 running on my year-old iPhone 16 Pro, and there are very few things I prefer in iOS 18 versus iOS 26. Whereas I’d be sick if I had to work in MacOS 26 Tahoe every day.</p>
  1972.  
  1973. <p>That’s my point here. iOS 26 doesn’t suffer in any way — not even one teensy little single way — from MacOS UI idioms being inappropriately applied to the iPhone. On the iPad, maybe there’s a little of that, like, say, the weird way iPadOS 26 uses Mac-style red / yellow / green window control buttons but makes them too small to use, so before you use them, <a href="https://sixcolors.com/post/2025/09/ipados-26-review-a-computer/">you need a gesture to embiggen them temporarily first</a>. But the implementation of “Liquid Glass” on MacOS Tahoe is just riddled with iOS-isms that aren’t appropriate on MacOS. So many decades-old Mac UI nuances and idioms were just ignored. They weren’t changed, they weren’t updated, they were just ignored. You either see that this is true or you don’t, and if you don’t see it, you shouldn’t be designing the Mac user interface.&nbsp;<a href="#fnr1-2026-05-05"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  1974. </li>
  1975.  
  1976.  
  1977. <li id="fn2-2026-05-05">
  1978. <p>Consider the age of television. Television is the broadcast of motion pictures with sound. Cinema is an artform. But at the peak of television’s hegemony over western culture and mass media, the artistic quality of almost everything on TV was terrible. It was slop. It wallowed in its own sloppiness. This, despite the fact that cinematic artists had largely mastered the artform in the decades preceding TV. TV became popular in the 1950s and culturally dominant in the 1960s. But <em>Citizen Kane</em> came out in 1941. The network executives with “TV brain” in the second half of the 20th century didn’t even consider TV as a medium for art. They just cared that it was watched. It was judged only by ratings and ad revenue, not artistic merit. That’s what’s happening with software right now. But remember too, that as dreadful television programming rocketed to stratospheric popularity in the 1970s, that same decade saw <a href="https://www.imdb.com/list/ls000335086/">a remarkable explosion in innovative filmmaking</a> in movie theaters. Keep the faith.&nbsp;<a href="#fnr2-2026-05-05"  class="footnoteBackLink"  title="Jump back to footnote 2 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  1979. </li>
  1980.  
  1981. </ol>
  1982. </div>
  1983.  
  1984.    ]]></content>
  1985.  <title>★ Software as the Product of Obsession Times Voice</title></entry></feed><!-- THE END -->
  1986.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//daringfireball.net/index.xml

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda