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


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


  1. <?xml version="1.0" encoding="utf-8"?>
  2. <feed xmlns="">
  3. <title>Daring Fireball</title>
  4. <subtitle>By John Gruber</subtitle>
  5. <link rel="alternate" type="text/html" href="" />
  6. <link rel="self" type="application/atom+xml" href="" />
  7. <id></id>
  10. <updated>2020-03-29T22:57:21Z</updated><rights>Copyright © 2020, John Gruber</rights><entry>
  11. <title>‘Lego Thunderball’</title>
  12. <link rel="alternate" type="text/html" href="" />
  13. <link rel="shorturl" type="text/html" href="" />
  14. <link rel="related" type="text/html" href="" />
  15. <id>,2020:/linked//6.36631</id>
  16. <published>2020-03-29T20:22:50Z</published>
  17. <updated>2020-03-29T20:30:33Z</updated>
  18. <author>
  19. <name>John Gruber</name>
  20. <uri></uri>
  21. </author>
  22. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  23. <p>Jon Opstad:</p>
  25. <blockquote>
  26.  <p>Been isolating at home with my wife &amp; kids for a week now. For my
  27. contribution to home schooling my kids (aged 6 &amp; 4). I chose the
  28. most obvious thing — creating a shot-by-shot recreation of the
  29. jet pack sequence from “Thunderball” out of LEGO.</p>
  30. </blockquote>
  32. <p>Astonishingly well-done. Pure joy.</p>
  34. <div>
  35. <a  title="Permanent link to ‘‘Lego Thunderball’’"  href="">&nbsp;★&nbsp;</a>
  36. </div>
  38. ]]></content>
  39.  </entry><entry>
  40. <title>Friday’s New York Times Front Page Visualization of U.S. Unemployment Claims (PDF)</title>
  41. <link rel="alternate" type="text/html" href="" />
  42. <link rel="shorturl" type="text/html" href="" />
  43. <link rel="related" type="text/html" href="" />
  44. <id>,2020:/linked//6.36630</id>
  45. <published>2020-03-29T20:13:00Z</published>
  46. <updated>2020-03-29T22:57:21Z</updated>
  47. <author>
  48. <name>John Gruber</name>
  49. <uri></uri>
  50. </author>
  51. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  52. <p>Brilliant data visualization of a sobering disaster. Like most of you, I’m sure, I seldom read a paper edition of a newspaper anymore. But this design is a good reminder of how expansive the space is on a broadsheet front page. This graphic both makes great use of that space <em>and</em> plays against the reader’s decades-old assumptions about how the front page of The Times is laid out. It’s an unprecedented, shocking design to present unprecedented, shocking data.</p>
  54. <p>(I <a href="">tweeted this</a> yesterday and a few people asked how they could obtain hard copies — e.g. for teaching data visualization. <a href="">The Times sells reprints of each day’s front page</a>.)</p>
  56. <div>
  57. <a  title="Permanent link to ‘Friday’s New York Times Front Page Visualization of U.S. Unemployment Claims (PDF)’"  href="">&nbsp;★&nbsp;</a>
  58. </div>
  60. ]]></content>
  61.  </entry><entry>
  62. <title>NextDraft</title>
  63. <link rel="alternate" type="text/html" href="" />
  64. <link rel="shorturl" type="text/html" href="" />
  65. <link rel="related" type="text/html" href="" />
  66. <id>,2020:/linked//6.36629</id>
  67. <published>2020-03-29T01:09:34Z</published>
  68. <updated>2020-03-29T01:10:38Z</updated>
  69. <author>
  70. <name>John Gruber</name>
  71. <uri></uri>
  72. </author>
  73. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  74. <p>My thanks to Dave Pell for sponsoring this week at DF to promote NextDraft, his “quick, entertaining look at the day’s biggest and best stories, from the top of the news to the very bottom”. Pell is a news junkie’s news junkie, and a kindred spirit of mine. NextDraft is his Daring Fireball.</p>
  76. <p>In normal times, NextDraft is a once-per-weekday newsletter, delivered either by email or <a href="">a very nice iOS app</a>. These are not normal times, and as the coronavirus crisis continues, NextDraft has gone to a 7-days-a-week schedule.</p>
  78. <p>The once-a-day pace keeps you up to date on the news, but keeps you from being pestered by frequent emails or notifications. NextDraft is not about breaking news — it’s just a carefully curated and cleverly written daily update. You like email? Sign up for the newsletter. Hate email? <a href="">Get the app</a>.</p>
  80. <p>Here’s the kicker: NextDraft is free of charge. There is no catch. I read NextDraft every day; you should too.</p>
  82. <div>
  83. <a  title="Permanent link to ‘NextDraft’"  href="">&nbsp;★&nbsp;</a>
  84. </div>
  86. ]]></content>
  87.  </entry><entry>
  89.    <link rel="alternate" type="text/html" href="" />
  90. <link rel="shorturl" href="" />
  91. <id>,2020://1.36627</id>
  92. <published>2020-03-28T23:15:00Z</published>
  93. <updated>2020-03-29T17:48:54Z</updated>
  94. <author>
  95. <name>John Gruber</name>
  96. <uri></uri>
  97. </author>
  98. <summary type="text">Some pointers regarding cursors.</summary>
  99. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  100. <p><em>Cursor</em> is an overloaded term. There are two discrete elements of modern computing that we loosely refer to as “cursors”:</p>
  102. <ul>
  103. <li>The icon that moves around on the screen that you control with your mouse or trackpad.</li>
  104. <li>The vertical bar that blinks in a text editing field to indicate where typed characters will appear.</li>
  105. </ul>
  107. <p>For clarity, it’s best not to refer to either of these things as <em>cursors</em>. Instead:</p>
  109. <ul>
  110. <li>Mouse/trackpad pointer.</li>
  111. <li>Insertion point.</li>
  112. </ul>
  114. <p>This terminology has been <a href="">slightly confusing</a> over the last week, since Apple’s surprise announcement of pointer support in iPadOS 13.4. In their marketing materials, Apple is calling pointers “cursors”. E.g, <a href="">on the webpage for the refreshed iPad Pros</a>:</p>
  116. <blockquote>
  117.  <p>The click-anywhere trackpad opens up a whole new way to work in
  118. iPadOS. It allows control of the new cursor in iPadOS, which is
  119. perfect for tasks like editing a spreadsheet, selecting text, or
  120. simply doing everything right from the trackpad.</p>
  121. </blockquote>
  123. <p>From the <a href="">Apple Newsroom announcement</a>:</p>
  125. <blockquote>
  126.  <p>iPadOS 13.4 brings trackpad support to iPad for the first time for
  127. a more natural typing experience and added precision for tasks
  128. such as writing and selecting text, working with spreadsheets and
  129. pro workflows. Designed specifically for the touch-first
  130. experience on iPad, the cursor appears as a circle that highlights
  131. user interface elements, text fields and apps on the Home screen
  132. and Dock, giving a clear indication of what users can click on.</p>
  133. </blockquote>
  135. <p>In neither of these cases is <em>cursor</em> ambiguous — in context, it’s completely clear they’re referring to the trackpad pointer. But as a general rule, it’s better to err on the side of precision, and <em>pointer</em> and <em>insertion point</em> always avoid ambiguity.</p>
  137. <p>In its technical documentation, Apple is clear. <a href="">In the updated Human Interface Guidelines</a>:</p>
  139. <blockquote>
  140.  <p><strong>Pointers (iPadOS)</strong></p>
  142. <p>iPadOS 13.4 introduces dynamic pointer effects and behaviors that
  143. enhance the experience of using a pointing device with iPad. As
  144. people use a pointing device, iPadOS automatically adapts the
  145. pointer to the current context, providing rich visual feedback and
  146. just the right level of precision needed to enhance productivity
  147. and simplify common tasks.</p>
  149. <p>The iPadOS pointing system gives people an additional way to
  150. interact with apps and content — it doesn’t replace touch. Some
  151. people may continue to use touch only, while others may prefer to
  152. use the pointer or a combination of both. Let people choose how to
  153. interact with your app, and avoid condensing your interface or
  154. making changes that require them to use the pointer.</p>
  155. </blockquote>
  157. <p>From Apple’s excellent <em>Apple Style Guide</em> (<a href="">available free of charge in the Apple Books store</a>):</p>
  159. <blockquote>
  160.  <p>cursor <br />
  161. Don’t use in describing the macOS or iOS interface; use <em>insertion
  162. point</em> or <em>pointer</em>, depending on the context. The term <em>cursor</em>
  163. is appropriate when you describe the VoiceOver interface and may
  164. be appropriate when you describe other interfaces and in developer
  165. materials.</p>
  166. </blockquote>
  168. <p>“Other interfaces” would include the terminal/command-line, where the (perhaps) blinking insertion point <a href="/misc/2020/03/terminal-cursor.png">is properly called the <em>cursor</em></a>.</p>
  170. <p>When it comes to pointers, it’s worth noting the <em>Apple Style Guide</em> recommends getting specific:</p>
  172. <blockquote>
  173.  <p>pointer <br />
  174. OK in general references, but be specific whenever appropriate:
  175. <em>arrow</em>, <em>crosshair</em>, <em>I-beam</em>.</p>
  176. </blockquote>
  178. <p>And, of course, the Apple Style Guide prescribes <em>OK</em>, never <em>okay</em>.</p>
  182.    ]]></content>
  183.  <title>★ Curse Words</title></entry><entry>
  184. <title>Nikkei Asian Review: ‘Apple Weighs Delaying 5G iPhone Launch by Months, Sources Say’</title>
  185. <link rel="alternate" type="text/html" href="" />
  186. <link rel="shorturl" type="text/html" href="" />
  187. <link rel="related" type="text/html" href="" />
  188. <id>,2020:/linked//6.36628</id>
  189. <published>2020-03-28T23:14:00Z</published>
  190. <updated>2020-03-28T23:16:56Z</updated>
  191. <author>
  192. <name>John Gruber</name>
  193. <uri></uri>
  194. </author>
  195. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  196. <p>Yifan Yu, Lauly Li, and Cheng Ting-Fang, reporting for Nikkei:</p>
  198. <blockquote>
  199.  <p>The Cupertino, California-based tech giant has held internal
  200. discussions on the possibility of delaying the launch by months,
  201. three people familiar with the matter said, while supply chain
  202. sources say practical hurdles could push back the release,
  203. originally scheduled for September.</p>
  205. <p>“Supply chain constraint aside, Apple is concerned that the
  206. current situation would significantly lower consumer appetite to
  207. upgrade their phones, which could lead to a tame reception of the
  208. first 5G iPhone,” said a source with direct knowledge of the
  209. discussion. “They need the first 5G iPhone to be a hit.” […]</p>
  211. <p>The engineering development of the 5G iPhone has also been
  212. affected by travel curbs introduced in the U.S., China and
  213. elsewhere to combat the coronavirus, two people with knowledge of
  214. Apple’s schedule said. The company was supposed to work with
  215. suppliers to develop a more concrete prototype for the new phones
  216. from early March, but it had to delay such close collaboration,
  217. which requires hands-on testing, until the end of the month,
  218. before postponing it again due to the worsening pandemic in the
  219. U.S., they said.</p>
  220. </blockquote>
  222. <p>Of course Apple is discussing this. Nikkei’s report from Asian suppliers is, of course, focused on hardware, but on the software side keep in mind that iOS 14 might be delayed or severely scaled back as well. Apple might <em>have</em> to delay the launch of new iPhones this year, and they might <em>want</em> to delay them. “Always in motion is the future” a wise little fellow once said. Never truer than in the midst of this crisis.</p>
  224. <div>
  225. <a  title="Permanent link to ‘Nikkei Asian Review: ‘Apple Weighs Delaying 5G iPhone Launch by Months, Sources Say’’"  href="">&nbsp;★&nbsp;</a>
  226. </div>
  228. ]]></content>
  229.  </entry><entry>
  230. <title>Dumb and Dumber</title>
  231. <link rel="alternate" type="text/html" href="" />
  232. <link rel="shorturl" type="text/html" href="" />
  233. <link rel="related" type="text/html" href="" />
  234. <id>,2020:/linked//6.36625</id>
  235. <published>2020-03-28T21:01:28Z</published>
  236. <updated>2020-03-28T21:16:53Z</updated>
  237. <author>
  238. <name>John Gruber</name>
  239. <uri></uri>
  240. </author>
  241. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  242. <p>ABC 7 NYC reporter CeFaan Kim, on Twitter:</p>
  244. <blockquote>
  245.  <p>Multiple sources tell @ABC Pres. Trump turned to former Yankee Alex Rodriguez for advice this week. A source close to Rodriguez described the call as “pleasant” adding that Trump was seeking thoughts from A-Rod about the coronavirus response.</p>
  246. </blockquote>
  248. <p>A-Rod: <a href="">great player</a>, fun announcer, but <a href="">not exactly the sharpest knife in the box</a>. So, yeah, he’s probably our next Secretary of Health and Human Services.</p>
  250. <div>
  251. <a  title="Permanent link to ‘Dumb and Dumber’"  href="">&nbsp;★&nbsp;</a>
  252. </div>
  254. ]]></content>
  255.  </entry><entry>
  256. <title>‘Slop Machines’</title>
  257. <link rel="alternate" type="text/html" href="" />
  258. <link rel="shorturl" type="text/html" href="" />
  259. <link rel="related" type="text/html" href="" />
  260. <id>,2020:/linked//6.36624</id>
  261. <published>2020-03-28T20:57:05Z</published>
  262. <updated>2020-03-28T20:59:44Z</updated>
  263. <author>
  264. <name>John Gruber</name>
  265. <uri></uri>
  266. </author>
  267. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  268. <p>Fascinating profile by John Semley for Eater back in 2017:</p>
  270. <blockquote>
  271.  <p>Since it opened in April 1963, R.C. Farms has had a very particular relationship with the overflowing decadence of nearby Las Vegas. At the time, the Combs family operated a modest hog farm in Chula Vista, near San Diego. They established relationships with a local army base, collecting food scraps to be reused as pig feed. Every year the base would contract out the privilege of collecting their wasted food to the highest bidder, with a few local farmers vying for the deal. But in Vegas, tens of thousands of pounds of food were going to waste. “My dad came here to Vegas for his 70th birthday, to have little gambling vacation,” Combs said as we sat at the round kitchen table of his modest bungalow farmhouse. On that auspicious trip, Combs’s father wandered through a backdoor of the now-long-gone Navajo-themed Thunderbird Hotel, and he came upon a huge container full of food being thrown away — the same sort of stuff he was bidding on back in La Mesa.</p>
  273. <p>Combs told me the story with a well-practiced, raconteur’s confidence. It’s a tale he’s likely told a hundred times before, slowly metastasizing with each telling into a bona fide legend: Imagine Jed Clampett happening across oil in his fetid swamp, except that the treasure is something that was being chucked away. Where the casinos saw only untouched shrimp cocktails and half-nibbled slabs of heat-lamp-warmed prime rib, the older Combs saw profit. He leased 150 acres north of the Strip, at the dead end of a dirt road, and installed his son to run the place. The young Bob (affectionately known as “Goof” to his family) arranged deals with several of the old-school casinos — the Desert Inn, the Stardust, the Sands, the Flamingo, the Sahara, the Tropicana, Caesars, the Riviera, and other locals-only joints. The business model was simple: collect buffet food scraps, reprocess them as feed, fatten hogs, send them off to slaughter.</p>
  274. </blockquote>
  276. <div>
  277. <a  title="Permanent link to ‘‘Slop Machines’’"  href="">&nbsp;★&nbsp;</a>
  278. </div>
  280. ]]></content>
  281.  </entry><entry>
  282. <title>From the Department of Unexpected COVID-19 Consequences</title>
  283. <link rel="alternate" type="text/html" href="" />
  284. <link rel="shorturl" type="text/html" href="" />
  285. <link rel="related" type="text/html" href="" />
  286. <id>,2020:/linked//6.36623</id>
  287. <published>2020-03-28T18:34:37Z</published>
  288. <updated>2020-03-28T18:48:28Z</updated>
  289. <author>
  290. <name>John Gruber</name>
  291. <uri></uri>
  292. </author>
  293. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  294. <p>Tiana Bohner, reporting for Fox 5 Las Vegas:</p>
  296. <blockquote>
  297.  <p>A Las Vegas farm relied on strip casinos as its main food source for 4,000 pigs. Now it’s getting creative to keep them full. “Pigs are a lot like us so they love sweets, candies, ice cream,” Las Vegas Livestock co-owner Hank Combs said. “They like meat and potatoes. They’re not a big fan of salads and produce, but they will eat it.</p>
  299. <p>On a normal day, the farm would get 20 tons of food from casinos and restaurants across the valley. Once the strip shut down and casinos closed, their food source was cut off.</p>
  301. <p>“You know we’re just one of the many stories out there in the world and I’m just trying to survive, keep the pigs fed, keep the employees employed,” Combs said.</p>
  302. </blockquote>
  304. <p>It is fascinating the way this crisis is revealing how interconnected our world is. The repercussions are seemingly infinite. It makes sense, now that I read it, that Vegas area pig farms would purchase the surplus food from the casino buffets (20 tons a day!), but until this moment, it never occurred to me that pig farming could be massively disrupted by the closing of casinos.</p>
  306. <p>Something to think about as I eat bacon for lunch.</p>
  308. <div>
  309. <a  title="Permanent link to ‘From the Department of Unexpected COVID-19 Consequences’"  href="">&nbsp;★&nbsp;</a>
  310. </div>
  312. ]]></content>
  313.  </entry><entry>
  314. <title>How to Turn Trump’s Daily Virus Misinformation Show Into a Vector for the Truth</title>
  315. <link rel="alternate" type="text/html" href="" />
  316. <link rel="shorturl" type="text/html" href="" />
  317. <link rel="related" type="text/html" href="" />
  318. <id>,2020:/linked//6.36622</id>
  319. <published>2020-03-27T20:53:47Z</published>
  320. <updated>2020-03-27T20:59:34Z</updated>
  321. <author>
  322. <name>John Gruber</name>
  323. <uri></uri>
  324. </author>
  325. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  326. <p><a href="">Speaking of</a> good journalism battling against misinformation, this is an important idea from Dan Froomkin at Press Watch:</p>
  328. <blockquote>
  329.  <p>These are not political rallies, or spin sessions, or even normal press briefings. These are urgent, emergency communications.</p>
  331. <p>And if — rather than sharing credible updates, thoughtful guidance, expressions of empathy and reasoned optimism — Trump lies, spreads misinformation and toots his own horn during these emergency communications, <em>that is the news</em>. Each and every time he does it.</p>
  333. <p>So rather than hide what’s happening, news organizations should respond by doing journalism – in this case, some journalistic jujitsu. When Trump spreads misinformation, the networks need to show viewers, in real time, the correct information. When he lies and contradicts himself, they need to provide the necessary context as he speaks. When he puffs himself up, they need to remind viewers of his massive failures.</p>
  334. </blockquote>
  336. <div>
  337. <a  title="Permanent link to ‘How to Turn Trump’s Daily Virus Misinformation Show Into a Vector for the Truth’"  href="">&nbsp;★&nbsp;</a>
  338. </div>
  340. ]]></content>
  341.  </entry><entry>
  342. <title>Snopes Is Hiring</title>
  343. <link rel="alternate" type="text/html" href="" />
  344. <link rel="shorturl" type="text/html" href="" />
  345. <link rel="related" type="text/html" href="" />
  346. <id>,2020:/linked//6.36621</id>
  347. <published>2020-03-27T19:12:50Z</published>
  348. <updated>2020-03-27T21:34:33Z</updated>
  349. <author>
  350. <name>John Gruber</name>
  351. <uri></uri>
  352. </author>
  353. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  354. <p>Snopes:</p>
  356. <blockquote>
  357.  <p> is an independent publication owned and operated by Snopes Media Group. We are slightly more than a baker’s dozen of reporters, editors, developers, and professionals who are passionate about journalism, media literacy, and, of course, fighting misinformation. We work remotely — there is no official Snopes office — but we maintain a collaborative and supportive team dynamic.</p>
  358. </blockquote>
  360. <p>Snopes managing editor Doreen Marchionni is a good friend and a great journalist. For the reporting jobs, they’re looking for folks with capital-J journalism experience. But they’re also hiring developers and communications specialists. I know there’s a lot of overlap with all of these jobs with DF readers, and good employers (with a fully remote work culture) who are hiring right now are few and far between.</p>
  362. <p>It goes without saying that Snopes’s mission — countering misinformation with verifiable journalism — has never been more essential. Never. Even if you’re not looking for a job, <a href="">you can support Snopes with a membership</a>, and they’ll thank you for it.</p>
  364. <div>
  365. <a  title="Permanent link to ‘Snopes Is Hiring’"  href="">&nbsp;★&nbsp;</a>
  366. </div>
  368. ]]></content>
  369.  </entry><entry>
  370. <title>Apple Releases New COVID-19 App and Website Based on CDC Guidance</title>
  371. <link rel="alternate" type="text/html" href="" />
  372. <link rel="shorturl" type="text/html" href="" />
  373. <link rel="related" type="text/html" href="" />
  374. <id>,2020:/linked//6.36620</id>
  375. <published>2020-03-27T18:32:45Z</published>
  376. <updated>2020-03-27T18:33:56Z</updated>
  377. <author>
  378. <name>John Gruber</name>
  379. <uri></uri>
  380. </author>
  381. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  382. <p>Apple Newsroom:</p>
  384. <blockquote>
  385.  <p>The COVID-19 app and website allow users to answer a series of questions around risk factors, recent exposure and symptoms for themselves or a loved one. In turn, they will receive CDC recommendations on next steps, including guidance on social distancing and self-isolating, how to closely monitor symptoms, whether or not a test is recommended at this time, and when to contact a medical provider. This new screening tool is designed to be a resource for individuals and does not replace instructions from healthcare providers or guidance from state and local health authorities.</p>
  386. </blockquote>
  388. <p>Nicely designed, too.</p>
  390. <div>
  391. <a  title="Permanent link to ‘Apple Releases New COVID-19 App and Website Based on CDC Guidance’"  href="">&nbsp;★&nbsp;</a>
  392. </div>
  394. ]]></content>
  395.  </entry><entry>
  396. <title>The Apple A12Z Bionic SoC Is Just a Renamed A12X With an Enabled GPU Core</title>
  397. <link rel="alternate" type="text/html" href="" />
  398. <link rel="shorturl" type="text/html" href="" />
  399. <link rel="related" type="text/html" href="" />
  400. <id>,2020:/linked//6.36619</id>
  401. <published>2020-03-27T17:11:27Z</published>
  402. <updated>2020-03-27T21:33:00Z</updated>
  403. <author>
  404. <name>John Gruber</name>
  405. <uri></uri>
  406. </author>
  407. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  408. <p>Vaidyanathan Subramaniam, writing for NotebookCheck:</p>
  410. <blockquote>
  411.  <p>Essentially what this means is that, the A12X and A12Z are the same physical chip (pending the results of the A12Z floorplan analysis) with the same physical number of CPU and GPU cores. Anandtech feels that the A12Z could, in fact, be <a href="">a re-binned variant of the A12X</a>. Recent <a href="">comparative benchmarks</a> have also shown that the A12Z offers minimal performance improvements compared to the A12X.</p>
  412. </blockquote>
  414. <p>The A12X has 8 GPU cores, but only 7 are enabled. The A12Z uses all 8 — that pretty much explains the “<a href="">CPU performance is the same but GPU is slightly better</a>” benchmarking differences completely.</p>
  416. <p><strong>Update:</strong> To be clear, this ought not be controversial in the least. See <a href="">this thread on Twitter from Quinn Nelson</a>.</p>
  418. <div>
  419. <a  title="Permanent link to ‘The Apple A12Z Bionic SoC Is Just a Renamed A12X With an Enabled GPU Core’"  href="">&nbsp;★&nbsp;</a>
  420. </div>
  422. ]]></content>
  423.  </entry><entry>
  424. <title>Every Default MacOS Wallpaper in 5K</title>
  425. <link rel="alternate" type="text/html" href="" />
  426. <link rel="shorturl" type="text/html" href="" />
  427. <link rel="related" type="text/html" href="" />
  428. <id>,2020:/linked//6.36617</id>
  429. <published>2020-03-27T16:46:22Z</published>
  430. <updated>2020-03-27T16:50:14Z</updated>
  431. <author>
  432. <name>John Gruber</name>
  433. <uri></uri>
  434. </author>
  435. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  436. <p>Stephen Hackett:</p>
  438. <blockquote>
  439.  <p>Every major version of <del>Mac OS X</del> macOS has come with a new default wallpaper. As you can see, I have collected them all here. While great in their day, the early wallpapers are now quite small in the world of 5K displays.</p>
  441. <p>Major props to <a href="">the world-class designer</a> who does all the art of Relay FM, the mysterious <a href="">@forgottentowel</a>, for upscaling some of these for modern screens.</p>
  442. </blockquote>
  444. <p>Fun trip down memory lane.</p>
  446. <div>
  447. <a  title="Permanent link to ‘Every Default MacOS Wallpaper in 5K’"  href="">&nbsp;★&nbsp;</a>
  448. </div>
  450. ]]></content>
  451.  </entry><entry>
  452. <title>The Talk Show: ‘The Subtle Difference Between Hand Sanitizer and Vodka’</title>
  453. <link rel="alternate" type="text/html" href="" />
  454. <link rel="shorturl" type="text/html" href="" />
  455. <link rel="related" type="text/html" href="" />
  456. <id>,2020:/linked//6.36616</id>
  457. <published>2020-03-27T04:27:30Z</published>
  458. <updated>2020-03-27T04:27:31Z</updated>
  459. <author>
  460. <name>John Gruber</name>
  461. <uri></uri>
  462. </author>
  463. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  464. <p>Matthew Panzarino returns to the show. Topics include the brand new MacBook Air and iPad Pros, and, you know, global pandemics in the internet age.</p>
  466. <p>Brought to you by these fine sponsors:</p>
  468. <ul>
  469. <li><a href=";utm_source=rss&amp;utm_medium=referral&amp;utm_campaign=daringfireball">Yes Plz</a>: Brew yourself the best coffee. Try YES PLZ today and save $5 with code <strong>fireball5</strong>.</li>
  470. <li><a href="">Eero</a>: Wi-Fi done right. Get free overnight shipping with promo code <strong>thetalkshow</strong>.</li>
  471. <li><a href="">Squarespace</a>: Make your next move. Use code <strong>talkshow</strong> for 10% off your first order.</li>
  472. </ul>
  474. <div>
  475. <a  title="Permanent link to ‘The Talk Show: ‘The Subtle Difference Between Hand Sanitizer and Vodka’’"  href="">&nbsp;★&nbsp;</a>
  476. </div>
  478. ]]></content>
  479.  </entry><entry>
  480. <title>Google Podcasts Now on iOS</title>
  481. <link rel="alternate" type="text/html" href="" />
  482. <link rel="shorturl" type="text/html" href="" />
  483. <link rel="related" type="text/html" href="" />
  484. <id>,2020:/linked//6.36615</id>
  485. <published>2020-03-26T21:46:49Z</published>
  486. <updated>2020-03-27T22:47:52Z</updated>
  487. <author>
  488. <name>John Gruber</name>
  489. <uri></uri>
  490. </author>
  491. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  492. <p>Zack Reneau-Wedeen, product manager for Google Podcasts:</p>
  494. <blockquote>
  495.  <p>But you should be able to find new favorites in minutes, not
  496. years. We’ve redesigned the Google Podcasts app to make it easier
  497. to discover podcasts you’ll love, build your list of go-to
  498. podcasts, and customize your listening. To support listeners on
  499. more platforms, we’re also bringing Google Podcasts to iOS for the
  500. first time and adding support for subscriptions on Google Podcasts
  501. for Web. Regardless of the platform you’re using, your listening
  502. progress will sync across devices, and you’ll be able to pick up
  503. right where you left off.</p>
  505. <p>The new app is organized around three tabs: Home, Explore and
  506. Activity. The Home tab features a feed of new episodes and gives
  507. you quick access to your subscribed shows. When you select an
  508. episode you want to listen to, you’ll now see topics or people
  509. covered in that podcast, and you can easily jump to Google Search
  510. to learn more.</p>
  511. </blockquote>
  513. <p>Seems to me that Google has never really made an effort to get serious about podcasts. Maybe this is it. I kicked the tires on the iOS client for a few shows today, and it’s pretty decent, and surprisingly iOS-like for a Google app. (Some <a href="/misc/2020/03/google-podcasts-linebreaks.png">strange decisions on line breaks</a> with even slightly long words like “Coronavirus” though.) The integration with Google search for related topics is clever and unobtrusive — there if you want it, easily ignored if you don’t.</p>
  515. <p>Two more things: (1) No iPad support — it just runs as an iPhone app on iPads; (2) I don’t get the icon at all. What is that supposed to be?</p>
  517. <p><strong>Update:</strong> A few readers have pointed out the oddness of shipping on iOS first. I’m not sure what the explanation is there, but on iOS, Google Podcasts is a brand-new app. It didn’t exist until now. On Android, Google Podcasts has been out for a while, and it looks mostly the same. When I was testing it today, I was playing with it on both iPhone and Pixel 4. The currently-shipping version on Android looks mostly the same, but lacks the main three-tab interface at the bottom.</p>
  519. <p>As for the icon, folks say it represents a waveform. If you say so. To me it looks like a knock-off of the new Slack icon.</p>
  521. <div>
  522. <a  title="Permanent link to ‘Google Podcasts Now on iOS’"  href="">&nbsp;★&nbsp;</a>
  523. </div>
  525. ]]></content>
  526.  </entry><entry>
  527. <title>2018 Retina MacBook Airs May be Susceptible to Anti-Reflective Coating Issues</title>
  528. <link rel="alternate" type="text/html" href="" />
  529. <link rel="shorturl" type="text/html" href="" />
  530. <link rel="related" type="text/html" href="" />
  531. <id>,2020:/linked//6.36614</id>
  532. <published>2020-03-26T21:22:03Z</published>
  533. <updated>2020-03-27T01:46:57Z</updated>
  534. <author>
  535. <name>John Gruber</name>
  536. <uri></uri>
  537. </author>
  538. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  539. <p>Joe Rossignol, reporting for MacRumors:</p>
  541. <blockquote>
  542.  <p>Apple this week acknowledged that MacBook Air models with Retina displays can exhibit anti-reflective coating issues, as indicated in a memo shared with Apple Authorized Service Providers and obtained by MacRumors. “Retina displays on some MacBook, MacBook Air, and MacBook Pro computers can exhibit anti-reflective (AR) coating issues,” the memo states.</p>
  544. <p>Apple’s internal service documentation for this issue previously only mentioned MacBook Pro and discontinued 12-inch MacBook models with Retina displays, but the MacBook Air is now mentioned in at least two places. Apple added a Retina display to the MacBook Air in October 2018 and all models of the notebook have featured once since.</p>
  545. </blockquote>
  547. <p>I don’t understand how this is <em>still</em> an issue. My beloved 2014 13-inch MacBook Pro is afflicted with this, and I never bothered getting it repaired. Whatever causes this, you’d think Apple would’ve identified the problem after a few years.</p>
  549. <p><strong>Update:</strong> I have it on good authority that the MacBook Air, retina display or otherwise, is <em>not</em> covered by the repair program. Unclear to me is how widespread the problem is with Airs.</p>
  551. <div>
  552. <a  title="Permanent link to ‘2018 Retina MacBook Airs May be Susceptible to Anti-Reflective Coating Issues’"  href="">&nbsp;★&nbsp;</a>
  553. </div>
  555. ]]></content>
  556.  </entry><entry>
  557. <title>Safari Now Has Full Third-Party Cookie Blocking</title>
  558. <link rel="alternate" type="text/html" href="" />
  559. <link rel="shorturl" type="text/html" href="" />
  560. <link rel="related" type="text/html" href="" />
  561. <id>,2020:/linked//6.36613</id>
  562. <published>2020-03-25T17:03:03Z</published>
  563. <updated>2020-03-25T18:38:28Z</updated>
  564. <author>
  565. <name>John Gruber</name>
  566. <uri></uri>
  567. </author>
  568. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  569. <p>John Wilander, writing at the WebKit blog:</p>
  571. <blockquote>
  572.  <p>Safari continues to pave the way for privacy on the web, this time
  573. as the first mainstream browser to fully block third-party cookies
  574. by default. As far as we know, only the <a href="">Tor Browser</a> has
  575. featured full third-party cookie blocking by default before
  576. Safari, but <a href="">Brave just has a few exceptions</a> left in its
  577. blocking so in practice they are in the same good place. We know
  578. Chrome wants this behavior too and they announced that they’ll be
  579. <a href="">shipping it by 2022</a>.</p>
  581. <p>We will report on our experiences of full third-party cookie
  582. blocking to the privacy groups in W3C to help other browsers take
  583. the leap.</p>
  584. </blockquote>
  586. <p>Somehow I feel like Google could ship this in Chrome long before 2022 if they really wanted to.</p>
  588. <div>
  589. <a  title="Permanent link to ‘Safari Now Has Full Third-Party Cookie Blocking’"  href="">&nbsp;★&nbsp;</a>
  590. </div>
  592. ]]></content>
  593.  </entry><entry>
  594. <title>‘What I Learned When My Husband Got Sick With Coronavirus’</title>
  595. <link rel="alternate" type="text/html" href="" />
  596. <link rel="shorturl" type="text/html" href="" />
  597. <link rel="related" type="text/html" href="" />
  598. <id>,2020:/linked//6.36612</id>
  599. <published>2020-03-25T16:29:47Z</published>
  600. <updated>2020-03-25T19:31:09Z</updated>
  601. <author>
  602. <name>John Gruber</name>
  603. <uri></uri>
  604. </author>
  605. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  606. <p>Jessica Lustig, writing for The New York Times Magazine:</p>
  608. <blockquote>
  609.  <p>CK and I had settled in to watch “Chernobyl,” the HBO series about
  610. the 1986 nuclear accident and its aftermath, when T first felt
  611. sick and went to lie down in the bedroom. We stopped after three
  612. episodes. That time, when we would sit on the couch watching
  613. something together, is behind us. Now there is too much rushing
  614. back and forth, making sure T has a little dinner — just a tiny
  615. bowl of soup, just an appetizer, really, that he is unable to
  616. smell, that he fights nausea to choke down — taking his
  617. temperature, monitoring his oxygen-saturation levels with the
  618. fingertip pulse oximeter brought by a friend from the drugstore on
  619. the doctor’s advice, taking him tea, dispensing his meds, washing
  620. my hands over and over, texting the doctor to say T is worse
  621. again, standing next to him while he coughs into the covers,
  622. rubbing his knees through the blankets.</p>
  624. <p>“You shouldn’t stay here,” he says, but he gets more frightened as
  625. night comes, dreading the long hours of fever and soaking sweats
  626. and shivering and terrible aches. “This thing grinds you like a
  627. mortar,” he says.</p>
  628. </blockquote>
  630. <p>Brutal, heart-wrenching story, beautifully written.</p>
  632. <p>Stay safe.</p>
  634. <div>
  635. <a  title="Permanent link to ‘‘What I Learned When My Husband Got Sick With Coronavirus’’"  href="">&nbsp;★&nbsp;</a>
  636. </div>
  638. ]]></content>
  639.  </entry><entry>
  640. <title>Tokyo Olympics Officially Postponed to Next Year</title>
  641. <link rel="alternate" type="text/html" href="" />
  642. <link rel="shorturl" type="text/html" href="" />
  643. <link rel="related" type="text/html" href="" />
  644. <id>,2020:/linked//6.36611</id>
  645. <published>2020-03-25T15:57:48Z</published>
  646. <updated>2020-03-25T16:02:29Z</updated>
  647. <author>
  648. <name>John Gruber</name>
  649. <uri></uri>
  650. </author>
  651. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  652. <p>Michelle R. Martinelli, reporting for USA Today:</p>
  654. <blockquote>
  655.  <p>A day after USA Today Sports broke the news that the 2020 Summer Olympics would be postponed because of the global coronavirus pandemic, it became official. The president of the International Olympic Committee, Thomas Bach, and Japanese prime minister, Shinzo Abe, announced Tuesday in a joint statement that the 2020 Tokyo Games — which were originally scheduled to begin July 24 — will be postponed. They said the Olympics “must be rescheduled to a date beyond 2020 but not later than summer 2021,” but they’ll still be referred to as the 2020 Olympics.</p>
  656. </blockquote>
  658. <p>A surprise to no one at this point, but still a hell of a thing to see. This is the first time the Olympics have ever been postponed, and they’ve only ever been canceled during World Wars I and II.</p>
  660. <div>
  661. <a  title="Permanent link to ‘Tokyo Olympics Officially Postponed to Next Year’"  href="">&nbsp;★&nbsp;</a>
  662. </div>
  664. ]]></content>
  665.  </entry><entry>
  666. <title>Facebook, Google Could Lose Over $44 Billion in Ad Revenue in 2020 Because of Coronavirus</title>
  667. <link rel="alternate" type="text/html" href="" />
  668. <link rel="shorturl" type="text/html" href="" />
  669. <link rel="related" type="text/html" href="" />
  670. <id>,2020:/linked//6.36610</id>
  671. <published>2020-03-25T15:33:30Z</published>
  672. <updated>2020-03-25T15:36:18Z</updated>
  673. <author>
  674. <name>John Gruber</name>
  675. <uri></uri>
  676. </author>
  677. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  678. <p>Todd Spangler, reporting for Variety:</p>
  680. <blockquote>
  681.  <p>Ad spending is falling off a cliff amid the COVID-19 pandemic — and Facebook and Google, the two heavyweights in digital advertising, are expected to bear the brunt of the downturn in terms of sheer dollars lost.</p>
  683. <p>The two internet giants together could see more than $44 billion in worldwide ad revenue evaporate in 2020, Cowen &amp; Co. analysts estimate. That said, both Google and Facebook will continue to be massively profitable even with double-digit revenue drops.</p>
  684. </blockquote>
  686. <p>Usage of both Facebook and Google is spiking, because everyone’s at home all day. But the general rule of thumb since the dawn of time is that the first thing to get cut in a recession is the ad budget.</p>
  688. <div>
  689. <a  title="Permanent link to ‘Facebook, Google Could Lose Over $44 Billion in Ad Revenue in 2020 Because of Coronavirus’"  href="">&nbsp;★&nbsp;</a>
  690. </div>
  692. ]]></content>
  693.  </entry><entry>
  694. <title>‘Who Would Have Thought an iPad Cursor Could Be So Much Fun?’</title>
  695. <link rel="alternate" type="text/html" href="" />
  696. <link rel="shorturl" type="text/html" href="" />
  697. <link rel="related" type="text/html" href="" />
  698. <id>,2020:/linked//6.36609</id>
  699. <published>2020-03-25T03:59:00Z</published>
  700. <updated>2020-03-25T04:17:59Z</updated>
  701. <author>
  702. <name>John Gruber</name>
  703. <uri></uri>
  704. </author>
  705. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  706. <p>Craig Mod, writing for Wired:</p>
  708. <blockquote>
  709.  <p>Move the pointer above a button and the circle morphs into the
  710. button itself, “snapping” into it, enveloping it like an amoeba,
  711. causing it to glow in a pleasing way. What this means is that the
  712. usual precision of a trackpad isn’t required to get exact hits on
  713. navigational elements. If you own an Apple TV, you’re already
  714. familiar with this vibe — it’s how the cursor on the TV “jumps”
  715. from icon to icon with a kind of sticky momentum. Similarly, on
  716. the iPad home screen, you can “lazily” slam the cursor around and
  717. have it lock onto applications with an eerie telepathy not
  718. experienced on a desktop OS.</p>
  720. <p>The cursor itself, too, has momentum. It continues to glide on the
  721. screen for just a short millisecond after you stop moving your
  722. finger on the trackpad. This sounds more annoying than it is in
  723. practice. (And you can modify almost all these behaviors to your
  724. liking in Settings → General → Trackpad, and Settings →
  725. Accessibility → Pointer.) What I’ve found is that this momentum
  726. creates a subtle design cohesion between scrolling and scroll
  727. bounce, selecting applications, locking onto buttons, and just
  728. generally moving things around the screen.</p>
  729. </blockquote>
  731. <p>Best piece I’ve seen on the joy and utility of iPadOS’s new pointer support. Five days in and I can’t imagine doing without it.</p>
  733. <div>
  734. <a  title="Permanent link to ‘‘Who Would Have Thought an iPad Cursor Could Be So Much Fun?’’"  href="">&nbsp;★&nbsp;</a>
  735. </div>
  737. ]]></content>
  738.  </entry><entry>
  739. <title>‘Something, Something, Something Murder’</title>
  740. <link rel="alternate" type="text/html" href="" />
  741. <link rel="shorturl" type="text/html" href="" />
  742. <link rel="related" type="text/html" href="" />
  743. <id>,2020:/linked//6.36608</id>
  744. <published>2020-03-24T19:19:49Z</published>
  745. <updated>2020-03-24T19:19:50Z</updated>
  746. <author>
  747. <name>John Gruber</name>
  748. <uri></uri>
  749. </author>
  750. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  751. <p>Dave Pell:</p>
  753. <blockquote>
  754.  <p>The excellent <a href="">Damon Lindelof</a> is writing this exclusive,
  755. serialized story for <a href="">NextDraft</a> to help us, and him,
  756. through the quarantine. Chapters will update here periodically,
  757. but for the epic experience and all the day’s real news, get the
  758. free newsletter or app by touching the head below (please use a
  759. rubber glove).</p>
  760. </blockquote>
  762. <p>Yes, NextDraft is this week’s sponsor at DF. No, this is not my official thank-you post. I just wanted to throw in an early-in-the-week link to Lindelof’s story, which I’m enjoying very much. Catch up now, but I think it’s best enjoyed in the daily serial format, which is why I’m jumping the gun with this link.</p>
  764. <p>This week more than ever, we need some fun diversions.</p>
  766. <div>
  767. <a  title="Permanent link to ‘‘Something, Something, Something Murder’’"  href="">&nbsp;★&nbsp;</a>
  768. </div>
  770. ]]></content>
  771.  </entry><entry>
  772. <title>‘100,000 Miles and One Week With an iPad Pro’</title>
  773. <link rel="alternate" type="text/html" href="" />
  774. <link rel="shorturl" type="text/html" href="" />
  775. <link rel="related" type="text/html" href="" />
  776. <id>,2020:/linked//6.36607</id>
  777. <published>2020-03-24T18:22:45Z</published>
  778. <updated>2020-03-25T20:57:05Z</updated>
  779. <author>
  780. <name>John Gruber</name>
  781. <uri></uri>
  782. </author>
  783. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  784. <p>Matthew Panzarino, who went full-time on iPad Pro while traveling 18 months ago, reviewing the new iPad Pros for TechCrunch:</p>
  786. <blockquote>
  787.  <p>Lidar is a technology with a ton of promise and a slew of
  788. potential applications. Having this much more accurate way to
  789. bring the outside world into your device is going to open a lot of
  790. doors for Apple and developers over time, but my guess is that
  791. we’ll see those doors open over the next couple of years rather
  792. than all at once.</p>
  793. </blockquote>
  795. <p>I think the lidar sensor in the new iPad Pro is sort of like the U1 ultra-wideband chip in the iPhones 11. (The U1 chips is also apparently in the new iPad Pros.) It’s there for the future more than the present.</p>
  797. <p>The whole review is excellent, with a slew of insightful observations, but I particularly like this bit regarding multitasking:</p>
  799. <blockquote>
  800.  <p>With iPad Pro, no matter where I have been or what I have been
  801. doing, I was able to flip it open, swipe up and be issuing my
  802. first directive within seconds. As fast as my industry moves and
  803. as wild as our business gets, that kind of surety is literally
  804. priceless.</p>
  806. <p>Never once, however, did I wish that it was easier to use.</p>
  808. <p>Do you wish that a hammer is easier? No, you learn to hold it
  809. correctly and swing it accurately. The iPad could use a bit more
  810. of that.</p>
  812. <p>Currently, iPadOS is still too closely tethered to the sacred cow
  813. of simplicity. In a strange bout of irony, the efforts on behalf
  814. of the iPad software team to keep things simple (same icons, same
  815. grid, same app switching paradigms) and true to their original
  816. intent have instead caused a sort of complexity to creep into the
  817. arrangement.</p>
  818. </blockquote>
  820. <div>
  821. <a  title="Permanent link to ‘‘100,000 Miles and One Week With an iPad Pro’’"  href="">&nbsp;★&nbsp;</a>
  822. </div>
  824. ]]></content>
  825.  </entry><entry>
  827.    <link rel="alternate" type="text/html" href="" />
  828. <link rel="shorturl" href="" />
  829. <id>,2020://1.36606</id>
  830. <published>2020-03-24T17:02:23Z</published>
  831. <updated>2020-03-27T22:45:52Z</updated>
  832. <author>
  833. <name>John Gruber</name>
  834. <uri></uri>
  835. </author>
  836. <summary type="text">The new 2020 iPad Pros are, in most ways, minor spec bump updates to the 2018 iPad Pros. The camera system is better, there’s a new LIDAR sensor that greatly improves AR, and the built-in microphone system is noticeably improved. That’s about it.</summary>
  837. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  838. <p>The new 2020 iPad Pros are, in most ways, minor spec bump updates to the 2018 iPad Pros. The camera system is better, there’s a new lidar sensor that greatly improves AR, and the built-in microphone system is noticeably improved. That’s about it.</p>
  840. <p>That’s not a complaint. The 2018 iPad Pros were amazing devices, way ahead of their time in terms of performance. If it’s going to take two or more years between truly major updates to the iPad Pro, I want Apple to release a spec bump update mid-cycle. That’s what these iPad Pros are.</p>
  842. <h2>Performance</h2>
  844. <p>Let’s get this out of the way first. I’m using the phrase “<em>spec</em> bump” rather than “<em>speed</em> bump” to describe these new iPad Pros because they don’t really seem to be much faster than the 2018 models. Some numbers from <a href="">Geekbench 5</a>:</p>
  846. <!-- Markdown Table
  847. |                        | Single |  Multi | Compute |
  848. |------------------------------|-------:|-------:|--------:|
  849. | 2018 12.9″ iPad Pro          |  1,124 |  4,675 |   9,183 |
  850. | 2018 11″ iPad Pro            |  1,118 |  4,543 |   9,059 |
  851. | 2020 12.9″ iPad Pro          |  1,123 |  4,691 |  10,046 |
  852. | 2020 Core i5 MacBook Air     |  1,127 |  2,854 |   4,950 |
  853. | 2019 Core i9 16″ MacBook Pro |  1,263 |  7,277 |  25,351 |
  854. | 2019 iPhone 11 Pro           |  1,338 |  3,467 |   6,310 |
  855. -->
  857. <table width="425">
  858. <thead>
  859. <tr>
  860.  <th></th>
  861.  <th align="right">Single</th>
  862.  <th align="right">Multi</th>
  863.  <th align="right">Compute</th>
  864. </tr>
  865. </thead>
  866. <tbody>
  867. <tr>
  868.  <td>2018 12.9″ iPad Pro</td>
  869.  <td align="right">1,124</td>
  870.  <td align="right">4,675</td>
  871.  <td align="right">9,183</td>
  872. </tr>
  873. <tr>
  874.  <td>2018 11″ iPad Pro</td>
  875.  <td align="right">1,118</td>
  876.  <td align="right">4,543</td>
  877.  <td align="right">9,059</td>
  878. </tr>
  879. <tr>
  880.  <td>2020 12.9″ iPad Pro</td>
  881.  <td align="right">1,123</td>
  882.  <td align="right">4,691</td>
  883.  <td align="right">10,046</td>
  884. </tr>
  885. <tr>
  886.  <td><a href="">2020 Core i5 MacBook Air</a></td>
  887.  <td align="right">1,127</td>
  888.  <td align="right">2,854</td>
  889.  <td align="right">4,950</td>
  890. </tr>
  891. <tr>
  892.  <td>2019 Core i9 16″ MacBook Pro</td>
  893.  <td align="right">1,263</td>
  894.  <td align="right">7,277</td>
  895.  <td align="right">25,351</td>
  896. </tr>
  897. <tr>
  898.  <td>2019 iPhone 11 Pro</td>
  899.  <td align="right">1,338</td>
  900.  <td align="right">3,467</td>
  901.  <td align="right">6,310</td>
  902. </tr>
  903. </tbody>
  904. </table>
  906. <p>The thing worth noting is that the new iPad Pros sport a system-on-a-chip that Apple is calling the A12Z. The 2018 models use the A12X. Both are 8-core designs, with 4 high-performance cores and 4 high-efficiency cores. The way that works, basically, is that when your iPad is not breaking a sweat computationally, it uses the 4 high-efficiency cores; when it is breaking a sweat, it switches to the high-performance cores. The 8-core MacBook Pro scores better on the multi-core benchmark because its 8 cores are all, effectively, high-performance cores.</p>
  908. <p>Worth noting too are the numbers from the A13-powered iPhone 11. The A13 is faster in single-core performance than even the Core i9 16-inch MacBook Pro, but the A12X and Z hold their own, and still come out ahead in multi-core.</p>
  910. <p>Real-world performance may differ more significantly, but from what I can tell, A12Z CPU performance is unchanged from the A12X and GPU performance is only slightly improved. But iPad Pro performance was already great. Look at those numbers — the iPad Pro outperforms the new mid-range MacBook Air. The 16-inch MacBook Pro I’ve compared it to here starts at $2,800 and it weighs 4.3 pounds (2.0 kg).</p>
  912. <p>One more spec tweak: the 2018 iPad Pro models came with 4 GB of RAM, except for the ones with 1 TB of storage — those came with 6 GB of RAM. Apple never talks about RAM with iOS devices, but it’s easy to tell how much RAM is in a device using third-party utilities. With the 2020 lineup, all models seemingly come with 6 GB of RAM. In practical terms, this means the new iPad Pros should be able to keep more apps running at the same time without reloading them from scratch. In my personal day-to-day use, I don’t notice the difference.</p>
  914. <h2>Lidar and Dual-Lens Camera</h2>
  916. <p>As promised, lidar vastly improves the AR experience. No more warmup period where AR apps want you to pan the device around to allow the system to orient itself and get a sense of your environment — you just launch the app and it’s ready. I mostly tested this with Apple’s Measure app. Measuring the sizes of furniture and countertops is much faster, easier, and more accurate. I just measured a 3-foot shelf here in my office and the Measure app pegged it at precisely 36 inches, on the button.</p>
  918. <p>The lidar sensor also greatly helps with identifying walls and ceilings. It’s just as easy to use Measure to tell how far away something — again, say, a piece of furniture — is from the wall as it is to measure how big the thing itself is. On all other iOS devices — which is to say, all non-lidar-equipped iOS devices — Measure is not good at this.</p>
  920. <p>In short, if you’re an AR junkie, you should jump all over the new iPad Pro. If you’re not an AR junkie — which is to say the overwhelming majority of you — well, it’s not that big a deal. I don’t mean to be dismissive of AR and ARKit. I think an AR revolution is coming, and the whole “use your iPhone and iPad as ARKit devices” effort on Apple’s part — and it’s a massive effort — is laying the groundwork for an AR-first device to hit the ground running with developer support from day one. But are there really people for whom ARKit-powered apps are so important right now that they’ll upgrade to a new iPad just for lidar support? I suppose the answer is yes — for example, developers working on ARKit apps and games. But for most people the answer is clearly no.</p>
  922. <p>The new wide/ultra-wide dual-lens camera system on the new iPad Pros looks, on paper, a lot like the wide/ultra-wide dual-lens system on the non-Pro iPhone 11. And the results for regular still photography and video seem very comparable. But there’s at least one significant difference: the iPad Pro does not support Portrait mode with the main camera; the iPhone 11 does. (The iPad Pro <em>does</em> support Portrait mode with the front-facing self-portrait camera.) One reason for this, I suspect, is that the iPhone 11 has the A13 chip, while the iPad Pros have the previous-generation A12Z. The iPad Pro wide/ultra-wide cameras may in fact be the exact same cameras as the iPhone 11 — I don’t know, and Apple doesn’t make statements like that — but the iPad Pro can’t use the same software path for Portrait mode that the iPhone 11 does because Portrait mode makes heavy use of machine learning and that means the Neural Engine — but the A13 Neural Engine is far more powerful than that of the A12Z. This could be the sort of thing that just didn’t make it for a mid-cycle iPadOS 13.4 software release; it wouldn’t surprise me if the new iPad Pros gain Portrait mode in iPadOS 14.0.</p>
  924. <p>In the meantime, I think supporting Portrait mode on the new iPad Pro would have required engineering effort that Apple instead chose to expend on supporting the lidar sensor for AR.</p>
  926. <p>In theory, a lidar sensor could be used to help with still photography and video. One can imagine how it could help with Portrait mode in particular — using lidar for the depth map to blur objects and scenery in the background based on how far away they are. Lidar could also help with identifying eyeglasses, hats, hair, etc. It’s not that simple though. The lidar sensor in the new iPad Pro has tremendous accuracy on the Z axis (depth), but not so much on the X and Y axes. It just doesn’t project <em>that</em> many dots. But the iPad Pro makes up for the lack of X/Y accuracy when you pan the iPad Pro around, by continuously scanning the dots in real time as you pan. When shooting still photos or video, however, you can’t assume that the user is going to pan. The iPad might even be locked down on a tripod. I do expect Apple to eventually use lidar, or something like lidar, as a focusing and depth-map aid for photography, but they’re not there yet. This lidar system is clearly designed for 3D mesh generation, not 2D depth mapping.</p>
  928. <h2>The New Microphone Array</h2>
  930. <p>One other notable hardware change in the 2020 iPad Pro: Apple claims it now uses the same five-microphone “studio quality” array that they introduced with <a href="">the 16-inch MacBook Pro in November</a>. Indeed, it does sound better, and background noise is reduced. Here are recordings I made side-by-side with a 2018 iPad Pro and the new 2020 iPad Pro. I can easily hear the improvement — richer sound, higher quality, and less noise.</p>
  932. <p>2018 iPad Pro:</p>
  934. <p><audio
  935.    src = "/misc/2020/03/ipad-pro-2018-mic-test.m4a"
  936.    controls
  937.    preload = "none"
  938. /></p>
  940. <p>2020 iPad Pro:</p>
  942. <p><audio
  943.    src = "/misc/2020/03/ipad-pro-2020-mic-test.m4a"
  944.    controls
  945.    preload = "none"
  946. /></p>
  948. <h2>This Is All Just a Prelude to the Thing We Really Want to Review</h2>
  950. <p>I’ve been testing a 12.9-inch iPad Pro with 1 TB of storage since Thursday (five days ago). Apple included the updated Smart Keyboard cover. There are two differences from the Smart Keyboard cover for the 2018 iPad Pros — (1) the camera cutout has been embiggened to accommodate the larger camera/lidar system; and (2) the back of the cover <a href="/misc/2020/03/smart-keyboard-apple-logo.jpeg">now has an debossed Apple logo</a>, oriented for landscape, natch.</p>
  952. <p>Apple did <em>not</em> include the product I really want to test, and which all of you really want to read about: the new <a href="">Magic Keyboard cover</a>. It’s no surprise that Apple has not yet made them available for review: they’re not shipping until “May”, and with the exception of the original AirPods, I can’t recall Apple providing reviewers with hardware more than a week or so in advance of shipping.</p>
  954. <p>The truth is I just don’t like the Smart Keyboard cover. I don’t like typing on it, and I want a trackpad.</p>
  956. <p>What I do when I write on my iPad is use a Bluetooth or USB keyboard. Apple’s <a href="">Bluetooth Magic Keyboard</a> is a great option — I particularly like it in <a href="">Studio Neat’s Canopy cover/stand</a>. I also enjoy writing on my iPad using a standalone external mechanical keyboard. One reason I prefer a standalone keyboard over the Smart Keyboard cover is simply that the keyboards feel better. But another is that if you’re setting it up on a desk or countertop, there’s no need to magnetically snap the iPad into a case, cover, or stand. You can just prop it up, which makes it utterly seamless to pick it up with one hand and walk away from the keyboard setup when you just want to go somewhere else with the iPad. It also allows you to do something with the iPad that no dedicated laptop can do: orient the screen vertically rather than horizontally, which makes a lot of sense for long-form writing. Here, for example, <a href="/misc/2020/03/ipad-pro-vertical.jpeg">is my setup as I write this very review</a>.<sup id="fnr1-2020-03-24"><a href="#fn1-2020-03-24">1</a></sup></p>
  958. <p>That said, I am deeply intrigued by the iPad Pro Magic Keyboard. In the meantime, we wait.</p>
  960. <h2>The Bottom Line</h2>
  962. <p>If you already have a 2018 iPad Pro, the only reason to even consider upgrading is if you’re somehow professionally involved with AR, or if you make serious use of your iPad camera. These are not <em>new</em> iPad Pros so much as <em>tweaked</em> iPad Pros. And the best part of holding onto a 2018 iPad Pro is that the upcoming Magic Keyboards are fully compatible with those models. Keep your 2018 iPad Pro and wait for the keyboard.</p>
  964. <p>If you don’t have a 2018 iPad Pro, I can recommend these new iPad Pros with no reservations. <a href="">Everything I wrote about the 2018 iPad Pros still stands</a>. Rumors abound that Apple might release a more significant iPad Pro update at the end of the year, <a href="">perhaps only in the 12.9-inch size</a>. If you want to wait, wait, but waiting for rumored future products is a good way to tie yourself in knots and wind up waiting forever. If you need a new iPad now, these are the best iPads Apple has ever made, and arguably the best portable computers Apple has ever made, period.</p>
  966. <div class="footnotes">
  967. <hr />
  968. <ol>
  969. <li id="fn1-2020-03-24">
  970. <p>That keyboard is a <a href="">Keychron K2</a> with Gateron brown switches. I like it, but the Gateron switches are nowhere near as nice as the ones from Cherry. They feel a little cheap.&nbsp;<a href="#fnr1-2020-03-24"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  971. </li>
  972. </ol>
  973. </div>
  977.    ]]></content>
  978.  <title>★ The 2020 iPad Pros</title></entry><entry>
  979. <title>Convergence on the Laptop Form Factor</title>
  980. <link rel="alternate" type="text/html" href="" />
  981. <link rel="shorturl" type="text/html" href="" />
  982. <link rel="related" type="text/html" href="" />
  983. <id>,2020:/linked//6.36605</id>
  984. <published>2020-03-24T00:59:11Z</published>
  985. <updated>2020-03-24T01:02:55Z</updated>
  986. <author>
  987. <name>John Gruber</name>
  988. <uri></uri>
  989. </author>
  990. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  991. <p>Nick Heer, responding to arguments that, with the upcoming Magic Keyboard, Apple is moving the iPad in the direction of Microsoft’s Surface lineup:</p>
  993. <blockquote>
  994.  <p>I’m going to irritatingly self-quote here from a piece <a href="">I wrote a
  995. couple of years ago</a>:</p>
  997. <blockquote>
  998.  <p>If there is a smartphone-to-desktop continuum, with the tablet
  999. somewhere in the middle, Microsoft has long approached it as
  1000. skinning Windows with touch drivers and bigger buttons, while
  1001. Apple chose to start by making a touchscreen phone and build up
  1002. from there.</p>
  1003. </blockquote>
  1005. <p>The addition of real mouse and trackpad support to the iPad is not
  1006. just a slapped-on version of the MacOS cursor, but a clearly
  1007. considered rethinking of what that should be on a system that is
  1008. still primarily used by touch. I expect to see plenty more changes
  1009. like this as Apple continues to add more advanced features to
  1010. iPadOS — features that will probably be similar to aspects of
  1011. MacOS, but reconsidered for a touch-based operating system.</p>
  1012. </blockquote>
  1014. <p>See also: Tom Warren’s take for The Verge: “<a href="">Apple Finally Admits Microsoft Was Right About Tablets</a>”, which is a borderline jacktastic headline.</p>
  1016. <p>I think Heer gets this right. It’s not about iPad moving closer to Surface conceptually; it’s about moving closer to the laptop ideal. For certain tasks nothing beats the laptop form factor, and quite possibly never will. All computing platforms that are used for such tasks inevitably take on that form. What’s new this decade is the detachable 2-in-1 form — one device that serves as both a laptop with keyboard and trackpad <em>and</em> as a handheld tablet. Microsoft got there from one direction, Apple from another.</p>
  1018. <div>
  1019. <a  title="Permanent link to ‘Convergence on the Laptop Form Factor’"  href="">&nbsp;★&nbsp;</a>
  1020. </div>
  1022. ]]></content>
  1023.  </entry><entry>
  1024. <title>Facebook Donates Emergency Reserve of 720,000 Masks to Health Workers</title>
  1025. <link rel="alternate" type="text/html" href="" />
  1026. <link rel="shorturl" type="text/html" href="" />
  1027. <link rel="related" type="text/html" href="" />
  1028. <id>,2020:/linked//6.36603</id>
  1029. <published>2020-03-23T22:35:55Z</published>
  1030. <updated>2020-03-23T22:37:34Z</updated>
  1031. <author>
  1032. <name>John Gruber</name>
  1033. <uri></uri>
  1034. </author>
  1035. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1036. <p>Reuters:</p>
  1038. <blockquote>
  1039.  <p>Chief Executive Mark Zuckerberg said on Sunday that the social media company has donated its emergency reserve of 720,000 masks to provide health workers with more protective gear. “To help, Facebook donated our emergency reserve of 720,000 masks that we had bought in case the wildfires continued,” Zuckerberg said in a post, adding that the company is also working on “sourcing a lot more to donate.”</p>
  1040. </blockquote>
  1042. <p>Next up: Zuckerberg donates his emergency stash of do-it-yourself haircut kits.</p>
  1044. <div>
  1045. <a  title="Permanent link to ‘Facebook Donates Emergency Reserve of 720,000 Masks to Health Workers’"  href="">&nbsp;★&nbsp;</a>
  1046. </div>
  1048. ]]></content>
  1049.  </entry><entry>
  1050. <link rel="alternate" type="text/html" href="" />
  1051. <link rel="shorturl" href="" />
  1052. <link rel="related" type="text/html" href="" />
  1053. <id>,2020:/feeds/sponsors//11.36604</id>
  1054. <author><name>Daring Fireball Department of Commerce</name></author>
  1055. <published>2020-03-23T20:40:09-05:00</published>
  1056. <updated>2020-03-28T21:09:10-05:00</updated>
  1057. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1058. <p>NextDraft is a quick, entertaining look at the day’s biggest and best stories, from the top of the news to the very bottom. Written by Dave Pell, a news junkie’s news junkie, NextDraft is smart and funny.</p>
  1060. <p>In normal times, NextDraft is a once-per-weekday newsletter, delivered either by email or <a href="">a very nice iOS app</a>. These are not normal times, and while the coronavirus crisis continues, NextDraft has gone to a 7-days-a-week schedule.</p>
  1062. <p>The once-a-day pace keeps you up to date on the news, but keeps you from being pestered by frequent emails or notifications. NextDraft is not about breaking news — it’s just a carefully curated and cleverly written daily update. You like email? Sign up for the newsletter. Hate email? <a href="">Get the app</a>.</p>
  1064. <p>Here’s the kicker: NextDraft is free of charge. There is no catch.</p>
  1066. <div>
  1067. <a  title="Permanent link to ‘NextDraft’"  href="">&nbsp;★&nbsp;</a>
  1068. </div>
  1070. ]]></content>
  1071. <title>[Sponsor] NextDraft</title></entry><entry>
  1072. <title>Inside the Xbox Series X</title>
  1073. <link rel="alternate" type="text/html" href="" />
  1074. <link rel="shorturl" type="text/html" href="" />
  1075. <link rel="related" type="text/html" href="" />
  1076. <id>,2020:/linked//6.36602</id>
  1077. <published>2020-03-23T20:15:49Z</published>
  1078. <updated>2020-03-23T23:20:15Z</updated>
  1079. <author>
  1080. <name>John Gruber</name>
  1081. <uri></uri>
  1082. </author>
  1083. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1084. <p>I’m not into the whole Xbox-PlayStation console scene, but I found this detailed look at the internals of the upcoming Xbox Series X from Austin Evans to be fascinating. The only thing I found surprising is that it’s still going to contain an optical drive. It takes up so much space.</p>
  1086. <p><strong>Update:</strong> I totally get the practical reasons for including the optical drive — compatibility with older Xbox games (going back several generations — very Microsoftian), helpful for people without fast broadband connections (modern games are huge), reselling games and buying used ones. I get it. Just saying that as an outsider, it looks archaic, especially amidst how cutting-edge the rest of the hardware is architecturally.</p>
  1088. <div>
  1089. <a  title="Permanent link to ‘Inside the Xbox Series X’"  href="">&nbsp;★&nbsp;</a>
  1090. </div>
  1092. ]]></content>
  1093.  </entry><entry>
  1094. <title>Foxconn Gives a Thumbs-Up</title>
  1095. <link rel="alternate" type="text/html" href="" />
  1096. <link rel="shorturl" type="text/html" href="" />
  1097. <link rel="related" type="text/html" href="" />
  1098. <id>,2020:/linked//6.36601</id>
  1099. <published>2020-03-23T18:39:47Z</published>
  1100. <updated>2020-03-23T18:43:39Z</updated>
  1101. <author>
  1102. <name>John Gruber</name>
  1103. <uri></uri>
  1104. </author>
  1105. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1106. <p>Nikkei Asian Review:</p>
  1108. <blockquote>
  1109.  <p>Taiwan’s Foxconn, the top assembler of Apple’s iPhones, said it has secured enough workers to meet “seasonal demand” at all major Chinese plants, stressing a steady recovery from the labor shortage caused by the novel coronavirus epidemic on the mainland. The company issued a statement Sunday night saying recruitment goals have been reached “ahead of schedule at the plants.” This signals progress from early March when Chairman Young Liu told investors that Chinese plants were operating at roughly 50% capacity of normal.</p>
  1111. <p>The company also stressed that it has instituted rigorous measures to prevent infection. A total of 55,000 workers received PCR coronavirus tests, and over 40,000 people underwent chest X-rays, according to Foxconn.</p>
  1112. </blockquote>
  1114. <p>I don’t know whether this is good news or terrifying.</p>
  1116. <div>
  1117. <a  title="Permanent link to ‘Foxconn Gives a Thumbs-Up’"  href="">&nbsp;★&nbsp;</a>
  1118. </div>
  1120. ]]></content>
  1121.  </entry><entry>
  1122. <title>Yes Plz Coffee</title>
  1123. <link rel="alternate" type="text/html" href=";utm_source=rss&amp;utm_medium=referral&amp;utm_campaign=daringfireball" />
  1124. <link rel="shorturl" type="text/html" href="" />
  1125. <link rel="related" type="text/html" href="" />
  1126. <id>,2020:/linked//6.36600</id>
  1127. <published>2020-03-22T19:28:11Z</published>
  1128. <updated>2020-03-22T19:32:11Z</updated>
  1129. <author>
  1130. <name>John Gruber</name>
  1131. <uri></uri>
  1132. </author>
  1133. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1134. <p>My thanks to Yes Plz for sponsoring this past week at DF. Yes Plz sends outstanding coffee beans right to your door, along with a delightfully eclectic print zine — that’s right, a printed zine — covering topics like food, culture, and music.</p>
  1136. <p>As I wrote in <a href="">my thank-you post last week</a>, I <em>love</em> Yes Plz coffee. I’d recommend it wholeheartedly even if they weren’t sponsoring the site. It’s delicious. Last week, I wrote that I was drinking Yes Plz coffee while I posted. I can’t say that this week, because I drank it all. I’m out — waiting for a delivery of new beans that was sent yesterday. (You get a notice when a new batch is on its way.) Luckily, Yes Plz just added a new option for a larger bag of beans — I upgraded immediately. I make a lot of coffee at home in normal times; for the foreseeable future, I’ll be making <em>all</em> my coffee at home.</p>
  1138. <p>To that point — I checked with my old pal and Yes Plz honcho Tonx Konecny regarding how they’re holding up right now, and if it was OK to keep sending them new subscribers. Tonx’s reply:</p>
  1140. <blockquote>
  1141.  <p>Yes! We’re well stocked on raw materials, our small team and all
  1142. of our production is isolated, and USPS is still going strong so
  1143. we’re confident we’ll be able to stay fully operational.</p>
  1144. </blockquote>
  1146. <p>World-class coffee delivered right to your door, on a schedule you control. That’s Yes Plz. Just what the doctor ordered in these stay-at-home times. Try it now — no hassle, no commitment, and you can pause or cancel anytime. They even have a special deal for DF readers: $5 off your first bag using promo code <strong>FIREBALL5</strong> at checkout.</p>
  1148. <div>
  1149. <a  title="Permanent link to ‘Yes Plz Coffee’"  href="">&nbsp;★&nbsp;</a>
  1150. </div>
  1152. ]]></content>
  1153.  </entry><entry>
  1154. <title>Anker’s $10 USB‑C to USB‑A Adapter</title>
  1155. <link rel="alternate" type="text/html" href="" />
  1156. <link rel="shorturl" type="text/html" href="" />
  1157. <link rel="related" type="text/html" href="" />
  1158. <id>,2020:/linked//6.36599</id>
  1159. <published>2020-03-22T18:19:35Z</published>
  1160. <updated>2020-03-23T18:54:55Z</updated>
  1161. <author>
  1162. <name>John Gruber</name>
  1163. <uri></uri>
  1164. </author>
  1165. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1166. <p>If you <a href="">do need</a> a USB‑C to USB‑A adapter, my favorite is this one from Anker. It’s small and comes pretty close to color-matching Apple’s space gray aluminum. When you plug it in it has a nice snap. I bought a few a while back — I keep two at my desk and two in my travel bag. The only thing I don’t like about it is the prominent Anker logo, but because it’s USB‑C, I just plug it in logo side down to hide it. (Disclosure: I’m back on the Amazon affiliate gravy train; buying through this link will send a small percentage my way.)</p>
  1168. <div>
  1169. <a  title="Permanent link to ‘Anker’s $10 USB‑C to USB‑A Adapter’"  href="">&nbsp;★&nbsp;</a>
  1170. </div>
  1172. ]]></content>
  1173.  </entry><entry>
  1174. <title>USB‑A on the MacBook Air Wishlist?</title>
  1175. <link rel="alternate" type="text/html" href="" />
  1176. <link rel="shorturl" type="text/html" href="" />
  1177. <link rel="related" type="text/html" href="" />
  1178. <id>,2020:/linked//6.36598</id>
  1179. <published>2020-03-22T16:57:39Z</published>
  1180. <updated>2020-03-23T18:55:26Z</updated>
  1181. <author>
  1182. <name>John Gruber</name>
  1183. <uri></uri>
  1184. </author>
  1185. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1186. <p>Jason Cross, in his MacBook Air review for Macworld:</p>
  1188. <blockquote>
  1189.  <p>Apple is still determined to make every USB port feature a USB‑C
  1190. connector. We’ve been told that the ubiquity of USB‑C devices is
  1191. just around the corner for years now, and it’s still not
  1192. happening. Accessory makers keep cranking out mice, keyboards,
  1193. storage devices, microphones, audio interfaces, and loads of other
  1194. things with USB‑A connectors on them. Putting a single USB‑A port
  1195. on MacBooks would not be a step backwards, it would be recognition
  1196. that in the wide world of USB devices, that interface is still
  1197. widespread, and we shouldn’t need a dongle or dock to use them.</p>
  1198. </blockquote>
  1200. <p>It’s undeniable that the USB‑C revolution has been very slow in coming, but slowly but surely, it is coming along. I wrote in <a href="">my first-look review of the new Air</a> that I wish the MacBook Air had at least one more USB‑C port, on the right side of the machine, but I don’t think a built-in USB‑A port would be appropriate. Is USB‑A still in widespread use? Sure, but at this point USB‑A ports are backward-looking. SD cards remain in widespread use too, and they don’t belong built into the Air either. (MacBook Pros — there I can see the argument for built-in SD slots.)</p>
  1202. <p>Just like with the 1998 iMac going all-in on USB‑A, and the iPhone 7 <a href="">dropping the headphone jack</a>, Apple is helping drive the adoption of USB‑C by dropping USB‑A ports. Adding them back now would set back the whole industry.</p>
  1204. <div>
  1205. <a  title="Permanent link to ‘USB‑A on the MacBook Air Wishlist?’"  href="">&nbsp;★&nbsp;</a>
  1206. </div>
  1208. ]]></content>
  1209.  </entry><entry>
  1210. <title>Watch Gary Hustwit’s Design Documentaries for Free</title>
  1211. <link rel="alternate" type="text/html" href="" />
  1212. <link rel="shorturl" type="text/html" href="" />
  1213. <link rel="related" type="text/html" href="" />
  1214. <id>,2020:/linked//6.36597</id>
  1215. <published>2020-03-22T16:40:11Z</published>
  1216. <updated>2020-03-22T16:42:45Z</updated>
  1217. <author>
  1218. <name>John Gruber</name>
  1219. <uri></uri>
  1220. </author>
  1221. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1222. <p>Oh You Pretty Things:</p>
  1224. <blockquote>
  1225.  <p>Filmmaker Gary Hustwit is streaming his documentaries free worldwide during the global COVID crisis. Each week we’ll be posting another film here. We hope you enjoy them, and please stay strong.</p>
  1227. <p>March 17 to 24: <em>Helvetica</em> — a feature-length documentary about typography, graphic design and global visual culture. It looks at the proliferation of one typeface as part of a larger conversation about the way type affects our lives.</p>
  1228. </blockquote>
  1230. <p>If you haven’t seen <em>Helvetica</em>, or haven’t seen it in a while, it’s just so good.</p>
  1232. <div>
  1233. <a  title="Permanent link to ‘Watch Gary Hustwit’s Design Documentaries for Free’"  href="">&nbsp;★&nbsp;</a>
  1234. </div>
  1236. ]]></content>
  1237.  </entry><entry>
  1238. <title>Google Cancels I/O Entirely</title>
  1239. <link rel="alternate" type="text/html" href="" />
  1240. <link rel="shorturl" type="text/html" href="" />
  1241. <link rel="related" type="text/html" href="" />
  1242. <id>,2020:/linked//6.36596</id>
  1243. <published>2020-03-21T20:32:11Z</published>
  1244. <updated>2020-03-23T02:21:48Z</updated>
  1245. <author>
  1246. <name>John Gruber</name>
  1247. <uri></uri>
  1248. </author>
  1249. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1250. <p>The Google Developers Twitter account:</p>
  1252. <blockquote>
  1253.  <p>A #GoogleIO update: Out of concern for the health and safety of
  1254. our developers, employees, and local communities — and in line
  1255. with “shelter in place” requirements by the local Bay Area
  1256. government — we sadly will not be holding an I/O event in any
  1257. capacity this year.</p>
  1258. </blockquote>
  1260. <p>Makes you wonder about WWDC. I think WWDC will happen online, even if the current “shelter in place” regulations remain in place through June. Will recorded WWDC sessions be harder to produce remotely than they would with Apple employees on site, collaborating together? Of course. But a lot of WWDC sessions have been slides-only with recorded audio — meaning no video of the presenters — for years. Professional quality video is <em>way</em> harder to produce than professional quality audio and slides.</p>
  1262. <p>Also, WWDC is far more important to Apple strategically than I/O is for Google. I don’t think Google, as a whole, really gives much of a shit whether Android developers are taking advantage of the latest and greatest APIs. I’m sure the Android team does, but not Google as a whole. The other annual announcements at I/O are all a bit scattershot. Apple, on the other hand, really does want developers to take advantage of each year’s latest iOS — and to a lesser extent, MacOS, tvOS, and WatchOS — APIs. WWDC is so important to Apple strategically that I think they would go to <em>more</em> effort to pull off an online-only version this year than they do to put together a normal in-person WWDC — and Apple expends a tremendous amount of engineering and design staff time and effort on WWDC in normal years.</p>
  1264. <p>But it’d be foolish, given how much the ground has changed in just the last week, to say today that a complete cancellation of WWDC 2020 is off the table. Nothing is off the table at this point.</p>
  1266. <div>
  1267. <a  title="Permanent link to ‘Google Cancels I/O Entirely’"  href="">&nbsp;★&nbsp;</a>
  1268. </div>
  1270. ]]></content>
  1271.  </entry><entry>
  1272. <title>Three Weeks</title>
  1273. <link rel="alternate" type="text/html" href="" />
  1274. <link rel="shorturl" type="text/html" href="" />
  1275. <link rel="related" type="text/html" href="" />
  1276. <id>,2020:/linked//6.36595</id>
  1277. <published>2020-03-21T17:52:17Z</published>
  1278. <updated>2020-03-23T02:23:06Z</updated>
  1279. <author>
  1280. <name>John Gruber</name>
  1281. <uri></uri>
  1282. </author>
  1283. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1284. <p>Josh Marshall:</p>
  1286. <blockquote>
  1287.  <p>February 26th, 2020. President Trump: “When you have 15 people,
  1288. and the 15 within a couple of days is going to be down to close to
  1289. zero, that’s a pretty good job we’ve done.”</p>
  1291. <p>March 20th, 2020. Confirmed cases in the United States rise
  1292. to 16,064.</p>
  1293. </blockquote>
  1295. <p>It’s not “playing politics” to point this stuff out regarding the Trump administration’s response to COVID-19. It is essential that we, collectively, see that Trump is temperamentally unfit for the office. This was plainly obvious to those of us opposed to him all along. It should now be plainly obvious to anyone whose eyes are open. Three weeks ago he was confidently telling the world the U.S. would soon be “down to close to zero” cases. Instead, here we are with close to zero aspects of daily life that are normal.</p>
  1297. <div>
  1298. <a  title="Permanent link to ‘Three Weeks’"  href="">&nbsp;★&nbsp;</a>
  1299. </div>
  1301. ]]></content>
  1302.  </entry><entry>
  1303. <title>U.S. Intelligence Reports From January and February Warned About a Likely Pandemic</title>
  1304. <link rel="alternate" type="text/html" href="" />
  1305. <link rel="shorturl" type="text/html" href="" />
  1306. <link rel="related" type="text/html" href="" />
  1307. <id>,2020:/linked//6.36594</id>
  1308. <published>2020-03-21T17:25:31Z</published>
  1309. <updated>2020-03-21T17:43:27Z</updated>
  1310. <author>
  1311. <name>John Gruber</name>
  1312. <uri></uri>
  1313. </author>
  1314. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1315. <p>The Washington Post:</p>
  1317. <blockquote>
  1318.  <p>U.S. intelligence agencies were issuing ominous, classified warnings in January and February about the global danger posed by the coronavirus while President Trump and lawmakers played down the threat and failed to take action that might have slowed the spread of the pathogen, according to U.S. officials familiar with spy agency reporting. […]</p>
  1320. <p>Robert Kadlec, the assistant secretary for preparedness and response — who was joined by intelligence officials, including from the CIA — told committee members that the virus posed a “serious” threat, one of those officials said. Kadlec didn’t provide specific recommendations, but he said that to get ahead of the virus and blunt its effects, Americans would need to take actions that could disrupt their daily lives, the official said. “It was very alarming.”</p>
  1322. <p>Trump’s insistence on the contrary seemed to rest in his relationship with China’s President Xi Jingping, whom Trump believed was providing him with reliable information about how the virus was spreading in China, despite reports from intelligence agencies that Chinese officials were not being candid about the true scale of the crisis.</p>
  1323. </blockquote>
  1325. <p>We didn’t have to be here. The story is not complicated — Trump ignored the danger until it was far too late. Why did he take China’s word over that of our own intelligence agencies and experts? Because what China was claiming was what he wanted to hear.</p>
  1327. <div>
  1328. <a  title="Permanent link to ‘U.S. Intelligence Reports From January and February Warned About a Likely Pandemic’"  href="">&nbsp;★&nbsp;</a>
  1329. </div>
  1331. ]]></content>
  1332.  </entry><entry>
  1333. <title>‘Some People’</title>
  1334. <link rel="alternate" type="text/html" href="" />
  1335. <link rel="shorturl" type="text/html" href="" />
  1336. <link rel="related" type="text/html" href="" />
  1337. <id>,2020:/linked//6.36593</id>
  1338. <published>2020-03-21T03:59:00Z</published>
  1339. <updated>2020-03-21T04:05:32Z</updated>
  1340. <author>
  1341. <name>John Gruber</name>
  1342. <uri></uri>
  1343. </author>
  1344. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1345. <p>Some people would like to thank Jason Kottke for writing this.</p>
  1347. <div>
  1348. <a  title="Permanent link to ‘‘Some People’’"  href="">&nbsp;★&nbsp;</a>
  1349. </div>
  1351. ]]></content>
  1352.  </entry><entry>
  1353. <title>The Doctor Who Helped Defeat Smallpox Explains What’s Coming</title>
  1354. <link rel="alternate" type="text/html" href="" />
  1355. <link rel="shorturl" type="text/html" href="" />
  1356. <link rel="related" type="text/html" href="" />
  1357. <id>,2020:/linked//6.36586</id>
  1358. <published>2020-03-21T03:50:00Z</published>
  1359. <updated>2020-03-21T03:50:16Z</updated>
  1360. <author>
  1361. <name>John Gruber</name>
  1362. <uri></uri>
  1363. </author>
  1364. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1365. <p>Absolutely full-stop <em>must-read</em> interview by Steven Levy with Larry Brilliant, the epidemiologist who helped eradicate smallpox:</p>
  1367. <blockquote>
  1368.  <p>Now the unthinkable is here, and Brilliant, the Chairman of the board of Ending Pandemics, is sharing expertise with those on the front lines. We are a long way from 100 million deaths due to the novel coronavirus, but it has turned our world upside down. Brilliant is trying not to say “I told you so” too often. But he did tell us so, not only in talks and writings, but as the senior technical advisor for the pandemic horror film <em><a href="">Contagion</a></em>, now a top streaming selection for the homebound. Besides working with the World Health Organization in the effort to end smallpox, Brilliant, who is now 75, has fought flu, polio, and blindness; once led Google’s nonprofit wing,; co-founded the conferencing system the Well; and has traveled with the Grateful Dead.</p>
  1370. <p>We talked by phone on Tuesday. At the time, President Donald Trump’s response to the crisis <a href="">had started to change</a> from “no worries at all” to finally taking more significant steps to stem the pandemic. Brilliant lives in one of the six Bay Area counties where residents were ordered to shelter in place. When we began the conversation, he’d just gotten off the phone with someone he described as high government official, who asked Brilliant “How the fuck did we get here?” I wanted to hear how we’ll get <em>out</em> of here. The conversation has been edited and condensed.</p>
  1371. </blockquote>
  1373. <p>Read this and you’ll come out the end more informed than if you read 20 other articles on this pandemic. I found this exchange particularly salient, for perspective:</p>
  1375. <blockquote>
  1376.  <p><em>Are you scared?</em></p>
  1378. <p>I’m in the age group that has a one in seven mortality rate if I get it. If you’re not worried, you’re not paying attention. But I’m not scared. I firmly believe that the steps that we’re taking will extend the time that it takes for the virus to make the rounds. I think that, in turn, will increase the likelihood that we will have a vaccine or we will have a prophylactic antiviral in time to cut off, reduce, or truncate the spread. Everybody needs to remember: This is not a zombie apocalypse. It’s not a mass extinction event.</p>
  1379. </blockquote>
  1381. <p>This is not just idle talk; Brilliant has spent his career truly contemplating extinction-event pandemics.</p>
  1383. <div>
  1384. <a  title="Permanent link to ‘The Doctor Who Helped Defeat Smallpox Explains What’s Coming’"  href="">&nbsp;★&nbsp;</a>
  1385. </div>
  1387. ]]></content>
  1388.  </entry><entry>
  1389. <title>Jason Snell’s 2020 MacBook Air Review: ‘No News Is Good News’</title>
  1390. <link rel="alternate" type="text/html" href="" />
  1391. <link rel="shorturl" type="text/html" href="" />
  1392. <link rel="related" type="text/html" href="" />
  1393. <id>,2020:/linked//6.36591</id>
  1394. <published>2020-03-21T02:34:47Z</published>
  1395. <updated>2020-03-21T02:35:42Z</updated>
  1396. <author>
  1397. <name>John Gruber</name>
  1398. <uri></uri>
  1399. </author>
  1400. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1401. <p>Jason Snell, writing at Six Colors:</p>
  1403. <blockquote>
  1404.  <p>If you don’t really need a new Mac laptop, maybe you should wait to see what happens with ARM. But if you’re someone who has been holding out for a new MacBook Air — and ideally one without that infamous keyboard — I wouldn’t recommend that you wait. This is the MacBook Air that you’ve been waiting for.</p>
  1405. </blockquote>
  1407. <div>
  1408. <a  title="Permanent link to ‘Jason Snell’s 2020 MacBook Air Review: ‘No News Is Good News’’"  href="">&nbsp;★&nbsp;</a>
  1409. </div>
  1411. ]]></content>
  1412.  </entry><entry>
  1413. <title>Netflix Creates $100 Million Coronavirus Relief Fund</title>
  1414. <link rel="alternate" type="text/html" href="" />
  1415. <link rel="shorturl" type="text/html" href="" />
  1416. <link rel="related" type="text/html" href="" />
  1417. <id>,2020:/linked//6.36590</id>
  1418. <published>2020-03-21T02:23:34Z</published>
  1419. <updated>2020-03-21T02:26:08Z</updated>
  1420. <author>
  1421. <name>John Gruber</name>
  1422. <uri></uri>
  1423. </author>
  1424. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1425. <p>Brent Lang, reporting for Variety:</p>
  1427. <blockquote>
  1428.  <p>Netflix has created a $100 million relief fund to help members of the creative community who have been left unemployed and without a way to earn an income during the coronavirus crisis. The streaming giant said the bulk of the funds will go toward supporting laid-off crew members.</p>
  1430. <p>“The COVID-19 crisis is devastating for many industries, including the creative community. Almost all television and film production has now ceased globally — leaving hundreds of thousands of crew and cast without jobs,” Netflix’s chief content officer Ted Sarandos said in a statement. “These include electricians, carpenters and drivers, many of whom are paid hourly wages and work on a project-to-project basis. This community has supported Netflix through the good times, and we want to help them through these hard times, especially while governments are still figuring out what economic support they will provide.”</p>
  1431. </blockquote>
  1433. <p>Great move from Netflix. We need more like this from big companies that are well-positioned to financially weather this extended storm.</p>
  1435. <div>
  1436. <a  title="Permanent link to ‘Netflix Creates $100 Million Coronavirus Relief Fund’"  href="">&nbsp;★&nbsp;</a>
  1437. </div>
  1439. ]]></content>
  1440.  </entry><entry>
  1441. <title>Unread 2</title>
  1442. <link rel="alternate" type="text/html" href="" />
  1443. <link rel="shorturl" type="text/html" href="" />
  1444. <link rel="related" type="text/html" href="" />
  1445. <id>,2020:/linked//6.36589</id>
  1446. <published>2020-03-21T01:43:32Z</published>
  1447. <updated>2020-03-21T02:21:30Z</updated>
  1448. <author>
  1449. <name>John Gruber</name>
  1450. <uri></uri>
  1451. </author>
  1452. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1453. <p><a href="">Speaking of</a> iOS feed reader apps, John Brayton’s Unread 2 recently shipped too:</p>
  1455. <blockquote>
  1456.  <p>If you are frustrated by feeds that include only article summaries, you will love Unread 2. Unread 2 takes Unread’s Readability view to the next level.</p>
  1458. <p>Unread 2 automatically determines which feeds contain only article summaries. When displaying articles from such feeds, Unread displays the full article text from the webpage. For any given feed, you can override Unread’s determination of whether to show feed text or webpage text.</p>
  1460. <p>In addition, Unread 2 can cache webpage text ahead of time. This gives you fast offline access to the webpage text and embedded images of such articles.</p>
  1461. </blockquote>
  1463. <p>Unread is gorgeous, and takes an entirely different course than NetNewsWire on how to design a great iOS feed reading app. Unread is focused on eliminating chrome — it is a pure reading app. It’s like reader mode all the time, and the assortment of color themes is nicely curated.</p>
  1465. <p>There’s never been a better time to get back into RSS. My RSS subscriptions are largely about tech and design, and I keep political feeds in their own folder. It’s an oasis apart from general world news.</p>
  1467. <div>
  1468. <a  title="Permanent link to ‘Unread 2’"  href="">&nbsp;★&nbsp;</a>
  1469. </div>
  1471. ]]></content>
  1472.  </entry><entry>
  1473. <title>NetNewsWire 5.0 for iOS</title>
  1474. <link rel="alternate" type="text/html" href="" />
  1475. <link rel="shorturl" type="text/html" href="" />
  1476. <link rel="related" type="text/html" href="" />
  1477. <id>,2020:/linked//6.36588</id>
  1478. <published>2020-03-21T01:34:21Z</published>
  1479. <updated>2020-03-21T01:40:43Z</updated>
  1480. <author>
  1481. <name>John Gruber</name>
  1482. <uri></uri>
  1483. </author>
  1484. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1485. <p>Speaking of Brent Simmons, the reborn NetNewsWire is now out for iOS (both iPhone and iPad):</p>
  1487. <blockquote>
  1488.  <p>It’s free and open source, and it includes support for Feedbin and Feedly syncing.</p>
  1490. <p>Just as the Mac version looks like a Mac app, this is very much an iOS app. It supports Dark Mode, context menus, multiple windows, Siri Shortcuts, and other iOS features.</p>
  1491. </blockquote>
  1493. <p><em>iOS-assed iOS app</em> doesn’t have quite the same ring to it as <em>Mac-assed Mac app</em>, but that’s what NetNewsWire is. <a href="">I raved about NetNewsWire 5 for Mac</a> when it shipped back in August, and I’ll rave equally about NetNewsWire 5 for iOS now. It’s exactly what I want in an RSS reader, and it has changed my daily reading habits significantly.</p>
  1495. <div>
  1496. <a  title="Permanent link to ‘NetNewsWire 5.0 for iOS’"  href="">&nbsp;★&nbsp;</a>
  1497. </div>
  1499. ]]></content>
  1500.  </entry><entry>
  1501. <title>Mac-Assed Mac Apps</title>
  1502. <link rel="alternate" type="text/html" href="" />
  1503. <link rel="shorturl" type="text/html" href="" />
  1504. <link rel="related" type="text/html" href="" />
  1505. <id>,2020:/linked//6.36587</id>
  1506. <published>2020-03-21T01:24:22Z</published>
  1507. <updated>2020-03-21T01:33:52Z</updated>
  1508. <author>
  1509. <name>John Gruber</name>
  1510. <uri></uri>
  1511. </author>
  1512. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1513. <p>Brent Simmons:</p>
  1515. <blockquote>
  1516.  <p>A few people have asked me, “What’s a Mac-assed Mac app?”</p>
  1518. <p>Answer: it’s a phrase I stole from my friend <a href="">Collin Donnell</a> to describe Mac apps that are unapologetically <em>Mac</em> apps. They’re platform-specific and they’re not trying to wow us with all their custom not-Mac-like UI (which often isn’t very accessible).</p>
  1520. <p>I consider NetNewsWire to be a Mac-assed Mac app, and it’s a point of pride.</p>
  1522. <p>Slack, on the other hand, is most definitely not — though it’s not only Electron apps that miss the mark of Mac-assed-Mac-app-ness.</p>
  1523. </blockquote>
  1525. <p>I love this term. It’s better and more clear than just saying “native”. Native is ambiguous. Not to pick on Slack, but you can definitely argue that however odd Slack for Mac is UI-wise, it <em>is</em> a “native* app. But it sure as shit is not a Mac-assed Mac app.</p>
  1527. <p>Brent’s post is in the context of <a href="">Proxyman</a>, which I hadn’t heard of. It looks very cool — it’s a Mac-assed Mac alternative to tools like Wireshark or Charles for observing and debugging HTTP/HTTPS requests.</p>
  1529. <div>
  1530. <a  title="Permanent link to ‘Mac-Assed Mac Apps’"  href="">&nbsp;★&nbsp;</a>
  1531. </div>
  1533. ]]></content>
  1534.  </entry><entry>
  1535. <link rel="alternate" type="text/html" href=";utm_source=rss&amp;utm_medium=referral&amp;utm_campaign=daringfireball" />
  1536. <link rel="shorturl" href="" />
  1537. <link rel="related" type="text/html" href="" />
  1538. <id>,2020:/feeds/sponsors//11.36592</id>
  1539. <author><name>Daring Fireball Department of Commerce</name></author>
  1540. <published>2020-03-20T23:36:37-05:00</published>
  1541. <updated>2020-03-20T23:36:38-05:00</updated>
  1542. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1543. <p>The best cup of coffee you ever drink will be one you make in your own kitchen — and it’s easy and fun. Yes Plz sends the very best beans to your door alongside a weirdly eclectic print zine covering topics like food, culture, and music. From the same crazy bean-geniuses who brought you Tonx Coffee back in the day. Try it now — no-hassle, no commitment, pause or cancel anytime. We’re giving DF readers $5 off their first bag using promo code FIREBALL5 at checkout.</p>
  1545. <div>
  1546. <a  title="Permanent link to ‘YES PLZ — the Best Coffee in Your Kitchen’"  href="">&nbsp;★&nbsp;</a>
  1547. </div>
  1549. ]]></content>
  1550. <title>[Sponsor] YES PLZ — the Best Coffee in Your Kitchen</title></entry><entry>
  1552.    <link rel="alternate" type="text/html" href="" />
  1553. <link rel="shorturl" href="" />
  1554. <id>,2020://1.36585</id>
  1555. <published>2020-03-20T16:23:46Z</published>
  1556. <updated>2020-03-21T04:37:46Z</updated>
  1557. <author>
  1558. <name>John Gruber</name>
  1559. <uri></uri>
  1560. </author>
  1561. <summary type="text">Faster, cheaper, and now with a truly great keyboard.</summary>
  1562. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1563. <p>We waited a long time for a retina MacBook Air. <a href="">When we finally got it back in November 2018</a>, it was worth waiting for. Smaller, lighter, faster, better speakers, and — finally — a retina display. The MacBook Air has been and remains Apple’s most popular Mac — perhaps by far. When most people think of a “Mac”, what they think of specifically is a 13-inch MacBook Air. It’s the workhorse Mac — the best Mac for most people.</p>
  1565. <p>But that first crack at a retina MacBook Air wasn’t perfect.</p>
  1567. <p>Well, nothing’s perfect. But the retina MacBook Air had a few significant shortcomings:</p>
  1569. <ul>
  1570. <li><p><strong>The keyboard.</strong> Because the retina MacBook Air was so late to
  1571. the modern MacBook era, it debuted with the third-generation
  1572. butterfly-switch keyboard. That third-generation design really
  1573. was much improved over the first two, especially, it seems, in
  1574. terms of reliability. But it’s hard to find people who claim
  1575. those butterfly keyboards are their favorite keyboards. And
  1576. it’s really easy to find people who — reliability issues
  1577. aside — just don’t like the way they feel.</p></li>
  1578. <li><p><strong>Price.</strong> The MacBook Air is supposed to start at $999. It just
  1579. is. But the retina MacBook Air started at $1199. And so Apple
  1580. kept the by-that-time ancient non-retina MacBook Air around for
  1581. a while just to occupy that $999 price point in the lineup. The
  1582. way things should be, you ought not just be able to buy <em>a</em>
  1583. MacBook Air for $999, you ought to be able to buy a <em>good</em>
  1584. MacBook Air for $999.</p></li>
  1585. <li><p><strong>Performance.</strong> Yes, the retina MacBook Air was faster than the
  1586. non-retina MacBook Air models it replaced. But that’s because
  1587. the non-retina MacBook Air models were <em>really</em> old. They were
  1588. embarrassingly old.</p></li>
  1589. </ul>
  1591. <p>With the new 2020 MacBook Air, Apple has pulled a Michael Corleone and settled all family business. I’ve spent the last day testing Apple’s $1,300 mid-range MacBook Air, with the quad-core Intel Core i5 CPU, 512 GB storage, and 8 GB of RAM. My thoughts and observations:</p>
  1593. <h2>Performance</h2>
  1595. <p>I’ve only had this machine for a day, so I don’t have any extensive testing results to report. But it’s solid. One significant difference between this MacBook Air and the previous generation is that it offers CPU options at all. With the previous retina MacBook Air, there was one and only one CPU option. <a href="">From my 2018 first-look review</a>:</p>
  1597. <blockquote>
  1598.  <p>There’s only one CPU option for the new MacBook Air: “1.6GHz
  1599. dual‑core 8th‑generation Intel Core i5 processor, Turbo Boost up
  1600. to 3.6GHz”. There are no build-to-order CPU options. I could be
  1601. wrong, but off the top of my head, I think this is a first for a
  1602. Mac notebook in the Intel era. MacBook Pros have a slew of
  1603. different CPU options. The 12-inch MacBook, surprisingly, has
  1604. three CPU options. Even the base model non-retina MacBook Air has
  1605. two CPU options.</p>
  1607. <p>Why? I hate picking a CPU. Putting cost aside, I never know what
  1608. the right balance is between performance and battery life. These
  1609. are the sort of decisions I want Apple to make. That’s what they
  1610. do with iPhones and iPads.</p>
  1612. <p>When you order a new MacBook Air, the only choices you make (other
  1613. than color) are how much storage you want and how much RAM (8 or
  1614. 16 GB). That’s it, and that’s how it should be.</p>
  1615. </blockquote>
  1617. <p>Well, now we’re back to CPU options. I can’t say I love that, but the lineup doesn’t seem that confusing to me. The difference between the dual-core Core i3 and quad-core Core i5 seems pretty obvious: $300 will get you <em>much</em> better multithreaded performance. Unclear to me is whether the Core i7 is worth an additional $150. (And if you want quad-core multithreaded performance but are OK with just 256 GB of storage, you can upgrade the base model to the quad-core i5 for just $100 as a build-to-order configuration.)</p>
  1619. <p>With all the usual caveats that artificial benchmarks aren’t accurate indicators of real-world performance, here are some interesting numbers from Geekbench 5 (average of two runs, single-core / multi-core):</p>
  1621. <!-- Markdown Table
  1622. |                                       | Single |  Multi |
  1623. |---------------------------------------|-------:|-------:|
  1624. | MacBook Air 2020 (4-core Core i5)     |  1,127 |  2,854 |
  1625. | MacBook Air 2018 (2-core Core i5)     |    639 |  1,379 |
  1626. | 16″ MacBook Pro 2019 (8-core Core i9) |  1,263 |  7,277 |
  1627. | 13″ MacBook Pro 2014 (2-core Core i7) |    733 |  1,791 |
  1628. | 11″ iPad Pro 2018 (8-core A12X)       |  1,118 |  4,477 |
  1629. | iPhone 11 Pro (6-core A13)            |  1,321 |  3,387 |
  1630. -->
  1632. <table>
  1633. <thead>
  1634. <tr>
  1635.  <th></th>
  1636.  <th align="right">Single</th>
  1637.  <th align="right">Multi</th>
  1638. </tr>
  1639. </thead>
  1640. <tbody>
  1641. <tr>
  1642.  <td>MacBook Air 2020 (4-core Core i5)</td>
  1643.  <td align="right">1,127</td>
  1644.  <td align="right">2,854</td>
  1645. </tr>
  1646. <tr>
  1647.  <td>MacBook Air 2018 (2-core Core i5)</td>
  1648.  <td align="right">639</td>
  1649.  <td align="right">1,379</td>
  1650. </tr>
  1651. <tr>
  1652.  <td>16″ MacBook Pro 2019 (8-core Core i9)</td>
  1653.  <td align="right">1,263</td>
  1654.  <td align="right">7,277</td>
  1655. </tr>
  1656. <tr>
  1657.  <td>13″ MacBook Pro 2014 (2-core Core i7)</td>
  1658.  <td align="right">733</td>
  1659.  <td align="right">1,791</td>
  1660. </tr>
  1661. <tr>
  1662.  <td>11″ iPad Pro 2018 (8-core A12X)</td>
  1663.  <td align="right">1,118</td>
  1664.  <td align="right">4,477</td>
  1665. </tr>
  1666. <tr>
  1667.  <td>iPhone 11 Pro (6-core A13)</td>
  1668.  <td align="right">1,321</td>
  1669.  <td align="right">3,387</td>
  1670. </tr>
  1671. </tbody>
  1672. </table>
  1674. <p>I’d wager heavily that in terms of performance-per-watt, Intel remains hopelessly behind ARM, but in terms of sheer CPU performance — especially single-core, which is what matters most for a lot of day-to-day stuff like using the web — this 10th-generation Core i5 is more than holding its own. Previously the MacBook Air was hit by a double whammy: it was slower <em>and</em> less power efficient. Now it’s just less efficient. Not bad for Intel.</p>
  1676. <p>What’s important, I think, is that it’s a <em>good/faster/fastest</em> lineup — not <em>meh/good/faster</em>.</p>
  1678. <h2>Price</h2>
  1680. <p>The new MacBook Air starts at $999, and that base model is a terrific computer for a lot of people. For a long time, it was hard to recommend Apple’s base model MacBook Air. No longer — especially because it now ships with 256 GB of SSD storage (up from 128).</p>
  1682. <p>As I pointed out in <a href="">my initial thoughts on this week’s new products</a>, until this week, if you wanted a MacBook Air with 256 GB of storage, it cost $1,300. Now, you can get that for $1,000 (and education customers only pay $900). That’s a big price drop — and you get a faster computer and a better keyboard to boot.</p>
  1684. <h2>Keyboard</h2>
  1686. <p>Surprising exactly no one, the keyboard in the new MacBook Air uses the same new scissor switches introduced back in November’s 16-inch MacBook Pro. (The new Magic Keyboard for iPad Pro, coming in May, does too.)</p>
  1688. <p>I love it.</p>
  1690. <p>If anything, it feels a little <em>better</em> than the 16-inch MacBook Pro keyboard. It has the same 1 mm key travel, very similar clickiness, but it maybe feels a little softer, in a good way. Or maybe it just <em>sounds</em> softer. This might not be the keyboard itself but rather a result of the very different case sizes. Compared to the third-generation butterfly switch keyboard in the previous MacBook Air, it feels downright luxurious. To my taste, this conclusively proves that less than 1 mm travel is too little travel.</p>
  1692. <p>The bottom line: Apple is once again making excellent, world-class, no-caveat MacBook keyboards, so <em>something</em>, however insignificant in the grand scheme of life, is right in the world.</p>
  1694. <p>Also, I remain a huge fan of the Force Touch trackpad. The 13-inch MacBook Air is (duh) a smaller device than the 16-inch MacBook Pro, and it has a correspondingly smaller trackpad. But even after months of using a 16-inch MacBook Pro day-in and day-out, this trackpad doesn’t feel too small at all. Again, if anything, it feels better to me.</p>
  1696. <h2>Delightfully Close to Perfection</h2>
  1698. <p>The things that haven’t changed with the MacBook Air — size, weight, display — didn’t need to change. They were already great. The things that have changed — price, performance, and for me personally, especially the keyboard — have all changed significantly for the better. These new MacBook Airs are a <em>lot</em> cheaper, performance is appreciably improved for both CPU and graphics, and the keyboard has gone from “<em>well, it’s OK</em>” to “<em>damn, this keyboard feels so good it makes me</em> want <em>to write something</em>”.</p>
  1700. <p>I mean, really, what would you change? Serious question.</p>
  1702. <p>I do wish there were at least one USB-C port on the right, just to make it more convenient when the nearest power outlet is on that side. But, come on, it’s not that big a deal to snake the cable around the back of a notebook this small.</p>
  1704. <p>An option to get a Touch Bar? I’ve lost count of the number of MacBook Pro owners I know, or whose opinions I’ve simply read, who wish they could buy a new MacBook Pro with good old-fashioned function keys <em>instead of</em> a Touch Bar — not because they want to save a few hundred dollars or because they particularly like function keys, but because they outright dislike the Touch Bar. Conversely, I’ve never met anyone who wishes that the MacBook Air had the Touch Bar. Me, personally, I’m ambivalent — I don’t dislike the Touch Bar, and in fact I like it in several ways, but I can’t say I miss it at all after a full day using this keyboard without one. Not one bit.</p>
  1706. <p>The speakers on this MacBook Air are great compared to Airs of old, but they pale in comparison to the rather amazing sound that comes out of a 16-inch MacBook Pro. But I’m not even sure that sound like that is possible out of a notebook as small as the Air. Compared to any other 13-inch notebook I’ve heard, these speakers are good.</p>
  1708. <p>The camera stinks, especially in low light. There’s no other way to put it. But it’s the same crummy “720p FaceTime Camera” as in all the other MacBooks. You can buy a $3,000 16-inch MacBook Pro and you’ll get the exact same camera. I think this is largely a factor of just how thin the lids are on MacBooks. Is there room for a camera with better optics and a bigger sensor?</p>
  1710. <p>So what’s left? For what it is meant to be, it’s really hard to complain about anything at all regarding this machine. Now that Apple has extricated itself from its butterfly keyboard thicket, it’s clear that Apple was onto something with this design language, which debuted with the no-adjective 12-inch MacBook in 2015.</p>
  1712. <p>Don’t overthink it. The new MacBook Air is what it looks like: nearly perfect.</p>
  1716.    ]]></content>
  1717.  <title>★ The 2020 MacBook Air</title></entry><entry>
  1719.    <link rel="alternate" type="text/html" href="" />
  1720. <link rel="shorturl" href="" />
  1721. <id>,2020://1.36578</id>
  1722. <published>2020-03-18T23:45:18Z</published>
  1723. <updated>2020-03-19T06:59:16Z</updated>
  1724. <author>
  1725. <name>John Gruber</name>
  1726. <uri></uri>
  1727. </author>
  1728. <summary type="text">New iPad Pros and MacBook Air, mouse pointer support in iPadOS 13.4, and the new Magic Keyboard with integrated trackpad for iPad Pros.</summary>
  1729. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1730. <p>Big news drop today from Apple. Long story short:</p>
  1732. <ul>
  1733. <li><a href="">New iPad Pros</a>. Same sizes and shapes (11 and 12.9 inches), faster CPUs and GPUs.</li>
  1734. <li>iPadOS 13.4 — coming this Tuesday — will include full system-wide pointer support for mice and trackpads.</li>
  1735. <li>A new $299 Magic Keyboard folio case for iPad Pros with an integrated trackpad and backlit keys.</li>
  1736. <li>New MacBook Air. Storage has doubled, performance is much improved, and prices have dropped significantly.</li>
  1737. </ul>
  1739. <p>Long story longer:</p>
  1741. <h2>Mouse and Trackpad Pointer Support in iPadOS 13.4</h2>
  1743. <p>Above and beyond any of the hardware announcements, this is the most exciting news of the day for me. First, this is <em>not</em> the sort of feature one expects Apple to drop in a late-in-the-annual-cycle mid-March OS update. Clues suggesting serious mouse pointer support in iOS were gleaned from some sort of leak of iOS 14 (I presume, <a href="">from the way 9to5 Mac has written about it</a>, a device running an early build of iOS 14) but no one had any inkling this was coming <em>now</em>. (Steven Troughton-Smith came closest, <a href="">with this prescient tweet</a> yesterday.)</p>
  1745. <p>This mouse pointer support is rich and deep — it is <em>far</em> more than a simplistic virtual finger tip, and far more thoughtful and graceful and direct than a port to iOS of Mac-style mouse cursors.</p>
  1747. <p>First, when just mousing around, the main cursor is a circle instead of an arrow. A circle feels right; an arrow would definitely feel wrong. Similarly, it would feel all wrong for the Mac to change its primary cursor from the arrow to a circle. For me it boils down to the <em>je ne sais quoi</em> of the fundamental differences between iPad and Mac.</p>
  1749. <p>When you hover over a tappable button, the pointer disappears and instead you get a hover-state highlight around the button. Hover over an app icon in the Dock or on your homescreen, and instead of seeing the mouse pointer on top of the icon, you see a highlight around the icon, much like the way icons are popped on tvOS. When text editing, the cursor changes to an I-beam, of course, but it’s an all-new I-beam cursor, not the one you get in iOS while using the on-screen keyboard as a virtual trackpad (after a tap-and-hold on the spacebar or two-finger tap-and-drag on the key area). This new I-beam cursor is smart. It adjusts to the size of the text you’re editing — if you’re editing 16-point text you’ll get a smaller cursor; if you’re editing 48-point text you’ll get a larger cursor. (Lo these 35+ years after the original Macintosh, it suddenly strikes me as a bit silly that the I-beam cursor stays small even when editing very large text.) The new iPadOS I-beam cursor also is aware of where lines are in text fields, and “snaps” to the line.</p>
  1751. <p>These effects — hover states and size-appropriate I-beam cursor — should just work for existing iPad apps using standard UIKit controls. New APIs are rolling out now for developers who want to take additional advantage of mouse and trackpad support (like, say, if their apps use non-standard text layout engines).</p>
  1753. <p>These features are not exclusive to the new Magic Keyboard’s trackpad. iPadOS 13.4 <a href="">lets you use these features</a> with any iPad, using any (or almost any — I’m sure there are some weird exceptions) Bluetooth or USB mouse or trackpad, including Apple’s Magic Trackpad and Magic Mouse. It’s coming to everyone this coming Tuesday, March 24, and a new beta for developers was released earlier today.</p>
  1755. <h2>Magic Keyboard for iPad Pro</h2>
  1757. <p>This thing looks amazing. Real keys (with backlighting). It floats the iPad above the keyboard surface. You can <a href="">apparently</a> tear off the iPad from the keyboard with a single hand. And there’s no kickstand. It’s strong enough to hold the iPad Pro in place, adjustable to any angle from 90° to 130° — a significant range of motion.</p>
  1759. <p>Basically, this makes a “docked” iPad Pro a true clamshell laptop. It’s still going to be very top-heavy compared to a pure laptop, but that’s inherently true for any dockable tablet. On a pure laptop, the top part is <em>only</em> a display, and the display surface is lightweight plastic, not glass. On a tablet, the whole “computer” is in the top part, and the display is (relatively) heavy glass.</p>
  1761. <p>Apple’s Smart Keyboard covers have been… fine. But they’ve clearly been — if not afterthoughts, per se — at least sorta kinda on the afterthought spectrum. They seemed designed only for <em>typing</em>, and yet for typing alone, weren’t that great because they use those fabric-covered squishy keys. One of Apple’s decade-old arguments against touchscreen Macs is about the ergonomics of reaching up and out to touch a vertical or near-vertical display. And they’re right — it <em>is</em> uncomfortable to poke at a vertical display for more than a few seconds. But without a trackpad (and, of course, without trackpad support in the OS) that is the only way to do many things on an iPad in a Smart Keyboard. Clamoring for touchscreen support on Macs is unlikely ever to stop, but I feel strongly that iPads <em>needed</em> trackpad support — both for ergonomic comfort and for precision. Touchscreen support for Macs is, at best, a nice-to-have idea. (And if you ask me, it’s a feature that only <em>sounds</em> good.)</p>
  1763. <p>Apple’s Smart Keyboard covers have always been very limited in terms of viewing angles. The current ones have two slots; the older ones had just one angle. A proper laptop, of course, uses a hinge, with a range of motion that lets you adjust the display angle until it’s <em>just right</em> for you.</p>
  1765. <p>Put another way, with its Smart Keyboard covers, it has never seemed like Apple was even <em>trying</em> to be in the game for the best way to turn a tablet into a laptop form factor. With this new Magic Keyboard, if it works as well as it looks like it does, Apple quite possibly has jumped to the head of the pack. This is a setup that someone might consider even if they are primarily looking for a laptop, not a tablet. It turns it into a matter of OS preference, not form factor.</p>
  1767. <p>Magic is better than smart, at least when it comes to iPad keyboard covers.</p>
  1769. <p>There is no aspect of today’s product announcements that more makes me wish it had been feasible for in-person briefings and hands-on time than the hinge on the Magic Keyboard.<sup id="fnr1-2020-03-18"><a href="#fn1-2020-03-18">1</a></sup> It simply looks too good to be true that it’s strong enough to suspend the iPad Pro above the keyboard without flopping. Real keys, a real trackpad, no kickstand. It even has its own USB-C port to charge your connected iPad Pro via the Smart Connector, freeing the iPad’s own USB-C port for peripherals. It’s the first attempt from Apple at a way to use an iOS device <em>primarily</em> as a laptop. Talking to Apple about it, they claim the hinge and magnetic connection are more than sturdy enough to actually use it on your lap. </p>
  1771. <p>There’s no special name for the one and only color option, but judging from photos (<a href="">and AR</a>) it’s a very cool near-black. It makes me wish they’d switch the dark option for MacBooks from “space gray” to this near-black color — if you’re going to offer a darker option, go a lot darker. They’ve even added an Apple logo to the back — oriented for landscape. Put an iPad Pro in this case and it’s a laptop.</p>
  1773. <p>The only downsides: the Magic Keyboards are not available until “May”, and they cost $300/350 respectively for the 11/12.9-inch iPad Pros. That’s not cheap, but these don’t look cheap. And a bonus: they’re fully compatible with the previous generation 11- and 12.9-inch iPads Pros, including the camera cutouts on the back.</p>
  1775. <hr />
  1777. <p>As an addendum to this section, I’ll also point out that Apple has collaborated with Logitech on a <a href="">$150 Combo Touch Keyboard Case</a> for the current (7th generation) 10.2-inch iPad and the 10.5-inch iPad Air (which also works with the 10.5-inch iPad Pro). It features both a trackpad and backlit keys, but it requires putting the iPad into a case and settles on a kickstand for support.</p>
  1779. <p>The Logitech keyboard features a row of function keys, for things like home, brightness, volume, and media playback; Apple’s Magic Keyboard does not. Neither keyboard features an Escape key.<sup id="fnr2-2020-03-18"><a href="#fn2-2020-03-18">2</a></sup></p>
  1781. <h2>New iPad Pros</h2>
  1783. <p>Other than the cameras, from the outside these look identical to the previous generation. (As noted above, the previous generation models are compatible with the new Magic Keyboard.) On the inside, the highlights of what’s new include:</p>
  1785. <ul>
  1786. <li>Faster CPU and graphics performance with the A12Z chip. (Why A12<em>Z</em> instead of A12<em>X</em>? Because they needed a letter “better than X”. Not sure what they’ll do next time, though, since Z is the end of the alphabet. And as I’ve long held, no letter in the alphabet is <em>cooler</em> than X.)</li>
  1787. <li>Dual lens rear-facing camera system with wide and ultra-wide lenses.</li>
  1788. <li>A <a href="">LiDAR</a> sensor in the camera system — a first for Apple.</li>
  1789. <li>A five-microphone “studio quality” microphone array based on the same technology as the excellent microphone array introduced with <a href="">November’s 16-inch MacBook Pro</a>.</li>
  1790. </ul>
  1792. <p>This is a solid update. I don’t think it’s enough to tempt most owners of the previous generation iPad Pros, but for a single generation, just about everything that could be faster is faster. In addition to CPU and GPU, that includes Wi-Fi (support for 802.11ax) and the latest and greatest LTE bands. The A12Z (I almost typed X, dammit) is now an 8-core design.</p>
  1794. <p>Prices are unchanged, starting at $800 for the 11-inch and $1,000 for the 12.9-inch. Entry model storage is now 128 GB, up from 64 GB. The largest storage option is 1 TB, which carries a $500 premium. Cellular connectivity remains a $150 upgrade.</p>
  1796. <p>The LiDAR sensor is — at least for now — specifically for AR. (I say “at least for now” because it seems possible to me that, come iOS 14, the LiDAR sensor could also be used as an aid for still photography and video.) LiDAR should make AR <em>much</em> faster on these new iPad Pros than other iOS devices — specifically when you first start and ARKit is mapping your environment.</p>
  1798. <p>One curious omission: Portrait mode photography is only available with the selfie camera. I call this curious because the combination wide/ultra-wide rear-facing camera system is seemingly <em>very</em> similar to that of the iPhone 11, which offers Portrait mode. (And again, Portrait mode in particular is a feature that could, in theory, make great use of a LiDAR sensor — the <em>whole point</em> of LiDAR is to create a depth map. A LiDAR-aided Portrait mode could come a <em>lot</em> closer to DSLR-quality bokeh, blurring background elements based on how far away they are from the lens.)</p>
  1800. <h2>New MacBook Air</h2>
  1802. <p>Last but absolutely not least. This is truly the MacBook Air we’ve been waiting for. Changes from the previous generation:</p>
  1804. <ul>
  1805. <li>Much better base model performance.</li>
  1806. <li>Additional CPU options with even better performance, including quad-core Core i5 and i7 options.</li>
  1807. <li>Increased storage capacity, with the base model now starting at 256 GB.</li>
  1808. <li>The base model starts at $999 — with education pricing starting at $899.</li>
  1809. </ul>
  1811. <p>As a general rule, I tend to round prices up a dollar. E.g. I wrote above that the new 11-inch iPad Pro starts at $800, when in fact it starts at $799. I do this because for me at least, it makes comparison math far more clear. I find the difference between $799 and $1,299 far more difficult to compute at a glance than the difference between $800 and $1,300. But I make an exception here for $999, because I think that’s such a psychologically powerful price point. From a consumer advocate perspective, there’s zero practical difference between $999 and $1,000. But $999 is magic.</p>
  1813. <p>When the retina MacBook Air <a href="">debuted</a>, it didn’t hit that magic price. It started at $1,199, with the old non-retina MacBook Air hanging around in the lineup. And that $1,199 model had only 128 GB of storage.</p>
  1815. <p>Today’s new MacBook Air models are terrific in two regards: they’re noticeably better computers at noticeably lower prices. Before today, a 256 GB retina MacBook Air cost $1,299 and came with a butterfly mechanism keyboard. Today, a 256 GB MacBook Air costs $999 and comes with the same scissor-switch keyboard as the 16-inch MacBook Pro. You save $300, get a much better keyboard, faster performance, and there is no tradeoff. It’s just better and costs less.</p>
  1817. <p>Or, you could spend that same $1,299 (it’s hurting me here not to type “$1,300” but I figure I ought to stay consistent within this section) and get a model with a quad-core Core i5 (instead of dual-core i3) and 512 GB of storage. Same price, <em>way</em> better performance, better keyboard, double the storage.</p>
  1819. <div class="footnotes">
  1820. <hr />
  1821. <ol>
  1823. <li id="fn1-2020-03-18">
  1824. <p>I saw a prerecorded video briefing/presentation on the new products, and I had an off-the-record phone call Q&A with a few Apple folks. For obvious reasons no one in the media had an in-person briefing.&nbsp;<a href="#fnr1-2020-03-18"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1825. </li>
  1827. <li id="fn2-2020-03-18">
  1828. <p>It’s well worth pointing out that in iPadOS 13.4, you can remap hardware modifier keys in Settings → General → Keyboards → Hardware Keyboard → Modifier Keys. So if you’re using one of these Escape-less keyboards and wish you had an Escape key, just remap the Caps Lock key to Escape.&nbsp;<a href="#fnr2-2020-03-18"  class="footnoteBackLink"  title="Jump back to footnote 2 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  1829. </li>
  1831. </ol>
  1832. </div>
  1836.    ]]></content>
  1837.  <title>★ Super Wednesday</title></entry><entry>
  1839.    <link rel="alternate" type="text/html" href="" />
  1840. <link rel="shorturl" href="" />
  1841. <id>,2020://1.36519</id>
  1842. <published>2020-02-27T22:03:52Z</published>
  1843. <updated>2020-02-29T18:43:38Z</updated>
  1844. <author>
  1845. <name>John Gruber</name>
  1846. <uri></uri>
  1847. </author>
  1848. <summary type="text">Iconfactory’s delightful new notepad app for Mac and iOS.</summary>
  1849. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1850. <p>Over the holidays, my friend Craig Hockenberry started working on a small Mac app with a small name: <a href="">Tot</a>. The basic idea: Tot has one window containing seven and only seven scratchpads for collecting text. Tot is most certainly not a full-blown notes app — it’s like the difference between scrap paper and a notebook. Tot is a replacement for temporary Untitled documents in your favorite text editor or full-blown notes app. Tot was largely inspired by Andre Torrez’s utterly simple but deceptively clever app <a href="">Tyke</a> — a simple scratchpad that lives in your menu bar.</p>
  1852. <p>By default Tot works like a regular Mac app, with an icon in your Dock and a regular window. But a prefs setting lets you turn it into a menu bar app, which, I suspect, is how a lot of Tot users will use it. The seven scratchpads are called <em>dots</em>, and each dot has its own color. They work like tabs, basically. You can toggle each dot between a basic rich text view (bold, italics, links) and a plain text representation that uses a small subset of Markdown for formatting. I, of all people, was actually against the Markdown feature on the grounds that parsing Markdown is a tricky can of worms, but Hockenberry <a href="">made it work</a>, and at this point, it’s hard for me to imagine Tot <em>without</em> this feature.</p>
  1854. <p>Once it became obvious that Tot was useful as a Mac app, it became obvious that it would be really nice to have an iOS companion app. Somehow, Hockenberry put that together too, with (in my experience) bulletproof syncing via iCloud.</p>
  1856. <p>Hockenberry’s colleagues at The Iconfactory made the whole thing beautiful. Two quick months later, and here we are: <a href="">Tot 1.0 is shipping</a>, in both the <a href="">Mac</a> and <a href="">iOS</a> App Stores. The Mac app is free of charge, and the iOS app is $20. Some number of you read the preceding sentence and thought, “<em>$20 for a simple note pad, that’s fucking nuts.</em>” Well, then don’t buy it. I love the pricing scheme. The Mac app is the main attraction for me, and it’s completely free. It’s a gift to the Mac community. $20 is, no question, a lot by iOS standards, but the “standards” for iOS utility app prices are so low as to make it not worthwhile to create iOS utility apps. And this is a simple one-time purchase, not a subscription, not an in-app purchase. You want to use Tot on your Mac? It’s totally free. You want to sync your dots to an excellent iPhone/iPad version of Tot, too? $20.</p>
  1858. <p>Tot isn’t properly scriptable with AppleScript, but it does have a URL scheme (documented in Tot’s excellent Help — just that fact that Tot <em>has</em> excellent Help is commendable nowadays) that you can call from AppleScript or shell scripts. Hockenberry wrote <a href="">a small shell script</a> that works as a command-line companion tool — you can use it to append to or get the contents of any dot by number. I’ve already forked it with <a href="">a version that adds support for dot “0”</a> (zero) to target the first empty dot, if there is one. So you can do:</p>
  1860. <pre><code>date | 0 -
  1861. </code></pre>
  1863. <p>to add a timestamp like “Thu Feb 27 16:48:16 EST 2020” to the first empty dot.</p>
  1865. <p>A few small details I adore:</p>
  1867. <ul>
  1868. <li><p>When running in the Dock, the Mac app’s <a href="">icon changes color to correspond to the current dot</a> — <em>and</em> matches your choice of light or dark appearance.</p></li>
  1869. <li><p>The iPhone version offers subtle haptic feedback and animation when switching between dots. E.g. if you’re on dot 1 and tap dot 4, you’ll see dots 2 and 3 fly by and feel three subtle haptic taps.</p></li>
  1870. </ul>
  1872. <p>It’s just a great little utility. The limited scope of Tot reminds me of whiteboard space — expansive, but impermanent and set in size. For me it hearkens back to the <a href="">classic Mac OS</a> <a href="">Note Pad desk accessory</a>,<sup id="fnr1-2020-02-27"><a href="#fn1-2020-02-27">1</a></sup> which was limited to just eight sheets, and intended to run as a small window. Tot is a very modern take on that very old idea.</p>
  1874. <div class="footnotes">
  1875. <hr />
  1876. <ol>
  1877. <li id="fn1-2020-02-27">
  1878. <p>Fire up James Friend’s <a href="">web-based classic Mac emulator</a> and you can see Note Pad in action — Apple Menu → Note Pad. The fundamental similarity to Tot is striking.&nbsp;<a href="#fnr1-2020-02-27"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1879. </li>
  1880. </ol>
  1881. </div>
  1885.    ]]></content>
  1886.  <title>★ Tot</title></entry><entry>
  1888.    <link rel="alternate" type="text/html" href="" />
  1889. <link rel="shorturl" href="" />
  1890. <id>,2020://1.36512</id>
  1891. <published>2020-02-25T20:06:04Z</published>
  1892. <updated>2020-02-27T16:56:14Z</updated>
  1893. <author>
  1894. <name>John Gruber</name>
  1895. <uri></uri>
  1896. </author>
  1897. <summary type="text">The Finder should treat every bit of information it displays as though it’s as important as your bank account balance.</summary>
  1898. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1899. <p>Last week Marco Arment <a href="">tweeted this screenshot of a glitch/bug in the Finder on Catalina</a>: he selected a folder full of multi-hundred megabyte files and the Inspector panel showed the folder size as “Zero KB”.<sup id="fnr1-2020-02-25"><a href="#fn1-2020-02-25">1</a></sup></p>
  1901. <p>Clearly that’s wrong. I know from talking to Arment privately that about 30 seconds after he took the screenshot, the Inspector updated to show the actual folder size. But that’s still <em>very</em> wrong. The Finder should <em>never</em> show inaccurate information regarding the state of the file system. Never.</p>
  1903. <p>This is the sort of problem in recent versions of MacOS that clearly isn’t getting enough attention within Apple. John Moltz and I discussed this on <a href="">yesterday’s episode of my podcast</a>, and Moltz mentioned a similar problem I’ve seen too: you put some large files in the Trash, then empty the Trash, and the available space shown in Finder windows (View → Show Status Bar) <em>doesn’t change at all</em> for an indeterminate amount of time.</p>
  1905. <p>This is terribly wrong. Everything the Finder displays should be correct all the time. If, for some technical reason, it doesn’t know the size of something and needs to wait, it should show a spinner or some other indicator that you, the user, need to wait to get the information. The actual file size of a folder is what you want to see, and ideally you should see it as soon as you ask for it. But a spinner, if the system needs time to calculate the size, is still <em>correct</em> — it’s correctly showing you that you need to wait. But the Finder should <em>never</em> show the wrong number for a file or folder size.</p>
  1907. <p>Obviously, the actual integrity of the file system is the most important factor here. It’s reasonable to say that the integrity of the file system is the single most important responsibility of any operating system. <em>Do not corrupt or lose data.</em> And by all evidence, the <a href="">APFS file system</a> is exemplary in that regard. Apple treats the actual integrity of the file system with the utmost attention that it deserves.</p>
  1909. <p>But the visual representation of the file system in the user interface should be treated with almost the same amount of attention. This is how users <em>see</em> the file system. Showing “Zero KB” for a folder full of large files, or having the available disk space not change at all after emptying the Trash when it was full of very large files, is profoundly wrong. It creates mistrust in an aspect of the system that the user should, ideally, trust completely.</p>
  1911. <p>Consider your bank account. The most important job of your bank is to maintain the integrity of the actual amount of money in your account. But if you log into your account and it shows a balance of “Zero dollars” for 30 seconds before updating to show your actual balance — or, say, if you make a large withdrawal (like emptying the Trash) and the “available balance” doesn’t change — well, you’re probably going to start looking for a new bank. Even if your bank hasn’t <em>actually</em> misplaced a single penny, it’s a real problem if it <em>looks</em> like they have.</p>
  1913. <p>The Finder should treat every bit of information it displays as though it’s as important as your bank account balance.<sup id="fnr2-2020-02-25"><a href="#fn2-2020-02-25">2</a></sup></p>
  1915. <div class="footnotes">
  1916. <hr />
  1917. <ol>
  1918. <li id="fn1-2020-02-25">
  1919. <p>Here’s a fun tip you might not know. The Finder has a File → Get Info menu command with default shortcut ⌘I. This opens a regular window displaying information about the currently selected item(s). But if you hold down the Option key, File → Get Info changes to Show Inspector (and the shortcut, of course, is ⌘⌥I). The Inspector is very similar to the Get Info window, but it’s a floating palette window, and instead of statically showing info for whatever was selected when you invoked it (which is how the standard Get Info window works), the Inspector dynamically changes as you select different items in the Finder.&nbsp;<a href="#fnr1-2020-02-25"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1920. </li>
  1922. <li id="fn2-2020-02-25">
  1923. <p>It used to, for decades. I can’t recall the classic Mac OS Finder <em>ever</em> showing incorrect file sizes. You did have to wait sometimes — often quite a while, because spinning disks were slow (especially floppies, if you want to go back that far) and HFS wasn’t efficient for computing folder sizes. But while waiting for a folder size to compute, you’d see a spinner, and in list view with folder sizes turned off, you’d see “&#45;&#45;” as the folder size, not “0”. I don’t recall Finder info ever being incorrect in the early years of Mac OS X either.</p>
  1925. <p>Something went awry in this regard in recent years.&nbsp;<a href="#fnr2-2020-02-25"  class="footnoteBackLink"  title="Jump back to footnote 2 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  1926. </li>
  1928. </ol>
  1929. </div>
  1933.    ]]></content>
  1934.  <title>★ What You See in the Finder Should Always Be Correct</title></entry></feed><!-- THE END -->

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:

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