[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>2018-01-19T03:26:56Z</updated><rights>Copyright © 2018, John Gruber</rights><entry>
  12.    <link rel="alternate" type="text/html" href="" />
  13. <link rel="shorturl" href="" />
  14. <id>,2018://1.34490</id>
  15. <published>2018-01-19T02:58:44Z</published>
  16. <updated>2018-01-19T03:26:56Z</updated>
  17. <author>
  18. <name>John Gruber</name>
  19. <uri></uri>
  20. </author>
  21. <summary type="text">Make haste slowly.</summary>
  22. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  23. <p><a href="">Om Malik</a>:</p>
  25. <blockquote>
  26.  <p>Dean Cameron Allen, a 50-ish writer, designer, web-guy, and an
  27. all-around rascal, died this weekend in London, U.K. He leaves
  28. behind his parents, a former girlfriend and a lot of friends. If
  29. the universe feels a little hollow this week, now you know why.</p>
  31. <p>Jason Hoffman, founder of Joyent and a close friend, called out of
  32. the blue. He has just moved back from Stockholm, back to the Bay
  33. Area after a stint at Ericsson. “Dean is no more,” Jason said. He
  34. was fighting to hold back his tears, his voice shaking. I think I
  35. heard Jason say that Dean took his own life, giving up on the
  36. struggle.</p>
  37. </blockquote>
  39. <p>Dean was a magnificent bastard. His death is a real gut punch. I heard about it two days ago, and still can&#8217;t believe it. Om&#8217;s obituary is simply splendid, capturing the man I knew.</p>
  41. <p>Textism was such an achingly-good thing &#8212; an utterly personal website of exquisite writing and beautiful design. Unlike most who came from the print world &#8212; and Dean was a mightily talented print designer &#8212; Dean loved and truly <em>got</em> the web. He knew it wasn&#8217;t an ersatz throwaway stand-in for people too cheap to pay for the print edition of a magazine or newspaper. He knew the web was a wonderful new medium of its own, a glorious playground ripe for anything. Textism was well-paced.</p>
  43. <p>Dean strove for perfection and often achieved it.</p>
  45. <p>Textism started in 2001, a little over a year before I started Daring Fireball. To say that Textism was an influence on Daring Fireball is an understatement for the ages. Fairer to say Textism was <em>the</em> influence on Daring Fireball. I don&#8217;t know what DF would&#8217;ve wound up looking and reading like if not for Dean Allen, but it wouldn&#8217;t look or read like it did and does. For godsake <a href="">just read his old About page</a>. It&#8217;s so good, and so <em>Dean</em>.</p>
  47. <p>On the indie web of the early 2000s, Dean Allen was <em>the man</em>. There&#8217;s just no other way to put it. He did it better than anyone, week after week, post after post. And then he just walked away from it. For a while, the long-dormant home page of was replaced by a single word: &#8220;<a href="">Retooling</a>.&#8221; The thought that Textism might someday spring back to life made me downright giddy.</p>
  49. <p>The closest I ever came to telling Dean what an influence Textism was on Daring Fireball was the following, in an email in 2002, after I wrote to him to thank him for a post on Textism &#8212; <a href="">announcing the release of Textile</a> &#8212; that described yours truly as &#8220;witheringly talented&#8221;:</p>
  51. <blockquote>
  52.  <p>Textism has been an inordinate influence on me; there is nothing
  53. else quite like it, but I wish there were.</p>
  54. </blockquote>
  56. <p>Daring Fireball was only months old when I wrote that. We were frequent email correspondents in those days. He was, as you would expect, a master of the clever Subject: line. I helped him with the quote-educating algorithms in Textile. He helped me form the basis of Markdown. (I was badgering Dean with a series of &#8220;Why don&#8217;t you change the syntax of Textile to be more like <em>this</em> and <em>this</em>?&#8221; requests. Dean&#8217;s response was, more or less, &#8220;These are great ideas, but why don&#8217;t you just put them in your own thing?&#8221;)</p>
  58. <p>A year later, Dean wrote me this:</p>
  60. <blockquote>
  61.  <p>Date: Fri, 14 Nov 2003 19:38:16 +0100 <br />
  62. From: Dean Allen <br />
  63. Subject: Empty Coffee Pot</p>
  65. <ol>
  66. <li><p>I really really liked the OSX screen reading essay.</p></li>
  67. <li><p>Good job on the Waffle interview: you’re really establishing a
  68. Voice. Something most writers can only dream of.</p></li>
  69. <li><p>I plan to start corresponding with people again once I get over
  70. the guilt of not having corresponded with people while I went
  71. through the Samsa-like transformation from someone who got away
  72. with pretending the rest of the internet didn’t exist into
  73. someone who did not.</p></li>
  74. </ol>
  76. <p>Yr lad,</p>
  78. <p>- dca</p>
  79. </blockquote>
  81. <p>(The &#8220;OSX screen reading essay&#8221; was <a href="">this 2,900-word exegesis on the improvements to text rendering in Mac OS X 10.3</a>. The &#8220;Waffle interview&#8221; was <a href="">this</a>.)</p>
  83. <p>Dean Allen telling me I was &#8220;establishing a Voice&#8221; is the only compliment about my work that I&#8217;ve ever remembered. That&#8217;s when I knew that maybe I was actually hitting the notes I was trying to hit.</p>
  85. <p>We lost contact in the years of his self-imposed internet exile. Our last email exchange was over seven years ago. Every few months, though, it would occur to me that I dearly missed Textism, and I&#8217;d think to write Dean and tell him so &#8212; and to tell him that his offhand compliment in 2003 was still something I thought about all the time. Thinking maybe he&#8217;d be pleased to hear that, and perhaps he <em>needed</em> to hear it. I never did.</p>
  87. <p>I wish I had.</p>
  91.    ]]></content>
  92.  <title>★ Dean Allen</title></entry><entry>
  93. <title>Apple Shuttle Buses Rerouted Following Attacks</title>
  94. <link rel="alternate" type="text/html" href="" />
  95. <link rel="shorturl" type="text/html" href="" />
  96. <link rel="related" type="text/html" href="" />
  97. <id>,2018:/linked//6.34489</id>
  98. <published>2018-01-18T00:37:45Z</published>
  99. <updated>2018-01-18T00:51:06Z</updated>
  100. <author>
  101. <name>John Gruber</name>
  102. <uri></uri>
  103. </author>
  104. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  105. <p>Jack Morse, reporting for Mashable:</p>
  107. <blockquote>
  108.  <p>The tech giant runs shuttle buses full of employees from San Francisco to its headquarters in Cupertino every day, and, according to a source inside the company, someone is attacking those buses &#8212; and breaking windows.</p>
  110. <p>On an internal Apple email thread viewed by Mashable, one Apple employee speculated that the culprit may be firing &#8220;rubber rounds&#8221; at the buses. At least one of the buses only had the outer pane of its double-paned windows broken.</p>
  112. <p>In response, late Tuesday night, Apple emailed employees to alert them that an untold number of shuttles would be rerouted, adding 30 to 45 minutes to riders&#8217; commute. Mashable obtained the email and has verified its authenticity.</p>
  113. </blockquote>
  115. <p>Christ, what an asshole the guy doing this is. <a href="">Looks like he’s hit Google buses, too</a>.</p>
  117. <div>
  118. <a  title="Permanent link to ‘Apple Shuttle Buses Rerouted Following Attacks’"  href="">&nbsp;★&nbsp;</a>
  119. </div>
  121. ]]></content>
  122.  </entry><entry>
  123. <title>Apple to Create New Campus, Hire 20,000 New Employees</title>
  124. <link rel="alternate" type="text/html" href="" />
  125. <link rel="shorturl" type="text/html" href="" />
  126. <link rel="related" type="text/html" href="" />
  127. <id>,2018:/linked//6.34488</id>
  128. <published>2018-01-17T19:53:58Z</published>
  129. <updated>2018-01-18T00:20:54Z</updated>
  130. <author>
  131. <name>John Gruber</name>
  132. <uri></uri>
  133. </author>
  134. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  135. <p>Apple:</p>
  137. <blockquote>
  138.  <p>Apple expects to invest over $30 billion in capital expenditures in the US over the next five years and create over 20,000 new jobs through hiring at existing campuses and opening a new one. Apple already employs 84,000 people in all 50 states.</p>
  140. <p>The company plans to establish an Apple campus in a new location, which will initially house technical support for customers. The location of this new facility will be announced later in the year.</p>
  141. </blockquote>
  143. <p>Intriguing. This also seems to serve as Apple’s announcement that they plan to repatriate — and pay US taxes on — their overseas cash.</p>
  145. <div>
  146. <a  title="Permanent link to ‘Apple to Create New Campus, Hire 20,000 New Employees’"  href="">&nbsp;★&nbsp;</a>
  147. </div>
  149. ]]></content>
  150.  </entry><entry>
  151. <title>Gorgeous 50-Megapixel Panoramas Shot on an iPhone at 20,000 Feet</title>
  152. <link rel="alternate" type="text/html" href="" />
  153. <link rel="shorturl" type="text/html" href="" />
  154. <link rel="related" type="text/html" href="" />
  155. <id>,2018:/linked//6.34487</id>
  156. <published>2018-01-17T19:49:12Z</published>
  157. <updated>2018-01-17T19:51:43Z</updated>
  158. <author>
  159. <name>John Gruber</name>
  160. <uri></uri>
  161. </author>
  162. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  163. <p>These shots are amazing — but I have to ask: why an iPhone 7?</p>
  165. <div>
  166. <a  title="Permanent link to ‘Gorgeous 50-Megapixel Panoramas Shot on an iPhone at 20,000 Feet’"  href="">&nbsp;★&nbsp;</a>
  167. </div>
  169. ]]></content>
  170.  </entry><entry>
  171. <title>Farhad Manjoo: ‘It’s Time for Apple to Build a Less Addictive iPhone’</title>
  172. <link rel="alternate" type="text/html" href="" />
  173. <link rel="shorturl" type="text/html" href="" />
  174. <link rel="related" type="text/html" href="" />
  175. <id>,2018:/linked//6.34486</id>
  176. <published>2018-01-17T19:32:58Z</published>
  177. <updated>2018-01-18T02:17:27Z</updated>
  178. <author>
  179. <name>John Gruber</name>
  180. <uri></uri>
  181. </author>
  182. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  183. <p>It’s time for Farhad Manjoo to write a less eye-roll-inducing column:</p>
  185. <blockquote>
  186.  <p>Imagine if, once a week, your phone gave you a report on how you spent your time, similar to how your activity tracker tells you how sedentary you were last week. It could also needle you: “Farhad, you spent half your week scrolling through Twitter. Do you really feel proud of that?” It could offer to help: “If I notice you spending too much time on Snapchat next week, would you like me to remind you?”</p>
  187. </blockquote>
  189. <p>This sounds annoying as hell. Being aware of how much time you’re spending in which apps is an interesting idea, but you can already get a good sense of that in the Settings → Battery panel.</p>
  191. <blockquote>
  192.  <p>Another idea is to let you impose more fine-grained controls over notifications. Today, when you let an app send you mobile alerts, it’s usually an all-or-nothing proposition — you say yes to letting it buzz you, and suddenly it’s buzzing you all the time.</p>
  194. <p>Mr. Harris suggested that Apple could require apps to assign a kind of priority level to their notifications. “Let’s say you had three notification levels — heavy users, regular users and lite, or Zen,” Mr. Harris said.</p>
  196. <p>Apple could set rules for what kind of notifications were allowed in each bucket — for instance, the medium bucket might allow notifications generated by other people (like a direct message in Instagram) but not those from the app itself (Instagram just sending you an alert to remind you that your high school friend’s mom’s brother posted a new picture recently).</p>
  197. </blockquote>
  199. <p>I’m all in favor of controls to reduce notifications. But excessive notifications don’t make me feel addicted to my phone — they make me annoyed.</p>
  201. <p>This whole narrative that our phones are “too addictive” is nonsense. When I was a teenager my friends and I spent hours each week on the phone. Regular dumb old landline phones. There was no problem with landline phones being “addictive”. We simply craved social interaction and an alleviation of boredom. We use our “phones” today for the same reasons. They are more of a solution — again, to our collective desire for social interaction and alleviation of boredom — than a problem.</p>
  203. <div>
  204. <a  title="Permanent link to ‘Farhad Manjoo: ‘It’s Time for Apple to Build a Less Addictive iPhone’’"  href="">&nbsp;★&nbsp;</a>
  205. </div>
  207. ]]></content>
  208.  </entry><entry>
  209. <title>Study: 42 Percent of Republicans Believe Accurate — but Negative — Stories Qualify as ‘fake News’</title>
  210. <link rel="alternate" type="text/html" href="" />
  211. <link rel="shorturl" type="text/html" href="" />
  212. <link rel="related" type="text/html" href="" />
  213. <id>,2018:/linked//6.34484</id>
  214. <published>2018-01-16T21:26:07Z</published>
  215. <updated>2018-01-16T21:26:11Z</updated>
  216. <author>
  217. <name>John Gruber</name>
  218. <uri></uri>
  219. </author>
  220. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  221. <p>Erik Wemple:</p>
  223. <blockquote>
  224.  <p>All those media-trust studies have a tendency toward the rote.
  225. Yes, we already knew that the public had little trust in the
  226. country’s journalistic organs. Yes, we knew that finding credible
  227. sources could be a harrowing pursuit for the public. Yes, we knew
  228. that an increasing portion of the U.S. public felt that the news
  229. was biased.</p>
  231. <p>Yet this nugget from a new Gallup-Knight Foundation survey just
  232. about knocked the Erik Wemple Blog out of a decade-long
  233. media-research torpor:</p>
  235. <p>Four in 10 [or 42 percent of] Republicans consider accurate news
  236. stories that cast a politician or political group in a negative
  237. light to always be “fake news.” [The corresponding figure for
  238. Democrats is 17 percent.]</p>
  239. </blockquote>
  241. <p>17 percent for Democrats is a depressing enough figure. 42 is absurd.</p>
  243. <div>
  244. <a  title="Permanent link to ‘Study: 42 Percent of Republicans Believe Accurate — but Negative — Stories Qualify as ‘fake News&#8217;’"  href="">&nbsp;★&nbsp;</a>
  245. </div>
  247. ]]></content>
  248.  </entry><entry>
  249. <link rel="alternate" type="text/html" href=";utm_medium=DARINGFIREBALL&amp;utm_campaign=2018NewYears" />
  250. <link rel="shorturl" href="" />
  251. <link rel="related" type="text/html" href="" />
  252. <id>,2018:/feeds/sponsors//11.34485</id>
  253. <author><name>Daring Fireball Department of Commerce</name></author>
  254. <published>2018-01-16T17:08:43-05:00</published>
  255. <updated>2018-01-16T17:08:45-05:00</updated>
  256. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  257. <p>Highly effective audio-based workouts by certified trainers paired with amazing music. Try for free.</p>
  259. <div>
  260. <a  title="Permanent link to ‘Aaptiv: #1 Audio Fitness App’"  href="">&nbsp;★&nbsp;</a>
  261. </div>
  263. ]]></content>
  264. <title>[Sponsor] Aaptiv: #1 Audio Fitness App</title></entry><entry>
  265. <title>Alex Roy Reviews the Tesla Model 3 After a Cross-Country Speed Run</title>
  266. <link rel="alternate" type="text/html" href="" />
  267. <link rel="shorturl" type="text/html" href="" />
  268. <link rel="related" type="text/html" href="" />
  269. <id>,2018:/linked//6.34483</id>
  270. <published>2018-01-16T01:44:43Z</published>
  271. <updated>2018-01-16T01:44:46Z</updated>
  272. <author>
  273. <name>John Gruber</name>
  274. <uri></uri>
  275. </author>
  276. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  277. <p>Alex Roy, writing for The Drive:</p>
  279. <blockquote>
  280.  <p>The Model 3 is a triumph of industrial design. Forget the
  281. naysayers. Ask anyone who isn&#8217;t a car person, or especially women
  282. &#8212; a group too often excluded from the conversation, despite its
  283. size and disproportionate purchasing power, by an industry yet to
  284. have its Weinstein moment &#8212; for real perspective. Starting with a
  285. clean sheet, Tesla has out-Volvo&#8217;ed Volvo, delivering the purest
  286. interpretation of Scandinavian design in automotive history. I
  287. felt liberated from the tyranny of traditional car dashboards full
  288. of knobs and buttons.</p>
  290. <p>I&#8217;m not saying I&#8217;m opposed to analog controls and traditional
  291. dashboards. Quite the opposite. What I am opposed to is overly
  292. complicated design in either direction. The best iteration is
  293. always the simplest, and traditional car manufacturers have
  294. largely blown it in their respective efforts to integrate digital
  295. with analog.</p>
  296. </blockquote>
  298. <p>He does have one major UI design gripe: the entire interface &#8212; visual, audio, and interaction &#8212; of the Autopilot system. But this is a glowing review overall.</p>
  300. <p>Longtime readers may remember Roy&#8217;s previous mention on Daring Fireball, <a href="">regarding his attempt to set the record for the Cannonball Run 10 years ago</a>.</p>
  302. <p>(<a href="">Thanks to Nick Heer</a>.)</p>
  304. <div>
  305. <a  title="Permanent link to ‘Alex Roy Reviews the Tesla Model 3 After a Cross-Country Speed Run’"  href="">&nbsp;★&nbsp;</a>
  306. </div>
  308. ]]></content>
  309.  </entry><entry>
  310. <title>Hawaii Missile Alert: How One Employee ‘Pushed the Wrong Button’ and Caused a Wave of Panic</title>
  311. <link rel="alternate" type="text/html" href="" />
  312. <link rel="shorturl" type="text/html" href="" />
  313. <link rel="related" type="text/html" href="" />
  314. <id>,2018:/linked//6.34482</id>
  315. <published>2018-01-15T04:13:37Z</published>
  316. <updated>2018-01-15T04:21:22Z</updated>
  317. <author>
  318. <name>John Gruber</name>
  319. <uri></uri>
  320. </author>
  321. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  322. <p>Amy Wang, reporting for The Washington Post:</p>
  324. <blockquote>
  325.  <p>Around 8:05 a.m., the Hawaii emergency employee initiated the internal test, according to a timeline released by the state. From a drop-down menu on a computer program, he saw two options: “Test missile alert” and “Missile alert.” He was supposed to choose the former; as much of the world now knows, he chose the latter, an initiation of a real-life missile alert. [&#8230;]</p>
  327. <p>Around 8:07 a.m., an errant alert went out to scores of Hawaii residents and tourists on their cellphones: “BALLISTIC MISSILE THREAT INBOUND TO HAWAII. SEEK IMMEDIATE SHELTER. THIS IS NOT A DRILL.” A more detailed message scrolled across television screens in Hawaii, suggesting, “If you are indoors, stay indoors. If you are outdoors, seek immediate shelter in a building. Remain indoors well away from windows. If you are driving, pull safely to the side of the road and seek shelter in a building or lay on the floor.”</p>
  328. </blockquote>
  330. <p>This is just terrible, terrible user interface design.</p>
  332. <div>
  333. <a  title="Permanent link to ‘Hawaii Missile Alert: How One Employee ‘Pushed the Wrong Button’ and Caused a Wave of Panic’"  href="">&nbsp;★&nbsp;</a>
  334. </div>
  336. ]]></content>
  337.  </entry><entry>
  338. <title>Jamf Now</title>
  339. <link rel="alternate" type="text/html" href=";utm_medium=text&amp;utm_campaign=2018-02" />
  340. <link rel="shorturl" type="text/html" href="" />
  341. <link rel="related" type="text/html" href="" />
  342. <id>,2018:/linked//6.34481</id>
  343. <published>2018-01-14T01:47:09Z</published>
  344. <updated>2018-01-14T01:47:11Z</updated>
  345. <author>
  346. <name>John Gruber</name>
  347. <uri></uri>
  348. </author>
  349. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  350. <p>My thanks to Jamf for once again sponsoring the DF RSS feed. Jamf Now is a simple device management solution designed to help anyone set up, manage, and protect Apple devices at work. Easily configure email and Wi-Fi networks, distribute apps to your team, and protect sensitive data without locking down devices.</p>
  352. <p>Their latest feature: OS updates. Keep your Apple devices running the latest versions of iOS and MacOS by initiating OS Updates with Jamf Now.</p>
  354. <p><a href=";utm_medium=text&amp;utm_campaign=2018-02">Daring Fireball readers can create an account and manage three devices for free</a>. Forever. Each additional device is just $2 per month. <a href=";utm_medium=text&amp;utm_campaign=2018-02">Create your free account today</a>.</p>
  356. <div>
  357. <a  title="Permanent link to ‘Jamf Now’"  href="">&nbsp;★&nbsp;</a>
  358. </div>
  360. ]]></content>
  361.  </entry><entry>
  362. <title>Uber’s Secret Tool for Keeping the Cops in the Dark</title>
  363. <link rel="alternate" type="text/html" href="" />
  364. <link rel="shorturl" type="text/html" href="" />
  365. <link rel="related" type="text/html" href="" />
  366. <id>,2018:/linked//6.34480</id>
  367. <published>2018-01-13T04:45:55Z</published>
  368. <updated>2018-01-13T04:47:59Z</updated>
  369. <author>
  370. <name>John Gruber</name>
  371. <uri></uri>
  372. </author>
  373. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  374. <p>At this point Uber should best be described not as a business or startup, but as a racket, a criminal enterprise.</p>
  376. <div>
  377. <a  title="Permanent link to ‘Uber’s Secret Tool for Keeping the Cops in the Dark’"  href="">&nbsp;★&nbsp;</a>
  378. </div>
  380. ]]></content>
  381.  </entry><entry>
  382. <title>The iOS Economy, Updated</title>
  383. <link rel="alternate" type="text/html" href="" />
  384. <link rel="shorturl" type="text/html" href="" />
  385. <link rel="related" type="text/html" href="" />
  386. <id>,2018:/linked//6.34479</id>
  387. <published>2018-01-12T21:00:31Z</published>
  388. <updated>2018-01-12T21:04:02Z</updated>
  389. <author>
  390. <name>John Gruber</name>
  391. <uri></uri>
  392. </author>
  393. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  394. <p>Horace Dediu, on the latest figures from Apple on App Store revenue:</p>
  396. <blockquote>
  397.  <p>A few observations:</p>
  399. <ul>
  400. <li><p>Developer payment rate is now above $25 billion/yr. I’ve been
  401. notified via Twitter that this is higher than the <a href="">revenue of
  402. McDonald’s Corporation</a> in 2016.</p></li>
  403. <li><p>During this year iOS users will be spending about $100 million
  404. per day for Apps. This was Google’s <a href="">AdWords revenue rate</a>
  405. in 2012.</p></li>
  406. <li><p>The spending on App Store has been rising steadily, adding about
  407. $5 billion/yr since mid 2011.</p></li>
  408. <li><p>Apps are the biggest component of Apple services and helped that
  409. segment gross over $57 billion in 2017, <a href="">passing Fortune 100
  410. level</a> (net of developer payments).</p></li>
  411. </ul>
  412. </blockquote>
  414. <p><strong>See also:</strong> <a href="">Apple&#8217;s cash illustrated</a> &#8212; an informative graph.</p>
  416. <div>
  417. <a  title="Permanent link to ‘The iOS Economy, Updated’"  href="">&nbsp;★&nbsp;</a>
  418. </div>
  420. ]]></content>
  421.  </entry><entry>
  422. <title>Peter Valdes-Dapena Reviews the Tesla Model 3</title>
  423. <link rel="alternate" type="text/html" href="" />
  424. <link rel="shorturl" type="text/html" href="" />
  425. <link rel="related" type="text/html" href="" />
  426. <id>,2018:/linked//6.34478</id>
  427. <published>2018-01-12T20:20:03Z</published>
  428. <updated>2018-01-12T20:20:06Z</updated>
  429. <author>
  430. <name>John Gruber</name>
  431. <uri></uri>
  432. </author>
  433. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  434. <p>Perhaps unsurprisingly for a review for CNN, the video seems like the &#8220;real&#8221; review, and the written article seems like an afterthought extracted from the video review. He makes three main points:</p>
  436. <ol>
  437. <li><p>The car drives and performs well, about how you’d expect given Tesla’s reputation.</p></li>
  438. <li><p>It’s expensive for what you get compared to other cars in this price range &#8212; but this point seems hard to quantify, because none of those other cars have Tesla’s excellent electric drive train.</p></li>
  439. <li><p>Having almost <em>all</em> of the controls, including things like controlling the air vents, go through the touchscreen is not a good design. He writes:</p>
  441. <blockquote>
  442.  <p>To do almost anything, from adjusting the mirrors to tweaking the
  443. car&#8217;s speed while driving in Autopilot, I had to use the screen.
  444. There are two unmarked knobs on the steering that are involved in
  445. various functions but, before you can use the knobs, you have to
  446. poke around on the big screen first. It&#8217;s annoying and most people
  447. will hate it. More importantly, it&#8217;s terribly distracting.</p>
  448. </blockquote></li>
  449. </ol>
  451. <p>I feel like #3 is by far the most interesting point, but Valdes-Dapena seems ill-equipped to make it. He just says it’s very annoying, rather than explaining or illustrating <em>why</em> it’s annoying. Perhaps because he’s used to writing about cars, not about user interfaces?</p>
  453. <p>I’ve long been frustrated by the fact that car reviews seldom devote attention or expertise to the design of the controls of the car. They matter a lot to me (shocker, I know), but I think they matter a lot to everyone, whether they think about control design consciously or not. The Model 3&#8217;s touchscreen centric design is so radical, it deserves a thorough review of its own.</p>
  455. <div>
  456. <a  title="Permanent link to ‘Peter Valdes-Dapena Reviews the Tesla Model 3’"  href="">&nbsp;★&nbsp;</a>
  457. </div>
  459. ]]></content>
  460.  </entry><entry>
  461. <title>Facebook Purportedly Changes News Feed to Make It ‘Good for People’</title>
  462. <link rel="alternate" type="text/html" href="" />
  463. <link rel="shorturl" type="text/html" href="" />
  464. <link rel="related" type="text/html" href="" />
  465. <id>,2018:/linked//6.34477</id>
  466. <published>2018-01-12T19:57:17Z</published>
  467. <updated>2018-01-12T22:33:18Z</updated>
  468. <author>
  469. <name>John Gruber</name>
  470. <uri></uri>
  471. </author>
  472. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  473. <p>Laura Hazard Owen, writing for the Nieman Journalism Lab:</p>
  475. <blockquote>
  476.  <p>Facebook is making big, immediate changes to News Feed. The
  477. company will now prioritize content from friends, family, and
  478. groups over “public content like posts from businesses, brands,
  479. and media,” CEO Mark Zuckerberg <a href="">wrote in a post Thursday
  480. night</a>. News publishers that have relied on Facebook for
  481. traffic will suffer: “Some news helps start conversations on
  482. important issues,” Zuckerberg wrote. “But too often today,
  483. watching video, reading news or getting a page update is just a
  484. passive experience.”</p>
  485. </blockquote>
  487. <p><a href="">Who knows</a> what they&#8217;re actually changing, but I&#8217;ll take this opportunity to reiterate what I&#8217;ve believed all along: news publishers that have relied on Facebook for traffic are fools. The only audience you can count on is an audience you&#8217;ve built yourself and have a direct relationship with.</p>
  489. <p><a href="">Casey Newton put it well</a>:</p>
  491. <blockquote>
  492.  <p>So many publishers think they have audiences, when what they
  493. really have is traffic.</p>
  495. <p>I think we’re about to find out who has an audience.</p>
  496. </blockquote>
  498. <div>
  499. <a  title="Permanent link to ‘Facebook Purportedly Changes News Feed to Make It &#8216;Good for People&#8217;’"  href="">&nbsp;★&nbsp;</a>
  500. </div>
  502. ]]></content>
  503.  </entry><entry>
  504. <title>Ben Bajarin: ‘Apple’s Indirect Presence Fades From CES’</title>
  505. <link rel="alternate" type="text/html" href="" />
  506. <link rel="shorturl" type="text/html" href="" />
  507. <link rel="related" type="text/html" href="" />
  508. <id>,2018:/linked//6.34476</id>
  509. <published>2018-01-11T23:16:46Z</published>
  510. <updated>2018-01-12T00:30:20Z</updated>
  511. <author>
  512. <name>John Gruber</name>
  513. <uri></uri>
  514. </author>
  515. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  516. <p>Ben Bajarin, writing from CES 2018:</p>
  518. <blockquote>
  519.  <p>We would go to CES and remark at how Apple’s dominance loomed over
  520. the show. Vendors of all shapes and sizes were rushing to be a
  521. part of the Apple ecosystem. Apple’s ecosystem was front and
  522. center with everything from iOS apps, to accessories galore for
  523. iPhone and iPad, and even companies looking to copy Apple in many
  524. ways. The last year or so, things have dramatically changed, and
  525. that change is further evident at this year’s CES.</p>
  527. <p>Gone are the days of Apple’s presence, or observably “winning” of
  528. CES, even though they are not present. It was impossible to walk
  529. the show floor and not see a vast array of interesting innovations
  530. which touched the Apple ecosystem in some way. Now it is almost
  531. impossible to walk the floor and see any products that touch the
  532. Apple ecosystem in any way except for an app on the iOS App Store.
  533. The Apple ecosystem is no longer the star of CES but instead
  534. things like Amazon’s Alexa voice platform, and now Google’s
  535. assistant voice platform is the clear ecosystem winners of CES.</p>
  537. <p>While many Apple defenders want to dismiss the momentum we are
  538. observing with the Amazon ecosystem on display here at CES, while
  539. Amazon is similarly not present just like Apple, I believe it is a
  540. mistake to do so.</p>
  542. <p>It is easy to say that because Apple was never present at CES that
  543. the show didn’t mean something to them or their ecosystem. It is
  544. easy, and correct to say that CES was not, or never was, a measure
  545. of the health of Apple’s products. <em>It is, however, incorrect and
  546. dangerous to miss that CES had been, for some time, a barometer
  547. for the health of Apple’s ecosystem.</em></p>
  548. </blockquote>
  550. <p>It may or may not mean anything for Apple, but I do think this is an interesting and undeniable observation.</p>
  552. <div>
  553. <a  title="Permanent link to ‘Ben Bajarin: ‘Apple’s Indirect Presence Fades From CES’’"  href="">&nbsp;★&nbsp;</a>
  554. </div>
  556. ]]></content>
  557.  </entry><entry>
  558. <title>Confide Popular With Republican Politicians</title>
  559. <link rel="alternate" type="text/html" href="" />
  560. <link rel="shorturl" type="text/html" href="" />
  561. <link rel="related" type="text/html" href="" />
  562. <id>,2018:/linked//6.34475</id>
  563. <published>2018-01-11T19:58:13Z</published>
  564. <updated>2018-01-11T19:58:14Z</updated>
  565. <author>
  566. <name>John Gruber</name>
  567. <uri></uri>
  568. </author>
  569. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  570. <p>I thought that Confide rang a bell. I hadn&#8217;t tried it personally until <a href="">yesterday</a>, but now I remember where I&#8217;d heard of it: in the early days of the Trump White House, there were reports like this one from Axios that leaking staff members were using it to communicate privately.</p>
  572. <div>
  573. <a  title="Permanent link to ‘Confide Popular With Republican Politicians’"  href="">&nbsp;★&nbsp;</a>
  574. </div>
  576. ]]></content>
  577.  </entry><entry>
  579.    <link rel="alternate" type="text/html" href="" />
  580. <link rel="shorturl" href="" />
  581. <id>,2018://1.34474</id>
  582. <published>2018-01-11T03:34:13Z</published>
  583. <updated>2018-01-18T22:29:42Z</updated>
  584. <author>
  585. <name>John Gruber</name>
  586. <uri></uri>
  587. </author>
  588. <summary type="text">It’s an interesting puzzle trying to figure out how they’re doing this.</summary>
  589. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  590. <p><a href="">From the announcement of a new version of Confide, a &#8220;confidential messenger&#8221; app</a>:</p>
  592. <blockquote>
  593.  <p>ScreenShield is a patent-pending technology that allows you to
  594. view an app’s content on your screen but prevents you from taking
  595. a screenshot of it. If you try to take a screenshot on Confide,
  596. you will now simply capture a blank screen¹. ScreenShield also
  597. protects against other forms of screen capture, including iOS 11
  598. screen recording, AirPlay screen mirroring, QuickTime screen
  599. recording as well as taking screenshots from the app switcher or
  600. by using Xcode.</p>
  602. <p>We initially developed ScreenShield for Confide, but quickly
  603. realized that it could be used in a large number of apps &#8212; far
  604. more than we could build ourselves. That’s why we created
  605. <a href="">ScreenShieldKit</a> &#8212; to offer the ScreenShield technology to
  606. 3rd-party developers for use in a variety of different apps and
  607. categories.</p>
  609. <p>While there’s a lot of technology under the hood that makes
  610. ScreenShield possible, the great news is that there are no strange
  611. gimmicks for users (e.g., it doesn’t require them to hold their
  612. finger on the screen) &#8212; it just works as expected. And
  613. ScreenShieldKit is simple for developers to integrate into their
  614. iOS apps, providing easy to use replacements for UITextView and
  615. UIImageView.</p>
  616. </blockquote>
  618. <p>It&#8217;s an interesting puzzle trying to figure out how they&#8217;re doing this. Detecting that a screenshot <em>has</em> been taken is easy &#8212; <a href="">iOS has an API</a> that apps can use to get notified when the screen is recorded in any way. But ScreenShield is detecting it <em>before</em> the screenshot gets taken, so they can blank out the content in their text and image views.</p>
  620. <p>I wasn&#8217;t familiar with Confide, so I downloaded it and kicked the tires, and the screenshot prevention works as advertised. Confide <em>also</em> sends a notification to whomever you&#8217;re messaging with to warn them that you <em>tried</em> to take a screenshot, <em>a la</em> Snapchat, and they immediately delete the message you tried to capture (I presume so that you can&#8217;t try to capture it another way, like, say, by taking a photo of the screen &#8212; see below).</p>
  622. <p>My best guess as to how they&#8217;re doing this is that they&#8217;re using AVPlayer and somehow using <a href="">FairPlay Streaming</a> to block screenshots and recording. (Where by &#8220;my&#8221; best guess I mean the best guess of <a href="">a smart friend</a> who poked around the Confide app bundle.) Have you ever noticed how you can&#8217;t take screenshots of streaming video content in apps like Netflix and HBO Go/Now? That&#8217;s a feature in iOS (and MacOS &#8212; try taking a screenshot of Netflix video playing in Safari) for skittish video providers who don&#8217;t want us to capture even a still frame of their precious content. I <em>think</em> ScreenShieldKit is somehow using this to prevent screenshots or video captures of text or images.</p>
  624. <p>If anyone out there has a better or more informed guess, please let me know.</p>
  626. <p>If I&#8217;m reading their application correctly, Confide has also filed for a patent <a href=";Sect2=HITOFF&amp;p=1&amp;u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&amp;r=1&amp;f=G&amp;l=50&amp;co1=AND&amp;d=PTXT&amp;s1=9648001&amp;OS=9648001&amp;RS=9648001">for a way to identify when you&#8217;re using another device to take a photo of your screen</a>.</p>
  630.    ]]></content>
  631.  <title>★ ScreenShield — a Third-Party SDK That Somehow Allows iOS Apps to Prevent Screenshots</title></entry><entry>
  632. <title>Wired: ‘How Outlier, the Underground Fashion Label for Nerds, Got Cool’</title>
  633. <link rel="alternate" type="text/html" href="" />
  634. <link rel="shorturl" type="text/html" href="" />
  635. <link rel="related" type="text/html" href="" />
  636. <id>,2018:/linked//6.34472</id>
  637. <published>2018-01-11T02:45:06Z</published>
  638. <updated>2018-01-11T03:38:38Z</updated>
  639. <author>
  640. <name>John Gruber</name>
  641. <uri></uri>
  642. </author>
  643. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  644. <p>Adam Rogers, writing for Wired on indie menswear maker Outlier (<a href="">a former DF sponsor</a>):</p>
  646. <blockquote>
  647.  <p>Pants tough enough to deal with anything became Outlier’s
  648. signature play &#8212; trousers “for the end of the world,” as the
  649. folks at GQ <a href="">put it</a>. “We were trying to solve a specific cycling
  650. problem,” Burmeister says. “How to not look like a cyclist but
  651. still perform.”</p>
  653. <p>They started going to textile conferences &#8212; Outdoor Retailer,
  654. then in Utah, was a big one. They wanted to find out where big
  655. companies, which they assumed used all the best stuff, got their
  656. supplies. But it turned out that the big companies of the world
  657. actually used the best <em>cheapest</em> materials.</p>
  659. <p>As for the actual best, well, “we found that there was all this
  660. stuff nobody was touching. We were stunned. Like, nobody is using
  661. this? Nobody is using this?” Burmeister says. Military fabrics,
  662. equestrian fabrics, industrial fabrics &#8212; they were all for sale,
  663. or had been. They found, for example, a doubleweave with
  664. Cordura-grade nylon on one side and a softer nylon/polyester
  665. blend on the other. It seemed like it would make really great
  666. pair of jeans.</p>
  667. </blockquote>
  669. <p>Outlier&#8217;s clothes aren&#8217;t cheap, but once you wear them, you realize how cheaply made most other clothes are. (<a href="">Via Greg Koenig</a>.)</p>
  671. <div>
  672. <a  title="Permanent link to ‘Wired: &#8216;How Outlier, the Underground Fashion Label for Nerds, Got Cool&#8217;’"  href="">&nbsp;★&nbsp;</a>
  673. </div>
  675. ]]></content>
  676.  </entry><entry>
  677. <title>Android Central: ‘Essential Phone Review, Four Months Later: The Sun Is Setting on This Experiment’</title>
  678. <link rel="alternate" type="text/html" href="" />
  679. <link rel="shorturl" type="text/html" href="" />
  680. <link rel="related" type="text/html" href="" />
  681. <id>,2018:/linked//6.34471</id>
  682. <published>2018-01-10T19:56:05Z</published>
  683. <updated>2018-01-10T19:56:08Z</updated>
  684. <author>
  685. <name>John Gruber</name>
  686. <uri></uri>
  687. </author>
  688. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  689. <p>Andrew Martonik, writing for Android Central two weeks ago:</p>
  691. <blockquote>
  692.  <p>It all starts with just general app instability. Apps crash &#8212; a
  693. lot. More than I&#8217;ve experienced on any other phone. They freeze,
  694. stutter, lock up and force close. Sometimes you tap an app to
  695. open it, and nothing happens for multiple seconds. When an app
  696. calls up another one through a share action, it takes the same
  697. egregious delay. Sometimes apps open and switch just fine, but
  698. then randomly slow down to a crawl with inordinately long splash
  699. screens or loading animations. And it isn&#8217;t tied to just one app,
  700. it&#8217;s <em>all</em> apps.</p>
  702. <p>The app issues seem to come as a result of general system
  703. instability that I haven&#8217;t seen in a high-end phone in years.
  704. Touch response is very slow, making everything simply feel
  705. sluggish as you tap and scroll around every day. The phone
  706. will often struggle to open or close the camera and can fail
  707. to save photos if you close the camera too quickly. I&#8217;ve had
  708. the entire phone go unresponsive for several minutes and
  709. require a force reboot (hold the power button for ~15 seconds)
  710. multiple times. [&#8230;]</p>
  712. <p>The camera app is slow and unstable and lacks basic features like
  713. viewfinder grid lines or any sort of customization or &#8220;pro&#8221; mode.
  714. HDR mode doesn&#8217;t really seem to do anything but take photos
  715. slower, and toggling it on still inexplicably turns the flash to
  716. &#8220;auto&#8221; mode. The slow performance directly contributes to missing
  717. shots, and the fundamentals of a small sensor with no OIS mean you
  718. get grainy and blurry low-light shots regularly. The Essential
  719. Phone&#8217;s camera is still <em>so</em> far from the competition.</p>
  720. </blockquote>
  722. <p>In short, the Essential phone is a disaster.</p>
  724. <p>(Yet oddly it has <a href="">the same score from The Verge</a> &#8212; 8/10 &#8212; <a href="">as the iPhone 8</a>.)</p>
  726. <div>
  727. <a  title="Permanent link to ‘Android Central: &#8216;Essential Phone Review, Four Months Later: The Sun Is Setting on This Experiment&#8217;’"  href="">&nbsp;★&nbsp;</a>
  728. </div>
  730. ]]></content>
  731.  </entry><entry>
  732. <title>‘The Good War’</title>
  733. <link rel="alternate" type="text/html" href="" />
  734. <link rel="shorturl" type="text/html" href="" />
  735. <link rel="related" type="text/html" href="" />
  736. <id>,2018:/linked//6.34470</id>
  737. <published>2018-01-10T18:39:38Z</published>
  738. <updated>2018-01-10T18:39:40Z</updated>
  739. <author>
  740. <name>John Gruber</name>
  741. <uri></uri>
  742. </author>
  743. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  744. <p>Thought-provoking graphic essay by Mike Dawson and Chris Hayes.</p>
  746. <div>
  747. <a  title="Permanent link to ‘&#8216;The Good War&#8217;’"  href="">&nbsp;★&nbsp;</a>
  748. </div>
  750. ]]></content>
  751.  </entry><entry>
  752. <title>MacOS 10.13 High Sierra’s App Store System Prefs Panel Can Be Unlocked With Any Password</title>
  753. <link rel="alternate" type="text/html" href="" />
  754. <link rel="shorturl" type="text/html" href="" />
  755. <link rel="related" type="text/html" href="" />
  756. <id>,2018:/linked//6.34469</id>
  757. <published>2018-01-10T18:17:17Z</published>
  758. <updated>2018-01-10T18:17:44Z</updated>
  759. <author>
  760. <name>John Gruber</name>
  761. <uri></uri>
  762. </author>
  763. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  764. <p>This one is relatively low stakes:</p>
  766. <ul>
  767. <li>These settings are unlocked by default for admin users.</li>
  768. <li>Entering a bogus password only works if you&#8217;re logged in as an admin user.</li>
  769. <li>The settings in this panel aren&#8217;t particularly sensitive.</li>
  770. <li>It&#8217;s apparently already fixed in the current High Sierra developer betas.</li>
  771. </ul>
  773. <p>But, still, this is embarrassing given what we just went through <a href="">with the very serious root-access-with-no-password bug</a>. <a href=",28804,1870938_1870943_1870944,00.html">As a wise man once said</a>, &#8220;Fool me once, shame on… shame on you. Fool me… You can&#8217;t get fooled again.&#8221;</p>
  775. <div>
  776. <a  title="Permanent link to ‘MacOS 10.13 High Sierra&#8217;s App Store System Prefs Panel Can Be Unlocked With Any Password’"  href="">&nbsp;★&nbsp;</a>
  777. </div>
  779. ]]></content>
  780.  </entry><entry>
  781. <title>Pop-Up Mobile Ads Surge as Sites Scramble to Stop Them</title>
  782. <link rel="alternate" type="text/html" href="" />
  783. <link rel="shorturl" type="text/html" href="" />
  784. <link rel="related" type="text/html" href="" />
  785. <id>,2018:/linked//6.34468</id>
  786. <published>2018-01-10T02:21:49Z</published>
  787. <updated>2018-01-10T03:01:03Z</updated>
  788. <author>
  789. <name>John Gruber</name>
  790. <uri></uri>
  791. </author>
  792. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  793. <p>Lily Hay Newman, reporting for Wired:</p>
  795. <blockquote>
  796.  <p>These redirects can show up seemingly out of the blue when you&#8217;re
  797. in a mobile browser like Chrome, or even when you&#8217;re using a
  798. service like Facebook or Twitter and navigating to a page through
  799. one of their in-app browsers. Suddenly you go from loading a news
  800. article to wriggling away from an intrusive ad. What enables these
  801. ad redirects to haunt virtually any browser or app at any time,
  802. rather than just the sketchy backwaters in which they used to
  803. roam? Third-party ad servers that either don&#8217;t vet ad submissions
  804. properly for the JavaScript components that could cause redirects,
  805. or get duped by innocent-looking ads that hide their sketchy code. [&#8230;]</p>
  807. <p>An ad hijacking your browser like that isn&#8217;t technically a hack,
  808. in the sense that it doesn&#8217;t exploit a software vulnerability.
  809. Instead, it relies on the attacker&#8217;s ability to submit and run ads
  810. that contain redirecting JavaScript. But though they aren&#8217;t a
  811. critical threat to web users yet, redirecting mobile ads could
  812. create a jumping off point for attackers. And since you encounter
  813. the redirects while browsing on even prominent, legitimate sites,
  814. there&#8217;s nowhere to hide. Sometimes the ads are even designed to
  815. block your &#8220;Back&#8221; button, or keep redirecting when you try to
  816. close them, making it difficult to escape without having to
  817. restart the browser.</p>
  819. <p>&#8220;I do think it&#8217;s new that the ads are so pervasive and are on
  820. first-tier publishers,&#8221; says Anil Dash, CEO of the software
  821. engineering firm Fog Creek. &#8220;These things used to be relegated to
  822. garbage sites, now it&#8217;s happening on the New York Times.&#8221;</p>
  823. </blockquote>
  825. <p>The fact that ad networks are delivering unvetted JavaScript in their payloads is unsurprising but horrifying. They&#8217;re confined to your browser&#8217;s sandbox, but JavaScript-based ads are effectively malware at this point: they violate your privacy; consume excessive CPU time, bandwidth, and battery life; and now literally hijack your browsing experience.</p>
  827. <p>(And now with Meltdown and Spectre, we have the added worry that <a href="">JavaScript might be malware that breaks through browsers&#8217; sandbox protections</a>.)</p>
  829. <div>
  830. <a  title="Permanent link to ‘Pop-Up Mobile Ads Surge as Sites Scramble to Stop Them’"  href="">&nbsp;★&nbsp;</a>
  831. </div>
  833. ]]></content>
  834.  </entry><entry>
  835. <title>Google Announces Plan to Improve URLs for AMP Pages, But Even If It Happens, Which Remains Uncertain, AMP Will Still Suck</title>
  836. <link rel="alternate" type="text/html" href="" />
  837. <link rel="shorturl" type="text/html" href="" />
  838. <link rel="related" type="text/html" href="" />
  839. <id>,2018:/linked//6.34467</id>
  840. <published>2018-01-10T00:24:20Z</published>
  841. <updated>2018-01-10T00:40:10Z</updated>
  842. <author>
  843. <name>John Gruber</name>
  844. <uri></uri>
  845. </author>
  846. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  847. <p>Malte Ubl, tech lead for the AMP Project at Google</p>
  849. <blockquote>
  850.  <p>Based on this web standard AMP navigations from Google Search can
  851. take advantage of privacy-preserving preloading and the
  852. performance of Google’s servers, while URLs remain as the
  853. publisher intended and the primary security context of the web,
  854. the origin, remains intact. We have built a prototype based on
  855. the Chrome Browser and an experimental version of Google Search
  856. to make sure it actually does deliver on both the desired UX and
  857. performance in real use cases. This step gives us confidence that
  858. we have a promising solution to this hard problem and that it
  859. will soon become the way that users will encounter AMP content on
  860. the web.</p>
  862. <p>The next steps are moving towards fully implementing the new web
  863. standard in web browsers and in the Google AMP Cache. Our goal is
  864. that Web Packaging becomes available in as many browsers as
  865. possible (after all Web Packaging has exciting use cases beyond
  866. just AMP such as offline pages, ES6 module loading, and resource
  867. bundling). In particular, we intend to extend existing work on
  868. WebKit to include the implementation of Web Packaging and the
  869. Google Chrome team’s implementation is getting started.</p>
  871. <p>We’re super excited about getting this work under way and we
  872. expect the changes to first reach users in the second half of
  873. 2018. Thanks for all of your feedback on the matter and we will
  874. keep you all updated on the progress right here in this blog!</p>
  875. </blockquote>
  877. <p>A bunch of readers have forwarded this story to me, <a href="">based on my previous criticism of AMP</a>. This announcement isn&#8217;t bad news, and might be good news, but at this point it&#8217;s all conjecture, particularly for browsers other than Chrome. Even if it all works out, it only solves one problem: URLs. It doesn&#8217;t solve the deeper problem of content being hosted on Google&#8217;s servers, rather than publishers&#8217; own servers. In addition to ceding independence, think about what this means for search engines other than Google. One of AMP&#8217;s foundational tenets is that Google Search is the one and only search engine.</p>
  879. <p>And at a technical level <a href="">AMP still sucks</a>:</p>
  881. <blockquote>
  882.  <p><a href="">I’m on the
  883. record</a>
  884. as being strongly opposed to AMP simply on the grounds of
  885. publication independence. I’d stand by that even if the
  886. implementation were great. But the implementation is not great &#8212;
  887. it’s terrible. Yes, AMP pages load fast, but you don’t need AMP
  888. for fast-loading web pages. If you are a publisher and your web
  889. pages don’t load fast, the sane solution is to <a href="">fix your fucking
  890. website so that pages load
  891. fast</a>, not to throw your
  892. hands up in the air and implement AMP.</p>
  894. <p>But other than loading fast, AMP <em>sucks</em>. It implements its own
  895. scrolling behavior on iOS, which feels unnatural, and even worse,
  896. it breaks the decade-old system-wide iOS behavior of being able to
  897. tap the status bar to scroll to the top of any scrollable view.
  898. AMP also completely breaks Safari’s ability to search for text on
  899. a page (via the “Find on Page” action in the sharing sheet).
  900. Google has no respect for the platform. If I had my way, Mobile
  901. Safari would refuse to render AMP pages. It’s a deliberate effort
  902. by Google to break the open web.</p>
  903. </blockquote>
  905. <p>Seven months later and still none of these things work properly for AMP pages displayed on Mobile Safari. And I forgot to mention back in May that Mobile Safari doesn&#8217;t automatically show/hide its browser chrome as you scroll, like it does for any normal web page. AMP pages are also incompatible with Safari Reader mode, making them harder to read for some people, and impossible to read for others.</p>
  907. <p>Sharing canonical URLs rather than URLs is just one of many problems with AMP, and the &#8220;fix&#8221; proposed here requires updated versions of every web browser in the world to work.</p>
  909. <div>
  910. <a  title="Permanent link to ‘Google Announces Plan to Improve URLs for AMP Pages, But Even If It Happens, Which Remains Uncertain, AMP Will Still Suck’"  href="">&nbsp;★&nbsp;</a>
  911. </div>
  913. ]]></content>
  914.  </entry><entry>
  915. <title>North Carolina Congressional Map Ruled Unconstitutionally Gerrymandered</title>
  916. <link rel="alternate" type="text/html" href=";contentCollection=BreakingNews&amp;contentID=66339525&amp;pgtype=Homepage" />
  917. <link rel="shorturl" type="text/html" href="" />
  918. <link rel="related" type="text/html" href="" />
  919. <id>,2018:/linked//6.34466</id>
  920. <published>2018-01-09T23:53:34Z</published>
  921. <updated>2018-01-09T23:53:36Z</updated>
  922. <author>
  923. <name>John Gruber</name>
  924. <uri></uri>
  925. </author>
  926. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  927. <p>Alan Blinder, reporting for The New York Times:</p>
  929. <blockquote>
  930.  <p>A panel of federal judges struck down North Carolina’s
  931. congressional map on Tuesday, declaring it unconstitutionally
  932. gerrymandered and demanding that the Republican-controlled General
  933. Assembly redraw district lines before this year’s midterm
  934. elections.</p>
  936. <p>The ruling was the first time that a federal court had blocked a
  937. congressional map because the judges believed it to be a partisan
  938. gerrymander, and it deepened the political chaos that has
  939. enveloped North Carolina in recent years.</p>
  940. </blockquote>
  942. <p>More good news on the voting front.</p>
  944. <div>
  945. <a  title="Permanent link to ‘North Carolina Congressional Map Ruled Unconstitutionally Gerrymandered’"  href="">&nbsp;★&nbsp;</a>
  946. </div>
  948. ]]></content>
  949.  </entry><entry>
  950. <title>New Bill Aims to Eliminate Paperless Voting Machines</title>
  951. <link rel="alternate" type="text/html" href="" />
  952. <link rel="shorturl" type="text/html" href="" />
  953. <link rel="related" type="text/html" href="" />
  954. <id>,2018:/linked//6.34465</id>
  955. <published>2018-01-09T23:18:29Z</published>
  956. <updated>2018-01-09T23:46:06Z</updated>
  957. <author>
  958. <name>John Gruber</name>
  959. <uri></uri>
  960. </author>
  961. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  962. <p>Timothy B. Lee, writing for Ars Technica:</p>
  964. <blockquote>
  965.  <p>&#8220;With the 2018 elections just around the corner, Russia will be
  966. back to interfere again,&#8221; said co-sponsor Sen. Kamala Harris
  967. (D-Calif.).</p>
  969. <p>So a group of senators led by James Lankford (R-Okla.) wants to
  970. shore up the security of American voting systems ahead of the 2018
  971. and 2020 elections. And the senators have focused on two major
  972. changes that have broad support from voting security experts.</p>
  974. <p>The first objective is to get rid of paperless electronic voting
  975. machines. Computer scientists have been warning for more than a
  976. decade that these machines are vulnerable to hacking and can&#8217;t be
  977. meaningfully audited. States have begun moving away from paperless
  978. systems, but budget constraints have forced some to continue
  979. relying on insecure paperless equipment. The Secure Elections Act
  980. would give states grants specifically earmarked for replacing
  981. these systems with more secure systems that use voter-verified
  982. paper ballots.</p>
  983. </blockquote>
  985. <p>I don&#8217;t know of a single voting or computer security expert who is in favor of paperless voting machines. The sooner we get rid of them, the better.</p>
  987. <p><strong>Update:</strong> Electronic voting machines in the U.S. are far less regulated and <a href="">easier to rig than slot machines in Las Vegas</a>.</p>
  989. <div>
  990. <a  title="Permanent link to ‘New Bill Aims to Eliminate Paperless Voting Machines’"  href="">&nbsp;★&nbsp;</a>
  991. </div>
  993. ]]></content>
  994.  </entry><entry>
  995. <title>Regarding This Open Letter From Two Investor Groups to Apple Regarding Kids’ Use of Devices</title>
  996. <link rel="alternate" type="text/html" href="" />
  997. <link rel="shorturl" type="text/html" href="" />
  998. <link rel="related" type="text/html" href="" />
  999. <id>,2018:/linked//6.34464</id>
  1000. <published>2018-01-09T21:06:15Z</published>
  1001. <updated>2018-01-09T21:06:17Z</updated>
  1002. <author>
  1003. <name>John Gruber</name>
  1004. <uri></uri>
  1005. </author>
  1006. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1007. <p>David Gelles, reporting for The New York Times:</p>
  1009. <blockquote>
  1010.  <p>Now, two of the biggest investors on Wall Street have asked
  1011. Apple to study the health effects of its products and to make it
  1012. easier for parents to limit their children’s use of iPhones and
  1013. iPads. [&#8230;]</p>
  1015. <p>Jana, an activist hedge fund, wrote its letter with Calstrs, the
  1016. California State Teachers’ Retirement System, which manages the
  1017. pensions of California’s public-school teachers. When such
  1018. investors pressure companies to change their behavior, it is
  1019. typically with the goal of lifting a sagging stock price. In this
  1020. case, Jana and Calstrs said they were trying to raise awareness
  1021. about an issue they cared deeply about, adding that if Apple was
  1022. proactive about making changes, it could help the business.</p>
  1023. </blockquote>
  1025. <p>This open letter is getting a lot of attention, but to me, the way to limit your kids&#8217; access to devices is simply, well, to limit their access to devices. I&#8217;m sure iOS&#8217;s parental controls could be improved (and in a statement, <a href="">Apple claims they have plans to do so</a>), but more granular parental controls in iOS are no substitute for being a good, involved parent.</p>
  1027. <p><strong>See also:</strong> <a href="">the open letter from Jana and Calstrs</a>.</p>
  1029. <div>
  1030. <a  title="Permanent link to ‘Regarding This Open Letter From Two Investor Groups to Apple Regarding Kids&#8217; Use of Devices’"  href="">&nbsp;★&nbsp;</a>
  1031. </div>
  1033. ]]></content>
  1034.  </entry><entry>
  1035. <title>AT&amp;T Drops Huawei’s New Smartphone Amid Security Worries</title>
  1036. <link rel="alternate" type="text/html" href="" />
  1037. <link rel="shorturl" type="text/html" href="" />
  1038. <link rel="related" type="text/html" href="" />
  1039. <id>,2018:/linked//6.34463</id>
  1040. <published>2018-01-09T20:50:18Z</published>
  1041. <updated>2018-01-09T20:50:20Z</updated>
  1042. <author>
  1043. <name>John Gruber</name>
  1044. <uri></uri>
  1045. </author>
  1046. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1047. <p>Paul Mozur, reporting for The New York Times:</p>
  1049. <blockquote>
  1050.  <p>AT&amp;T walked away from a deal to sell the Huawei smartphone, the
  1051. Mate 10, to customers in the United States just before the
  1052. partnership was set to be unveiled, said two people on Tuesday
  1053. familiar with the plans, who spoke on the condition of anonymity
  1054. because the discussions were not public. The Wall Street Journal
  1055. reported earlier that AT&amp;T had changed plans.</p>
  1057. <p>The reasons that led to AT&amp;T’s shift were not entirely clear. But
  1058. last month, a group of lawmakers wrote a letter to the Federal
  1059. Communications Commission expressing misgivings about a potential
  1060. deal between Huawei and an unnamed American telecommunications
  1061. company to sell its consumer products in the United States. It
  1062. cited longstanding concerns among some lawmakers about what they
  1063. said are Huawei’s ties to the Chinese government.</p>
  1065. <p>The letter, which was reviewed by The New York Times, said
  1066. Congress has “long been concerned about Chinese espionage in
  1067. general, and Huawei’s role in that espionage in particular.”</p>
  1068. </blockquote>
  1070. <p>This sounds bad, but without any specific accusations regarding what Huawei might actually be doing to collaborate with the Chinese government &#8212; let alone actual evidence &#8212; I&#8217;m not sure what to make of this.</p>
  1072. <div>
  1073. <a  title="Permanent link to ‘AT&amp;T Drops Huawei’s New Smartphone Amid Security Worries’"  href="">&nbsp;★&nbsp;</a>
  1074. </div>
  1076. ]]></content>
  1077.  </entry><entry>
  1078. <title>Ad Tracking Companies Complain About Safari’s Intelligent Tracking Prevention</title>
  1079. <link rel="alternate" type="text/html" href="" />
  1080. <link rel="shorturl" type="text/html" href="" />
  1081. <link rel="related" type="text/html" href="" />
  1082. <id>,2018:/linked//6.34462</id>
  1083. <published>2018-01-09T18:41:44Z</published>
  1084. <updated>2018-01-10T00:50:14Z</updated>
  1085. <author>
  1086. <name>John Gruber</name>
  1087. <uri></uri>
  1088. </author>
  1089. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1090. <p>Alex Hern, in a decidedly-pro-ad-industry report for The Guardian:</p>
  1092. <blockquote>
  1093.  <p>Internet advertising firms are losing hundreds of millions of
  1094. dollars following the introduction of a new privacy feature from
  1095. Apple that prevents users from being tracked around the web.</p>
  1097. <p>Advertising technology firm Criteo, one of the largest in the
  1098. industry, says that the Intelligent Tracking Prevention (ITP)
  1099. feature for Safari, which holds 15% of the global browser market,
  1100. is likely to cut its 2018 revenue by more than a fifth compared to
  1101. projections made before ITP was announced.</p>
  1103. <p>With annual revenue in 2016 topping $730m, the overall cost of the
  1104. privacy feature on just one company is likely to be in the
  1105. hundreds of millions of dollars.</p>
  1106. </blockquote>
  1108. <p>If this is accurate, it goes to show the outsize influence Safari has. Criteo is claiming that a new feature in Safari, a browser with only 15 percent of global share, resulted in more than a 20 percent drop in their revenue. This, despite the fact that Intelligent Tracking Prevention &#8212; the feature in question &#8212; doesn&#8217;t block ads per se. It only prevents certain methods of privacy-invasive tracking. I fail to see how this is a bad thing.</p>
  1110. <div>
  1111. <a  title="Permanent link to ‘Ad Tracking Companies Complain About Safari&#8217;s Intelligent Tracking Prevention’"  href="">&nbsp;★&nbsp;</a>
  1112. </div>
  1114. ]]></content>
  1115.  </entry><entry>
  1116. <title>What Spectre and Meltdown Mean for WebKit</title>
  1117. <link rel="alternate" type="text/html" href="" />
  1118. <link rel="shorturl" type="text/html" href="" />
  1119. <link rel="related" type="text/html" href="" />
  1120. <id>,2018:/linked//6.34460</id>
  1121. <published>2018-01-09T01:13:50Z</published>
  1122. <updated>2018-01-09T01:19:08Z</updated>
  1123. <author>
  1124. <name>John Gruber</name>
  1125. <uri></uri>
  1126. </author>
  1127. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1128. <p>Great explanation from Filip Pizlo on the Spectre and Meltdown-related changes that have shipped (and will ship) in WebKit. Includes a pretty good overview of how the Spectre exploit works.</p>
  1130. <div>
  1131. <a  title="Permanent link to ‘What Spectre and Meltdown Mean for WebKit’"  href="">&nbsp;★&nbsp;</a>
  1132. </div>
  1134. ]]></content>
  1135.  </entry><entry>
  1136. <title>How Meltdown and Spectre Were Independently Discovered by Four Research Teams at Once</title>
  1137. <link rel="alternate" type="text/html" href="" />
  1138. <link rel="shorturl" type="text/html" href="" />
  1139. <link rel="related" type="text/html" href="" />
  1140. <id>,2018:/linked//6.34459</id>
  1141. <published>2018-01-08T23:54:14Z</published>
  1142. <updated>2018-01-08T23:56:05Z</updated>
  1143. <author>
  1144. <name>John Gruber</name>
  1145. <uri></uri>
  1146. </author>
  1147. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1148. <p>Great piece by Andy Greenberg for Wired:</p>
  1150. <blockquote>
  1151.  <p>Yet when Intel responded to the trio&#8217;s warning &#8212; after a long week of silence &#8212; the company gave them a surprising response. Though Intel was indeed working on a fix, the Graz team wasn&#8217;t the first to tell the chip giant about the vulnerability. In fact, two other research teams had beaten them to it. Counting another, related technique that would come to be known as Spectre, Intel told the researchers they were actually the <em>fourth</em> to report the new class of attack, all within a period of just months.</p>
  1153. <p>&#8220;As far as I can tell it’s a crazy coincidence,&#8221; says Paul Kocher, a well-known security researcher and one of the two people who independently reported the distinct but related Spectre attack to chipmakers. &#8220;The two threads have no commonality,&#8221; he adds. &#8220;There’s no reason someone couldn’t have found this years ago instead of today.&#8221;</p>
  1154. </blockquote>
  1156. <div>
  1157. <a  title="Permanent link to ‘How Meltdown and Spectre Were Independently Discovered by Four Research Teams at Once’"  href="">&nbsp;★&nbsp;</a>
  1158. </div>
  1160. ]]></content>
  1161.  </entry><entry>
  1162. <title>90Fun’s Puppy 1 Auto-Following Suitcase Won’t Stop Falling Over</title>
  1163. <link rel="alternate" type="text/html" href="" />
  1164. <link rel="shorturl" type="text/html" href="" />
  1165. <link rel="related" type="text/html" href="" />
  1166. <id>,2018:/linked//6.34458</id>
  1167. <published>2018-01-08T23:42:03Z</published>
  1168. <updated>2018-01-09T17:26:32Z</updated>
  1169. <author>
  1170. <name>John Gruber</name>
  1171. <uri></uri>
  1172. </author>
  1173. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1174. <p>Natt Garun, reporting for The Verge from CES:</p>
  1176. <blockquote>
  1177.  <p>Last week, 90Fun <a href="">announced an autonomous suitcase</a> that uses
  1178. Segway’s self-balancing technology and a remote control to follow
  1179. you around, leaving your hands free. We took 90Fun’s Puppy 1
  1180. suitcase for a spin at CES, and it’s clear that the vision of
  1181. hassle-free travel is still some ways away.</p>
  1183. <p>We were only able to play with a prototype of the Puppy 1, which
  1184. means that the design is not yet final.</p>
  1185. </blockquote>
  1187. <p>You&#8217;ve got to watch the video. It&#8217;s mind-boggling that this was deemed ready to demonstrate publicly. This is like a parody of bad CES demos.</p>
  1189. <div>
  1190. <a  title="Permanent link to ‘90Fun’s Puppy 1 Auto-Following Suitcase Won’t Stop Falling Over’"  href="">&nbsp;★&nbsp;</a>
  1191. </div>
  1193. ]]></content>
  1194.  </entry><entry>
  1195. <title>Pharmaceutical Ads in the U.S.</title>
  1196. <link rel="alternate" type="text/html" href="" />
  1197. <link rel="shorturl" type="text/html" href="" />
  1198. <link rel="related" type="text/html" href="" />
  1199. <id>,2018:/linked//6.34457</id>
  1200. <published>2018-01-08T23:30:19Z</published>
  1201. <updated>2018-01-08T23:30:21Z</updated>
  1202. <author>
  1203. <name>John Gruber</name>
  1204. <uri></uri>
  1205. </author>
  1206. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1207. <p>From Harper&#8217;s Index for January:</p>
  1209. <blockquote>
  1210.  <p>Amount the US pharmaceutical industry spent in 2016 on ads for prescription drugs: $6,400,000,000</p>
  1212. <p>Number of countries in which direct-to-consumer pharmaceutical ads are legal: 2</p>
  1213. </blockquote>
  1215. <div>
  1216. <a  title="Permanent link to ‘Pharmaceutical Ads in the U.S.’"  href="">&nbsp;★&nbsp;</a>
  1217. </div>
  1219. ]]></content>
  1220.  </entry><entry>
  1221. <title>Electronic Toymaker VTech Settles for $650,000 With FTC Over Children’s Privacy Suit</title>
  1222. <link rel="alternate" type="text/html" href="" />
  1223. <link rel="shorturl" type="text/html" href="" />
  1224. <link rel="related" type="text/html" href="" />
  1225. <id>,2018:/linked//6.34456</id>
  1226. <published>2018-01-08T22:39:07Z</published>
  1227. <updated>2018-01-09T17:50:12Z</updated>
  1228. <author>
  1229. <name>John Gruber</name>
  1230. <uri></uri>
  1231. </author>
  1232. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1233. <p>Shannon Liao, reporting for The Verge:</p>
  1235. <blockquote>
  1236.  <p>The Federal Trade Commission said today that the electronic
  1237. toymaker VTech Electronics has <a href="">agreed to settle for a fine of
  1238. $650,000</a>, to be paid within the next seven days, after
  1239. charges that it violated children’s privacy. The Hong Kong-based
  1240. VTech is also the parent company of LeapFrog, a popular brand for
  1241. educational entertainment for children.</p>
  1243. <p>The FTC alleges that VTech collected “personal information of
  1244. hundreds of thousands of children” through its KidiConnect mobile
  1245. app “without providing direct notice and obtaining their parent’s
  1246. consent.” The personal information included children’s first and
  1247. last names, email addresses, date of birth, and genders. VTech
  1248. also allegedly stated in its privacy policy that such data would
  1249. be encrypted, but did not actually encrypt any of it. [&#8230;]</p>
  1251. <p>The settlement dates back to the 2015 data breach that VTech
  1252. suffered. By November 2015, about 2.25 million parents had
  1253. registered and created accounts on VTech’s platform for almost 3
  1254. million children. At the same time, VTech was informed by media
  1255. that a hacker had accessed its computer network and children’s
  1256. personal information.</p>
  1257. </blockquote>
  1259. <p>$650K is a slap on the wrist for a company <a href="">with billions of dollars in annual revenue</a>.</p>
  1261. <div>
  1262. <a  title="Permanent link to ‘Electronic Toymaker VTech Settles for $650,000 With FTC Over Children’s Privacy Suit’"  href="">&nbsp;★&nbsp;</a>
  1263. </div>
  1265. ]]></content>
  1266.  </entry><entry>
  1267. <link rel="alternate" type="text/html" href=";utm_medium=text&amp;utm_campaign=2018-02" />
  1268. <link rel="shorturl" href="" />
  1269. <link rel="related" type="text/html" href="" />
  1270. <id>,2018:/feeds/sponsors//11.34461</id>
  1271. <author><name>Daring Fireball Department of Commerce</name></author>
  1272. <published>2018-01-08T22:00:28-05:00</published>
  1273. <updated>2018-01-08T22:00:30-05:00</updated>
  1274. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1275. <p>Support your users and their Apple devices without help from IT.</p>
  1277. <p>Jamf Now is a simple device management solution designed to help anyone set up, manage, and protect Apple devices at work. Easily configure email and Wi-Fi networks, distribute apps to your team, and protect sensitive data without locking down devices.</p>
  1279. <p>LATEST FEATURE:</p>
  1281. <ul>
  1282. <li>OS Updates: Keep your Apple devices running the latest versions of iOS and macOS by initiating OS Updates with Jamf Now.</li>
  1283. </ul>
  1285. <p><a href=";utm_medium=text&amp;utm_campaign=2018-02">Daring Fireball readers can create an account and manage three devices for free</a>. Forever. Each additional device is just $2 per month. <a href=";utm_medium=text&amp;utm_campaign=2018-02">Create your free account today</a>.</p>
  1287. <div>
  1288. <a  title="Permanent link to ‘Jamf Now’"  href="">&nbsp;★&nbsp;</a>
  1289. </div>
  1291. ]]></content>
  1292. <title>[Sponsor] Jamf Now</title></entry><entry>
  1293. <title>Goodbye Android Pay, Hello Google Pay</title>
  1294. <link rel="alternate" type="text/html" href="" />
  1295. <link rel="shorturl" type="text/html" href="" />
  1296. <link rel="related" type="text/html" href="" />
  1297. <id>,2018:/linked//6.34455</id>
  1298. <published>2018-01-08T20:33:11Z</published>
  1299. <updated>2018-01-08T22:34:05Z</updated>
  1300. <author>
  1301. <name>John Gruber</name>
  1302. <uri></uri>
  1303. </author>
  1304. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1305. <p>Pali Bhat, writing on the official Google blog:</p>
  1307. <blockquote>
  1308.  <p>Today, we’re excited to announce we’ll be bringing together all
  1309. the different ways to pay with Google, including Android Pay and
  1310. Google Wallet, into a single brand: Google Pay.</p>
  1311. </blockquote>
  1313. <p>This makes sense. Or better said, I don&#8217;t think Android Pay ever made sense as a brand from Google&#8217;s perspective. &#8220;Google Pay&#8221; works as a brand anywhere, on any device.</p>
  1315. <p>It seems to me that Google is stepping away from promoting Android as a brand, period. Take a look at <a href="">the web page for the Pixel 2 phones</a> and search for &#8220;Android&#8221;. I see one match, and it&#8217;s a small print footnote.</p>
  1317. <div>
  1318. <a  title="Permanent link to ‘Goodbye Android Pay, Hello Google Pay’"  href="">&nbsp;★&nbsp;</a>
  1319. </div>
  1321. ]]></content>
  1322.  </entry><entry>
  1323. <title>How to Take a Picture of a Stealth Bomber Over the Rose Bowl</title>
  1324. <link rel="alternate" type="text/html" href="" />
  1325. <link rel="shorturl" type="text/html" href="" />
  1326. <link rel="related" type="text/html" href="" />
  1327. <id>,2018:/linked//6.34454</id>
  1328. <published>2018-01-08T20:19:43Z</published>
  1329. <updated>2018-01-08T20:19:46Z</updated>
  1330. <author>
  1331. <name>John Gruber</name>
  1332. <uri></uri>
  1333. </author>
  1334. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1335. <p>Fascinating interview by Alexis Madrigal with aerial photographer Mark Holtzman:</p>
  1337. <blockquote>
  1338.  <p>Madrigal: So that’s the picture as you took it right out of the
  1339. camera, or did you have to crop it?</p>
  1341. <p>Hotlzman: I always crop it a little. I had to rotate it a little.
  1342. In the uncropped version, I had the whole stadium, plus some of
  1343. the parking lot. Unlike film, the way you shoot digital is you
  1344. shoot wider and crop it in. It’s hard. Things are happening really
  1345. quick. It’s very fluid. I’m flying at 100 miles per hour. They are
  1346. flying 200 miles an hour in the other [direction]. So, that’s 300
  1347. miles per hour. Things happen really quickly.</p>
  1348. </blockquote>
  1350. <p>Just an incredible photograph.</p>
  1352. <div>
  1353. <a  title="Permanent link to ‘How to Take a Picture of a Stealth Bomber Over the Rose Bowl’"  href="">&nbsp;★&nbsp;</a>
  1354. </div>
  1356. ]]></content>
  1357.  </entry><entry>
  1358. <title>Aaptiv</title>
  1359. <link rel="alternate" type="text/html" href=";utm_medium=DARINGFIREBALL&amp;utm_campaign=2018NewYears" />
  1360. <link rel="shorturl" type="text/html" href="" />
  1361. <link rel="related" type="text/html" href="" />
  1362. <id>,2018:/linked//6.34453</id>
  1363. <published>2018-01-07T00:07:29Z</published>
  1364. <updated>2018-01-07T00:07:31Z</updated>
  1365. <author>
  1366. <name>John Gruber</name>
  1367. <uri></uri>
  1368. </author>
  1369. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1370. <p>My thanks to Aaptiv for sponsoring this week&#8217;s DF RSS feed. Aaptiv provides you with highly effective audio-based workouts by certified trainers paired with amazing music. You need two things in your ears when you work out &#8212; instructions and music. Aaptiv gives you both, in one app.</p>
  1372. <p>If your New Year&#8217;s resolutions include getting in better shape, you should check out Aaptiv. They&#8217;ve got a New Year&#8217;s sale right now, and you can start with a free trial.</p>
  1374. <div>
  1375. <a  title="Permanent link to ‘Aaptiv’"  href="">&nbsp;★&nbsp;</a>
  1376. </div>
  1378. ]]></content>
  1379.  </entry><entry>
  1380. <title>Panic to Suspend Sales of Transmit for iOS</title>
  1381. <link rel="alternate" type="text/html" href="" />
  1382. <link rel="shorturl" type="text/html" href="" />
  1383. <link rel="related" type="text/html" href="" />
  1384. <id>,2018:/linked//6.34452</id>
  1385. <published>2018-01-05T22:14:55Z</published>
  1386. <updated>2018-01-06T21:59:41Z</updated>
  1387. <author>
  1388. <name>John Gruber</name>
  1389. <uri></uri>
  1390. </author>
  1391. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1392. <p>Panic co-founder Cabel Sasser:</p>
  1394. <blockquote>
  1395.  <p>Transmit iOS made about $35k in revenue in the last year,
  1396. representing a minuscule fraction of our overall 2017 app revenue.
  1397. That’s not enough to cover even a half-time developer working on
  1398. the app. And the app needs full-time work &#8212; we’d love to be
  1399. adding all of the new protocols we added in Transmit 5, as well as
  1400. some dream features, but the low revenue would render that effort
  1401. a guaranteed money-loser. Also, paid upgrades are still a matter
  1402. of great debate and discomfort in the iOS universe, so the
  1403. normally logical idea of a paid “Transmit 2 for iOS” would be
  1404. unlikely to help. Finally, the new Files app in iOS 10 overlaps a
  1405. lot of file-management functionality Transmit provides, and feels
  1406. like a more natural place for that functionality. It all leads to
  1407. one hecka murky situation.</p>
  1409. <p>Was the use case for this app too edge-casey or advanced? Did we
  1410. overestimate the amount of file management people want to do on a
  1411. portable device? Should we have focused more on document viewing
  1412. capabilities? Maybe all of the above?</p>
  1414. <p>My optimistic take: we hope that as iOS matures, and more and more
  1415. pro users begin to seriously consider the iPad as a legitimate
  1416. part of their daily work routines, Transmit iOS can one day return
  1417. and triumph like it does on the Mac.</p>
  1418. </blockquote>
  1420. <p>The good news is that this does not affect <a href="">Coda for iOS</a>, which includes full-featured remote file management. But it&#8217;s an interesting contrast to <a href="">Apple&#8217;s announcement today</a> of record-breaking App Store revenue. iOS is a vastly bigger platform, but high-quality apps that you pay for to use for work still do better on the Mac. Sure makes me wonder just how much of App Store revenue is from games.</p>
  1422. <div>
  1423. <a  title="Permanent link to ‘Panic to Suspend Sales of Transmit for iOS’"  href="">&nbsp;★&nbsp;</a>
  1424. </div>
  1426. ]]></content>
  1427.  </entry><entry>
  1428. <title>Jason Snell on the iMac Pro’s Groundbreaking T2 Chip</title>
  1429. <link rel="alternate" type="text/html" href="" />
  1430. <link rel="shorturl" type="text/html" href="" />
  1431. <link rel="related" type="text/html" href="" />
  1432. <id>,2018:/linked//6.34451</id>
  1433. <published>2018-01-05T21:25:43Z</published>
  1434. <updated>2018-01-05T21:29:19Z</updated>
  1435. <author>
  1436. <name>John Gruber</name>
  1437. <uri></uri>
  1438. </author>
  1439. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1440. <p>Jason Snell, writing at Macworld:</p>
  1442. <blockquote>
  1443.  <p>This new boot process means there’s also a new utility for Mac
  1444. users to get to know: <a href="">Startup Security Utility</a>, which you can only
  1445. access by booting into Recovery mode by holding down Command-R
  1446. while starting up. Startup Security Utility gives the T2 guidance
  1447. about just how strict it should be when judging whether it should
  1448. boot your computer.</p>
  1450. <p>By default, security is set to Full, which means that only the
  1451. current operating system or another OS version signed and trusted
  1452. by Apple &#8212; meaning it hasn’t been tampered with in any way &#8212; can
  1453. be booted by the computer. This version requires a network
  1454. connection when you attempt to install any OS software updates,
  1455. because it needs to verify with Apple that the updates are
  1456. legitimate. You can also set the security level lower, to Medium
  1457. (which allows older version of macOS to run regardless of Apple’s
  1458. level of trust), or turn the feature off entirely, emulating the
  1459. way all other Macs currently start up.</p>
  1461. <p>(This goes for Boot Camp, too &#8212; the T2 respects Microsoft’s
  1462. signing authority for Windows 10 beginning with 2017’s Fall
  1463. Creators Update, so Boot Camp users can reboot into Windows 10
  1464. while remaining fully secure.)</p>
  1465. </blockquote>
  1467. <p><strong>See also:</strong> <a href="">Timothy Perfitt&#8217;s detailed look at how SecureBoot works</a>.</p>
  1469. <div>
  1470. <a  title="Permanent link to ‘Jason Snell on the iMac Pro&#8217;s Groundbreaking T2 Chip’"  href="">&nbsp;★&nbsp;</a>
  1471. </div>
  1473. ]]></content>
  1474.  </entry><entry>
  1475. <title>App Store Continues to Grow</title>
  1476. <link rel="alternate" type="text/html" href="" />
  1477. <link rel="shorturl" type="text/html" href="" />
  1478. <link rel="related" type="text/html" href="" />
  1479. <id>,2018:/linked//6.34450</id>
  1480. <published>2018-01-05T20:58:50Z</published>
  1481. <updated>2018-01-05T20:58:51Z</updated>
  1482. <author>
  1483. <name>John Gruber</name>
  1484. <uri></uri>
  1485. </author>
  1486. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1487. <p>Apple Newsroom:</p>
  1489. <blockquote>
  1490.  <p>App Store customers around the world made apps and games a bigger
  1491. part of their holiday season in 2017 than ever before, culminating
  1492. in $300 million in purchases made on New Year’s Day 2018. During
  1493. the week starting on Christmas Eve, a record number of customers
  1494. made purchases or downloaded apps from the App Store, spending
  1495. over $890 million in that seven-day period.</p>
  1497. <p>“We are thrilled with the reaction to the new App Store and to see
  1498. so many customers discovering and enjoying new apps and games,”
  1499. said Phil Schiller, Apple’s senior vice president of Worldwide
  1500. Marketing. “We want to thank all of the creative app developers
  1501. who have made these great apps and helped to change people’s
  1502. lives. In 2017 alone, iOS developers earned $26.5 billion &#8212; more
  1503. than a 30 percent increase over 2016.”</p>
  1504. </blockquote>
  1506. <p>At the end of the same item:</p>
  1508. <blockquote>
  1509.  <p>Since the App Store launched in July 2008, iOS developers have
  1510. earned over $86 billion.</p>
  1511. </blockquote>
  1513. <p>So over 30 percent of all App Store royalties paid to developers in history came in 2017 alone.</p>
  1515. <div>
  1516. <a  title="Permanent link to ‘App Store Continues to Grow’"  href="">&nbsp;★&nbsp;</a>
  1517. </div>
  1519. ]]></content>
  1520.  </entry><entry>
  1521. <title>My Next Guest Needs No Introduction With David Letterman</title>
  1522. <link rel="alternate" type="text/html" href="" />
  1523. <link rel="shorturl" type="text/html" href="" />
  1524. <link rel="related" type="text/html" href="" />
  1525. <id>,2018:/linked//6.34449</id>
  1526. <published>2018-01-05T17:21:32Z</published>
  1527. <updated>2018-01-05T17:21:34Z</updated>
  1528. <author>
  1529. <name>John Gruber</name>
  1530. <uri></uri>
  1531. </author>
  1532. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1533. <p>First episode: January 12.</p>
  1535. <p>First guest: Barack Obama.</p>
  1537. <p>Fuckin’-A.</p>
  1539. <div>
  1540. <a  title="Permanent link to ‘My Next Guest Needs No Introduction With David Letterman’"  href="">&nbsp;★&nbsp;</a>
  1541. </div>
  1543. ]]></content>
  1544.  </entry><entry>
  1545. <title>Apple: ‘About Speculative Execution Vulnerabilities in ARM-Based and Intel CPUs’</title>
  1546. <link rel="alternate" type="text/html" href="" />
  1547. <link rel="shorturl" type="text/html" href="" />
  1548. <link rel="related" type="text/html" href="" />
  1549. <id>,2018:/linked//6.34448</id>
  1550. <published>2018-01-05T00:02:07Z</published>
  1551. <updated>2018-01-05T19:49:54Z</updated>
  1552. <author>
  1553. <name>John Gruber</name>
  1554. <uri></uri>
  1555. </author>
  1556. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1557. <p>Apple:</p>
  1559. <blockquote>
  1560.  <p>Update: Apple Watch is unaffected by both Meltdown and Spectre.</p>
  1562. <p>Security researchers have recently uncovered security issues known
  1563. by two names, Meltdown and Spectre. These issues apply to all
  1564. modern processors and affect nearly all computing devices and
  1565. operating systems. All Mac systems and iOS devices are affected,
  1566. but there are no known exploits impacting customers at this time.
  1567. Since exploiting many of these issues requires a malicious app to
  1568. be loaded on your Mac or iOS device, we recommend downloading
  1569. software only from trusted sources such as the App Store. Apple
  1570. has already released mitigations in iOS 11.2, macOS 10.13.2, and
  1571. tvOS 11.2 to help defend against Meltdown. Apple Watch is not
  1572. affected by either Meltdown or Spectre. In the coming days we plan
  1573. to release mitigations in Safari to help defend against Spectre.
  1574. We continue to develop and test further mitigations for these
  1575. issues and will release them in upcoming updates of iOS, macOS,
  1576. and tvOS.</p>
  1577. </blockquote>
  1579. <div>
  1580. <a  title="Permanent link to ‘Apple: ‘About Speculative Execution Vulnerabilities in ARM-Based and Intel CPUs’’"  href="">&nbsp;★&nbsp;</a>
  1581. </div>
  1583. ]]></content>
  1584.  </entry><entry>
  1585. <title>Correction of the Year</title>
  1586. <link rel="alternate" type="text/html" href="" />
  1587. <link rel="shorturl" type="text/html" href="" />
  1588. <link rel="related" type="text/html" href="" />
  1589. <id>,2018:/linked//6.34447</id>
  1590. <published>2018-01-04T22:52:35Z</published>
  1591. <updated>2018-01-04T22:52:38Z</updated>
  1592. <author>
  1593. <name>John Gruber</name>
  1594. <uri></uri>
  1595. </author>
  1596. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1597. <p>From a Politico report by Eliana Johnson on the rupture of Donald Trump&#8217;s relationship with his former campaign chairman and his preferred pick for original chief of staff, Steve Bannon:</p>
  1599. <blockquote>
  1600.  <p>Since then, however, most of the fights that Bannon has engaged in
  1601. have pitted him against the Trump White House. Though he has cast
  1602. himself as the ultimate loyalist &#8212; an indispensable translator of
  1603. the political sentiments of the Trump base &#8212; it became
  1604. increasingly clear, in recent months, that he and the president
  1605. had different interests and that Bannon would, when necessary,
  1606. work to thwart the president, and vice versa.</p>
  1608. <p>Back at the helm of Breitbart News, for example, he endorsed Roy
  1609. Moore in the Alabama Senate primary while the president backed
  1610. appointed incumbent Sen. Luther Strange. He blamed the president’s
  1611. decision on lobbying efforts by Kushner, whom he privately
  1612. referred to as “Fredo,” the traitorous brother of <em>The Godfather</em>.</p>
  1613. </blockquote>
  1615. <p><a href="">Josh Rogin</a>:</p>
  1617. <blockquote>
  1618.  <p>FUNNY CORRECTION: An earlier version of the story misidentified
  1619. the fictional character name Bannon uses to refer to Jared Kushner
  1620. as Frodo, a “Lord of the Rings” reference, rather than Fredo, a
  1621. reference to “The Godfather.”</p>
  1622. </blockquote>
  1624. <p>It&#8217;s hard to overstate the gaping chasm between Frodo &#8212; a noble, heroic figure &#8212; and Fredo Corleone. Describing Fredo merely as &#8220;traitorous&#8221; is euphemistic &#8212; Fredo was weak, ineffective, oblivious, <a href="">and stupid</a>, too.</p>
  1626. <div>
  1627. <a  title="Permanent link to ‘Correction of the Year’"  href="">&nbsp;★&nbsp;</a>
  1628. </div>
  1630. ]]></content>
  1631.  </entry><entry>
  1632. <title>Fans of the Fat Nano Unite</title>
  1633. <link rel="alternate" type="text/html" href="" />
  1634. <link rel="shorturl" type="text/html" href="" />
  1635. <link rel="related" type="text/html" href="" />
  1636. <id>,2018:/linked//6.34446</id>
  1637. <published>2018-01-04T20:56:54Z</published>
  1638. <updated>2018-01-05T00:26:19Z</updated>
  1639. <author>
  1640. <name>John Gruber</name>
  1641. <uri></uri>
  1642. </author>
  1643. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1644. <p>On Tuesday, in an aside regarding Rick Tetzeli&#8217;s description of the original iPod click wheel as &#8220;clunky&#8221;, <a href="">I wrote</a>:</p>
  1646. <blockquote>
  1647.  <p>Also, a personal niggle: I don’t think there was anything “clunky”
  1648. about the original iPod scroll wheel. In fact, I liked the
  1649. original iPod’s mechanical scroll wheel, which physically spun,
  1650. better than the capacitive touch scroll wheel that replaced it.
  1651. From a Mac user’s perspective, the original iPod was an amazing
  1652. device. If you want something from iPod history to cite as an
  1653. example of questionable Apple design, I suggest either <a href="">the 2007
  1654. “Fat” Nano</a> or <a href="">the 2009 iPod Shuffle</a> that literally had
  1655. no playback buttons at all.</p>
  1656. </blockquote>
  1658. <p>I heard from a bunch of readers — <a href="">including good friends</a> — who objected to my disparagement of the Fat Nano. I didn&#8217;t mean to imply no one loved it, though. Only that it was widely criticized on aesthetic grounds, and wound up lasting for just one year. Someone must have liked it at Apple too, otherwise it wouldn&#8217;t have shipped. I even heard from at least one reader who liked the no-button Shuffle. The iPod line was so good, and so well-designed, that it&#8217;s hard to say any of them exhibited &#8220;bad design&#8221;.</p>
  1660. <p>Even the much-derided 1998 <a href=";t=osx&amp;iax=images&amp;ia=images">hockey puck mouse</a> that debuted with the original iMac has fans (including my wife).</p>
  1662. <div>
  1663. <a  title="Permanent link to ‘Fans of the Fat Nano Unite’"  href="">&nbsp;★&nbsp;</a>
  1664. </div>
  1666. ]]></content>
  1667.  </entry><entry>
  1669.    <link rel="alternate" type="text/html" href="" />
  1670. <link rel="shorturl" href="" />
  1671. <id>,2017://1.34429</id>
  1672. <published>2017-12-29T03:18:26Z</published>
  1673. <updated>2018-01-09T01:34:17Z</updated>
  1674. <author>
  1675. <name>John Gruber</name>
  1676. <uri></uri>
  1677. </author>
  1678. <summary type="text">People naturally expect everything they do on an iPhone to be done on screen.</summary>
  1679. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1680. <p>Occasionally I notice a burst of traffic to Daring Fireball from Hacker News. It&#8217;s always short-lived, because for reasons I&#8217;ve never seen explained, Daring Fireball articles <em>always</em> get blacklisted from Hacker News once they hit their front page. It&#8217;s apparent that a lot of HN readers do not like my work on the basis that they see me as a shameless Apple shill, but it&#8217;s a shame the articles get deleted because I like reading the comments. I feel like it keeps me on my toes to read the comments from people who don&#8217;t like Daring Fireball.</p>
  1682. <p>Even after being blacklisted from the Hacker News homepage, though, the comment threads still exist. I went through <a href="">the Hacker News comments on my iPhone X review</a> today, and a few comments about how Apple Pay works on the iPhone X caught my attention:</p>
  1684. <p>arielm:</p>
  1686. <blockquote>
  1687.  <p>Apple made some interactions so unintuitive that even I was
  1688. confused. One example is purchasing an app. Pre-X, you’d tap the
  1689. “get” button and place your finger on the home button or enter
  1690. your password. With the X you have to tap the button, look at your
  1691. device, and then follow the most unintuitive animation to actually
  1692. press the physical side button.</p>
  1693. </blockquote>
  1695. <p>nkristoffersen:</p>
  1697. <blockquote>
  1698.  <p>I&#8217;ve had the X for a few days now. The animation to press the
  1699. physical button totally had me stumped the first few times!
  1700. Overall I&#8217;m a fan (such as great camera and great screen) but some
  1701. of the new interactions are taking some getting used to.</p>
  1702. </blockquote>
  1704. <p>breatheoften:</p>
  1706. <blockquote>
  1707.  <p>Yeah the explanation for the side button tap should be considered
  1708. a straight up bug &#8212; I had to google what to do.</p>
  1709. </blockquote>
  1711. <p>These remarks caught my attention because a technically-savvy family member was confused by the same thing the first time they tried to buy an app on their new iPhone X. They showed me the phone <a href="">with the &#8220;Double Click to Pay&#8221; animation</a><sup id="fnr1-2017-12-28"><a href="#fn1-2017-12-28">1</a></sup> and asked me, &#8220;What am I supposed to double click here? It doesn&#8217;t work.&#8221; What they had tried was double tapping on the &#8220;Double Click to Pay&#8221; label on screen. When I explained that the animation was pointing to the physical side button, the proverbial light bulb turned on.</p>
  1713. <p>This is an interesting design dilemma. The reason why Apple requires you to press the physical side button to confirm a purchase with Apple Pay or in the App Store is because pressing the side button can&#8217;t be faked by an app. If it was an on-screen button, a nefarious app could present a fake Apple Pay button. With any normal app, clicking the side button once will always lock the screen, and double-clicking will put you in Apple Pay mode. Only Apple&#8217;s own software can override the side button like this. Double clicking the side button to confirm a purchase effectively guarantees that it was a legitimate payment experience.</p>
  1715. <p>But: people naturally expect everything they do on an iPhone to be done on screen. The screen <em>is</em> the phone &#8212; and that&#8217;s even more true with the iPhone X. Even with an animation pointing to the side button on screen, it doesn&#8217;t occur to people that they need to do something off-screen to authorize the transaction. They think the affordance on the side of the screen <a href=""><em>is</em> the button they&#8217;re supposed to double tap</a> (and they don&#8217;t notice the verbal distinction between &#8220;click&#8221; and &#8220;tap&#8221;).</p>
  1717. <p>I&#8217;m not sure what the solution here is, but I think Apple needs to come up with a better indication &#8212; perhaps something more explicit, the first time you encounter it &#8212; that you need to click the hardware button, not tap something on screen.</p>
  1719. <p><strong>Update:</strong> This problem is not new to Face ID. Touch ID has a similar problem. Here&#8217;s a note I got today from a friend:</p>
  1721. <blockquote>
  1722.  <p>FWIW, Touch ID has been out for four years, and I still see people
  1723. try to press the fingerprint icon that shows up in the middle of
  1724. the screen. Can’t count the number of times just in the past six
  1725. months. I don’t think the X’s initial double-click confusion is a
  1726. new problem.</p>
  1727. </blockquote>
  1729. <p><a href="">Alex fehners</a>:</p>
  1731. <blockquote>
  1732.  <p>@jtregear @daringfireball Father in law repeatedly said his Touch
  1733. ID wasn’t working. He was putting his thumb to the finger print
  1734. icon on screen rather than the home button.</p>
  1735. </blockquote>
  1737. <p><a href="">Iván Cavero Belaunde</a>:</p>
  1739. <blockquote>
  1740.  <p>@daringfireball Not entirely a new problem. First time my mom was
  1741. asked for her fingerprint for iTunes purchases with TouchID, the
  1742. thought she had to put her finger on the fingerprint on-screen
  1743. image, not on the home button.</p>
  1744. </blockquote>
  1746. <p><strong>Update 2:</strong> Some more commentary.</p>
  1748. <p><a href="">Joanna Stern</a>:</p>
  1750. <blockquote>
  1751.  <p>Yes! On-screen language just needs to be rewritten with an arrow
  1752. pointing right. I suggest: “Press the damn side button twice. It’s
  1753. on the damn right edge of the phone.”
  1754. <a href="">…</a></p>
  1755. </blockquote>
  1757. <p><a href="">John R. Kirk</a>:</p>
  1759. <blockquote>
  1760.  <p>Mock me if you will, but I went weeks without understanding how to
  1761. confirm payments on the iPhone X. I kept double-tapping the
  1762. screen. I had to google and read an article before I was able to
  1763. figure it out.</p>
  1765. <p>Apple got this UI wrong. Very wrong. <br />
  1766. <a href="">…</a></p>
  1767. </blockquote>
  1769. <p><a href="">Craig Mod</a>:</p>
  1771. <blockquote>
  1772.  <p>This was my main crit of @gruber&#8217;s otherwise great review &#8212; the
  1773. side-button double-press is really, really, really bad.
  1774. Unintuitive but more damningly &#8212; it&#8217;s not <em>fun</em>!</p>
  1776. <p>This is in large part because the
  1777. power-button-across-from-volume-rockers has always felt like a
  1778. fundamentally wrong design decision. Double-press aside, I take
  1779. 5-10 unintentional screenshots a day. At least they&#8217;re in their
  1780. own folder now.</p>
  1782. <p>The best part of the iPhone X experience really is just how fun it
  1783. feels &#8212; how it&#8217;s so totally tactile and responsive and fluid in a
  1784. way iPhones have never been.</p>
  1785. </blockquote>
  1787. <div class="footnotes">
  1788. <hr />
  1789. <ol>
  1790. <li id="fn1-2017-12-28">
  1791. <p>The thing to keep in mind <a href="">if you watch this animation</a> is that the &#8220;Double Click to Pay&#8221; animation is aligned perfectly with the hardware side button.&nbsp;<a href="#fnr1-2017-12-28"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1792. </li>
  1793. </ol>
  1794. </div>
  1798.    ]]></content>
  1799.  <title>★ Pressing the Side Button to Confirm Payments on iPhone X</title></entry><entry>
  1801.    <link rel="alternate" type="text/html" href="" />
  1802. <link rel="shorturl" href="" />
  1803. <id>,2017://1.34424</id>
  1804. <published>2017-12-28T21:51:50Z</published>
  1805. <updated>2017-12-31T03:03:23Z</updated>
  1806. <author>
  1807. <name>John Gruber</name>
  1808. <uri></uri>
  1809. </author>
  1810. <summary type="text">The funny thing about Apple is that their communication problems tend to happen only when they don’t communicate at all. This whole iPhone battery controversy erupted only because Apple had never explained what was going on, which opened them up to accusations of nefarious intent.</summary>
  1811. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1812. <p>Apple: &#8220;<a href="">A Message to Our Customers About iPhone Batteries and Performance</a>&#8221;:</p>
  1814. <blockquote>
  1815.  <p>We’ve been hearing feedback from our customers about the way we
  1816. handle performance for iPhones with older batteries and how we
  1817. have communicated that process. We know that some of you feel
  1818. Apple has let you down. We apologize. There’s been a lot of
  1819. misunderstanding about this issue, so we would like to clarify and
  1820. let you know about some changes we’re making.</p>
  1822. <p>First and foremost, we have never &#8212; and would never &#8212; do
  1823. anything to intentionally shorten the life of any Apple product,
  1824. or degrade the user experience to drive customer upgrades. Our
  1825. goal has always been to create products that our customers love,
  1826. and making iPhones last as long as possible is an important part
  1827. of that. [&#8230;]</p>
  1829. <p>To address our customers’ concerns, to recognize their loyalty and
  1830. to regain the trust of anyone who may have doubted Apple’s
  1831. intentions, we’ve decided to take the following steps:</p>
  1833. <ul>
  1834. <li><p>Apple is reducing the price of an out-of-warranty iPhone battery
  1835. replacement by $50 &#8212; from $79 to $29 &#8212; for anyone with an
  1836. iPhone 6 or later whose battery needs to be replaced, starting
  1837. in late January and available worldwide through December 2018.
  1838. Details will be provided soon on</p></li>
  1839. <li><p>Early in 2018, we will issue an iOS software update with new
  1840. features that give users more visibility into the health of
  1841. their iPhone’s battery, so they can see for themselves if its
  1842. condition is affecting performance.</p></li>
  1843. </ul>
  1844. </blockquote>
  1846. <p>This is a terrific response, both in terms of explaining what has actually been going on, and in terms of the steps they&#8217;re taking going forward. Reducing the price of authorized battery replacements to $29 is really great.</p>
  1848. <p>The upcoming update to iOS 11 with more information on the state of the device&#8217;s battery is good news too. Right now, the Battery section inside the Settings app <a href="">will warn you</a> about the state of your battery &#8212; but <em>only</em> if the battery is in truly dire condition. What iOS should do &#8212; and it sounds to me like this is what Apple plans to do &#8212; is tell you about the state of your battery as soon as its condition drops beneath the threshold at which the performance throttling features kick in.</p>
  1850. <p>The funny thing about Apple is that their communication problems tend to happen only when they don&#8217;t communicate at all. This whole iPhone battery controversy erupted only because Apple had never explained what was going on, which opened them up to accusations of nefarious intent. When they do communicate, they do so with clarity, plain language, and honesty. And, when called for &#8212; as in this case &#8212; humility.</p>
  1854.    ]]></content>
  1855.  <title>★ Apple Responds to Controversy on iPhone Batteries and Performance</title></entry><entry>
  1857.    <link rel="alternate" type="text/html" href="" />
  1858. <link rel="shorturl" href="" />
  1859. <id>,2017://1.34415</id>
  1860. <published>2017-12-27T02:36:00Z</published>
  1861. <updated>2017-12-27T19:51:50Z</updated>
  1862. <author>
  1863. <name>John Gruber</name>
  1864. <uri></uri>
  1865. </author>
  1866. <summary type="text">The iPhone X is a triumph, a delightful conceptual modernization of a ten-year-old platform that, prior to using the iPhone X, I didn’t think needed a modernization.</summary>
  1867. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1868. <p>The more popular a computer platform becomes, the more of a bind in which it inevitably finds itself. A platform is only &#8220;finished&#8221; when it is abandoned. It needs to evolve to remain relevant, but it&#8217;s difficult to change in unfamiliar ways without angering the base of active users. Adding new features on top of the familiar foundation only gets you so far &#8212; eventually things grow too complex, especially when what&#8217;s needed now is in conflict with a design decision that made sense a decade (or more) prior.</p>
  1870. <p>Eventually, inevitably, incremental improvements paint a platform into a corner. Something has to give.</p>
  1872. <p>This happened to the classic Mac OS in the mid-90s, when certain technical constraints of the OS made the platform seem anachronistic. The classic Mac OS had no protected memory and used cooperative, rather than preemptive, multitasking. No protected memory meant that every process on the system could read and write anywhere in RAM &#8212; both the memory of other processes and the memory of the OS itself. Cooperative multitasking meant that each app decided when to give up the CPU to other processes. If an app wanted to use the entire CPU, it could. In a sense, from today&#8217;s perspective, the original Mac was effectively just one process, and apps were more akin to plugins running within that process. In 1984, these were utterly reasonable design decisions. Protected memory, pre-emptive multitasking, and a powerful OS kernel just weren&#8217;t feasible on a computer with an 8 Mhz CPU and 128 kilobytes (<em>kilobytes</em>!) of RAM. In fact, there was no multitasking at all on the original Mac until Andy Hertzfeld released <a href=";story=Switcher.txt">Switcher</a> in April 1985 &#8212; the forerunner of <a href="">MultiFinder</a>.<sup id="fnr1-2017-12-26"><a href="#fn1-2017-12-26">1</a></sup></p>
  1874. <p>The problem mid-90s Apple faced is that the Mac was popular because of its thriving library of excellent third-party software, but in trouble because of the creakiness of its underlying OS. But Apple couldn&#8217;t truly modernize the OS without breaking the application software &#8212; which is exactly what happened with Mac OS X. Old software ran in a virtual <a href="">&#8220;Classic&#8221; environment</a> &#8212; essentially, a virtualized version of the old classic Mac OS running within the modern Mac OS X. New software &#8212; apps that took advantage of Mac OS X&#8217;s modern APIs, new features, and new look-and-feel &#8212; needed to be written using different (Cocoa) or updated (Carbon) APIs. The transition worked, as evidenced by the Mac&#8217;s continued success today, but it took years &#8212; arguably close to a decade. And it was a painful, jarring transition for everyone involved: users, developers, and Apple itself.</p>
  1876. <hr />
  1878. <p>With the iPhone X, Apple is attempting something I believe to be unprecedented &#8212; a complete ground-up rethinking of a fabulously popular and successful platform, <em>without</em> a disruptive, painful transition.</p>
  1880. <p>There are several parallels between the original 2007 iPhone and the original 1984 Macintosh. Both introduced new fundamental paradigms that quickly became the standards on competing platforms &#8212; the GUI in 1984, multitouch in 2007. Both were created by relatively small teams, led by Steve Jobs. But the biggest similarity &#8212; or at least the one most salient to this discussion &#8212; is that both were burdened at the outset by severe technical limitations. An 8 Mhz CPU, 128 KB of RAM, and 400 KB floppy disks (the original Mac&#8217;s only form of storage) were not enough. Likewise, the original iPhone&#8217;s CPU, 128 MB of RAM, and EDGE-based cellular networking were not enough. That both products succeeded &#8212; and became downright beloved, despite their technical limits &#8212; is testimony to the genius and talent of the designers and engineers who brought them to life.</p>
  1882. <p>There is a fundamental difference: the barrier the iPhone ran up against a decade into life wasn&#8217;t technical (as with the aforementioned architectural shortcomings of the classic Mac OS<sup id="fnr2-2017-12-26"><a href="#fn2-2017-12-26">2</a></sup>), but rather conceptual. Here are some of the landmark changes to the iPhone as a platform over its decade of existence:</p>
  1884. <ul>
  1885. <li>iPhone 4 (2010): Retina display.</li>
  1886. <li>iPhone 5 (2012): Aspect ratio changes from 3:2 to 16:9.</li>
  1887. <li>iPhone 5S (2013): Touch ID.</li>
  1888. <li>iOS 7 (2013): Cosmetic reboot of user interface.</li>
  1889. <li>iPhone 6 and 6 Plus (2014): Larger screens.</li>
  1890. </ul>
  1892. <p>Ultimately these were all evolutions of the original iPhone, though. There is a clear evolutionary path from 2007&#8217;s original iPhone to 2017&#8217;s iPad Pro and iPhone 8 models. The home button gained a superpower with the iPhone 5S &#8212; the ability to authenticate your identity by fingerprint &#8212; but only <em>in addition to</em> everything it did before. There were always two things and only two things on the front face of an iOS device &#8212; the touchscreen display and the home button. In fact, the iPhone X changes iOS in more fundamental ways than even the iPad did. In terms of the role between the display and the home button, the iPad really was &#8212; and remains today &#8212; &#8220;just a big iPhone&#8221;.</p>
  1894. <p>The iPhone X, however, creates a schism, akin to a reboot of the franchise.</p>
  1896. <p>Apple hasn&#8217;t called attention to this, but effectively there are two versions of iOS 11 &#8212; I&#8217;ll call them &#8220;iOS 11 X&#8221;, which runs only on iPhone X, and &#8220;iOS 11 Classic&#8221;, which runs on everything else.</p>
  1898. <p>The fundamental premise of iOS Classic is that a running app gets the entire display, and the home button is how you interact with the system to get out of the current app and into another. Before Touch ID, the home button was even labeled with a generic empty &#8220;app&#8221; icon, an iconographic touch of brilliance.<sup id="fnr3-2017-12-26"><a href="#fn3-2017-12-26">3</a></sup></p>
  1900. <p>Over time, the home button&#8217;s responsibilities grew to encompass these essential roles:</p>
  1902. <ul>
  1903. <li>Single-click with display off: wakes the device.</li>
  1904. <li>Single-click with display on: takes you to home screen.</li>
  1905. <li>Double-click: takes you to multitasking switcher.</li>
  1906. <li>Triple-click: configurable accessibility shortcut.</li>
  1907. <li>Rest finger: authenticate with Touch ID.</li>
  1908. <li>Double-tap (without clicking): invoke Reachability.</li>
  1909. <li>Press-and-hold: invoke Siri.</li>
  1910. </ul>
  1912. <p>In iOS 11 X, almost every role of the home button has been subsumed by the display, with the remainder reassigned to the side button:</p>
  1914. <ul>
  1915. <li>Wake the device: tap the display.</li>
  1916. <li>Go to the home screen: short swipe up from the bottom of display.</li>
  1917. <li>Go to the multitasking switcher: longer swipe up from the bottom.</li>
  1918. <li>Even better way to multitask: just swipe sideways on the home indicator.</li>
  1919. <li>Accessibility shortcut: triple-click the side button.</li>
  1920. <li>Authenticate: just look at the display.</li>
  1921. <li>Reachability: swipe down on the bottom edge of display.</li>
  1922. <li>Siri: press-and-hold side button.</li>
  1923. </ul>
  1925. <p>The first few days using an iPhone X were rocky for me. My thumb kept reaching for the home button that wasn&#8217;t there, particularly for multitasking. After a week, it started feeling normal. Today, on the cusp of two months of use, I&#8217;m like &#8220;<em>What&#8217;s a home button?</em>&#8221; In fact, my acclimation to the iPhone X has made using an iPad feel anachronistic &#8212; I want to swipe up from the bottom to go home there too. </p>
  1927. <p>In short, with the iPhone X Apple took a platform with two primary means of interacting with the apps &#8212; a touchscreen and a home button &#8212; removed one of them, and created a better, more integrated, more organic experience.</p>
  1929. <p>One of the things Apple created to enable this has gotten a lot of attention: Face ID. But a few of the other things they&#8217;ve done to enable this have gone largely under the radar. Tapping anywhere on the display to wake it is so natural, it makes me wonder how we did without it for so long. (This is another frustration I have trying to use an iPad now &#8212; I tap the screen expecting it to wake up. It seems silly that I need to press a button.) The iPhone X display does not, alas, offer <a href="">the ProMotion feature</a> introduced with the latest iPad Pros, which allows for dynamic screen refresh rates of up to 120 Hz. But it does track touch input at 120 Hz, double the rate of all other iPhones. The result of this is that the animations for gestures track your finger better. It feels less like an animation that is playing in response to your touch and more like your finger is actually manipulating and moving things on screen as though they are real objects. Of the numerous new technologies embedded in the iPhone X, the 120 Hz refresh rate for touch tracking is almost certainly the least important, but it really does contribute to making gestures feel like the one true way to interact with the system.</p>
  1931. <p>Tapping the display to wake the device, seeing a list of truncated notifications on the lock screen, and then seeing those notifications expand to preview their content once you&#8217;re recognized by Face ID &#8212; this just makes the iPhone X feel <em>alive</em> in a way that no other device does. You tap it to get its attention, and it recognizes that you are you.</p>
  1933. <p>The lock screen is far more useful now: you can just tap any notification to jump to it. With Touch ID, after you tap a particular notification in the middle of the display, you then must move your finger down to the home button to authenticate. I always found that annoying. Now that I&#8217;m used to the iPhone X, I find it to be intolerable.</p>
  1935. <p>Face ID is not a win versus Touch ID in every single way. There are trade-offs, primarily scenarios where Face ID fails. (It does seem to work with most sunglasses, for example, but not with Ray Bans, which, alas, happen to be my preferred brand.)</p>
  1937. <p>Consider the aforementioned process of opening a notification from the lock screen. Touch ID adds an extra step, every time, <em>even when it works perfectly</em>. Face ID is not perfect &#8212; it&#8217;s true that I wind up either authenticating a second time or resorting to entering my PIN more often than with Touch ID &#8212; but it only adds these extra steps <em>when it fails for some reason</em>. When it works perfectly, which for me is the vast majority of the time, the effect is sublime. It really does feel like my iPhone has no passcode protecting it. That was never true for Touch ID. Touch ID feels like a better way to unlock your device. Face ID feels like your device isn&#8217;t even locked.</p>
  1939. <p>This was the way the iPhone was meant to be used. When Steve Jobs demoed the original iPhone on stage at Macworld Expo in January 2007, it was just &#8220;slide to unlock&#8221;. There was no PIN. One of the ways the world has changed in the last decade is that we&#8217;re no longer naive about device security. I&#8217;m pretty sure I used my iPhones with no PIN code for a few years. Slide to unlock was fun. Entering a PIN is no fun.</p>
  1941. <p>Thanks to Face ID, no-PIN &#8220;slide to unlock&#8221; is back. This, to me, epitomizes the iPhone X. In ways small and large, it changes fundamental aspects of using an iPhone. But it does so in ways that are faithful to the spirit of the original iPhone.</p>
  1943. <hr />
  1945. <p>It&#8217;s the big picture that interests me most about the iPhone X. Not this device, in particular, with this particular display (which is terrific), this particular camera system (which is terrific), etc. &#8212; but the ways it changes fundamental aspects of the platform, laying the groundwork for the next decade of iterative year-over-year improvements. But some particular details of this device are worth calling attention to:</p>
  1947. <ul>
  1948. <li><p>Apple Pay moving to Face ID has been a win for me. You now trigger it by double-clicking the side button. One of the things I find interesting about this change is that while it breaks from how Apple Pay works on other iPhones, it is consistent with how you invoke Apple Pay on Apple Watch. Same thing with being able to tap the display to wake it up &#8212; it&#8217;s now the same as on Apple Watch.</p></li>
  1949. <li><p>The camera bump is bigger and more prominent than on any other iPhone, but somehow, to me, that makes it less objectionable. It’s a thing now. Whereas the first bumps, on the iPhone 6 and 6 Plus, were like blemishes. If you’re going to have a bump, have a fucking bump. I also like that the sides of the iPhone X camera bump are perpendicular to the back of the phone, not sloped. It looks less like a mere lens on the back of the phone and more like a <em>whole camera</em> on the back of the phone.</p></li>
  1950. <li><p>After a few weeks, I became annoyed by the home indicator. Making it completely white or black is perhaps a good idea for new users, to make the affordance as visually prominent as possible. But once you get used to it, its extreme visual prominence gets in the way. I wish that it were more subtle, probably translucent. I expect the home indicator to become more subtle in future versions of iOS.<sup id="fnr4-2017-12-26"><a href="#fn4-2017-12-26">4</a></sup></p></li>
  1951. <li><p>When an alarm from the built-in Clock app fires, it fades out in volume as soon as you look at the display. This is utterly charming.</p></li>
  1952. <li><p>The hardware mute switch remains. If ever there were a time when Apple might get rid of it, iPhone X would have been it. That it remains on iPhone X suggests to me that Apple sees it as here to stay, at least for the foreseeable future. If, like me, you love the mute switch, you might be thinking “<em>Well of course they kept the mute switch, it would be terrible if they got rid of it.</em>” But they removed it from the iPad a few years ago, and Apple is famously averse to physical buttons (cf. the Touch Bar on the new MacBook Pros). And for reasons I’ve never been able to understand, Android handset makers seem willing to copy everything and anything from Apple they can get away with (and even things <a href="">they can’t get away with</a>), but <a href="">almost</a> none have copied the iPhone’s mute switch, despite the fact that it’s extremely useful.</p></li>
  1953. <li><p>Stainless steel looks and feels so much more luxurious than aluminum. The iPhone X doesn&#8217;t feel bigger than an iPhone 7 or 8 in my hand or pocket, but it does feel <em>heavier</em> and more serious.</p></li>
  1954. <li><p>True Tone epitomizes the sort of feature that you stop noticing on the devices that have it, but which ruins you for devices that don&#8217;t. Retina resolution was like this, too. Since switching to the iPhone X, I&#8217;ve gone entire weeks without once thinking about True Tone at all. But if I pick up or glance at an iPhone without it, I&#8217;m skeeved out.</p></li>
  1955. <li><p>One of the best ways to judge iPhone X after using it for a few weeks is to go back to an iPhone 7 (or any other previous iPhone). Things I notice instantly: the display looks very small, the colors look too cool at night (because of the aforementioned lack of True Tone), and the perfectly square corners of the display seem downright crude. The round display corners seemed like something that might feel gimmicky, but in practice, they feel organic and refined. As a wise man once pointed out, <a href="">rectangles with round corners are everywhere</a>. As with True Tone, I stopped noticing the round corners on the iPhone X, but started noticing and being annoyed by the square corners on other iOS devices.</p></li>
  1956. <li><p>I don&#8217;t notice the notch when using the phone in portrait orientation, and I only hold the phone in landscape when watching video, using the camera, or playing a game. And I don&#8217;t play many games. But Apple really should hide the notch in landscape (which, in fact, they do for the Camera app). Last week I was playing <a href="">Desert Golfing</a><sup id="fnr5-2017-12-26"><a href="#fn5-2017-12-26">5</a></sup> &#8212; a game that&#8217;s been updated to embrace the notch &#8212; and on one hole my ball went to the edge of the display and was hidden by the notch. I &#8220;fixed&#8221; it by rotating the phone 180 degrees to put the notch on the other side, but that&#8217;s ridiculous.</p></li>
  1957. <li><p>The chins and foreheads on other iPhones now stick out to me far more than the notch on the X. They just scream &#8220;<em>Wasted space!</em>&#8221; to me.</p></li>
  1958. <li><p>On the iPhone X, iOS 11 now uses small colored pill-shaped indicators in the top left &#8220;ear&#8221; when the phone is hosting an active hotspot session (blue), there&#8217;s an active mapping navigation session (blue), there&#8217;s a phone call in the background (green), or the screen is being recorded (red). With iOS Classic, these indicators use the same colors, but they take up the entirety of the status bar. The old design for these indicators gave them too much visual prominence, and completely prevented you from tapping the status bar to scroll the current view to the top. It never made any sense that you couldn&#8217;t use the scroll-to-top shortcut just because one of these indicators was active &#8212; every time I ran into that, it would occur to me that it was a clumsy design. On iPhone X these indicators finally feel like they have a proper home.</p></li>
  1959. <li><p>The new status bar no longer has room for the numeric battery percentage. You can see the numeric percentage in Control Center, and on the lock screen while the device is charging, but there is no option for an always-on numeric battery percentage. I&#8217;ve never been a fan of the numeric battery percentage &#8212; to me, all it does is induce anxiety. The approximation of remaining battery life gleanable from the icon is all you need most of the time, I say. But, <a href="">some people disagree</a>. If this remains controversial, Apple should consider letting people choose between the icon and the numeric percentage.</p></li>
  1960. <li><p>The new status bar design also gets the name of your carrier off the screen most of the time. (It&#8217;s still visible from the lock screen and from Control Center.) The carrier string in the status bar has always irritated me &#8212; it&#8217;s like they were getting an ad on my screen, even though I&#8217;m the one paying them.</p></li>
  1961. <li><p>The glass back of the iPhone X does not pick up scratches or &#8220;<a href="">micro-abrasions</a>&#8221; like the jet black iPhone 7 does. I see two small, very fine micro-abrasions on mine (a space gray model), which I&#8217;ve been using for well over a month without any sort of case. My wife&#8217;s (a white model) has a few too. You have to look hard to see them, though. </p></li>
  1962. <li><p>I still think iPhone X is too big to be the smallest iPhone. The device doesn&#8217;t feel too big in hand or pocket. As someone who has carried a 4.7-inch iPhone ever since the iPhone 6 three years ago, the iPhone X really does feel the same size, as a device. But the extra screen size from the edge-to-edge display <a href="">puts a serious crimp in one-handed reachability</a>. In addition to an even bigger Plus-sized version of iPhone X next year, I would love to see Apple introduce a smaller iPhone SE-sized phone with all the same features and design elements. I&#8217;m not holding my breath, but I&#8217;d love to see it. I&#8217;m not even saying I personally would prefer it (but I&#8217;d give it a try) &#8212; but it would be great for people who value one-handed reachability.</p></li>
  1963. <li><p>Is the higher price of the iPhone X over the iPhones 8 justified? The 64 and 256 GB iPhone X models cost $999 and $1149, respectively. That&#8217;s $300 more than the equivalent iPhone 8, and $200 than an iPhone 8 Plus. For that premium, you get a better camera, stainless steel (rather than aluminum) frame, an edge-to-edge OLED display with True Tone, and Face ID. But you also get something you can&#8217;t compare in <a href="">a checkmark comparison</a> &#8212; a sort of <em>joie de vivre</em>. Critics of the iPhone X&#8217;s higher prices seem to me to be arguing not that <em>this</em> phone shouldn&#8217;t cost so much, but rather that <em>no</em> phone should. <a href="">As I argued earlier this year</a>, if we have laptops and tablets that cost more than $1000, why not phones too? Especially considering that for many, the phone is the most-used, most-important device in either or both their personal and professional lives.</p></li>
  1964. </ul>
  1966. <hr />
  1968. <p>I don&#8217;t recall a single review of the iPhones 8 that didn&#8217;t mention the much-more-highly-anticipated iPhone X (including <a href="">my own review</a>). But you can&#8217;t understand iPhone X without mentioning iPhone 8, either. A few months after the iPad debuted in 2010, I wrote &#8212; trying to assuage the fears of those who saw the iPad as the end of the Mac &#8212; <a href="">that the heaviness of the Mac allows iOS to remain conceptually light</a>. In a similar vein, the familiarity of iPhone 8 allows iPhone X to reinvent anything, to break the platform&#8217;s foundational conventions.</p>
  1970. <p>No one is being forced to adapt to the changes of iPhone X. If you want a new iPhone that is familiar, you can get an iPhone 8 or 8 Plus with the same A11 &#8220;Bionic&#8221; system on a chip, a camera that is <em>almost</em> as good, a display that is <em>almost</em> as good, the tried and true Touch ID, and even new (to the iPhone platform) features like inductive charging &#8212; and you&#8217;ll save a few hundred dollars.</p>
  1972. <p>In the short term this fork in the platform is a hit to consistency. Unlocking the phone, going to the home screen, switching between apps, authenticating via biometrics, invoking Siri, taking screenshots, powering down the device &#8212; all of these tasks are accomplished in completely different ways on the iPhone X than any other iPhone to date, including the iPhones 8.</p>
  1974. <p>It’s unique in Apple history &#8212; if not all of consumer computing history &#8212; for the same version of the OS to present two distinct interfaces that are so markedly different, based solely on which hardware the OS is running. From a developer standpoint, iOS 11 is one OS with various different sizes (SE, regular, Plus, X, iPad, iPad Pro) and layouts. From a user perspective, though, the “OS” is how you interact with the system. Again, it’s as though there are two very different versions of iOS 11 &#8212; and I can&#8217;t stop thinking about how weird that is.</p>
  1976. <p>It’s nowhere near as different switching from an older iPhone to an iPhone X as it is switching from an iPhone to any Android device, for example. But it is different, at a fundamental level.</p>
  1978. <p>Why not bring more of what&#8217;s different on iPhone X to the other iPhones running iOS 11? iPhone X needs these gestures because it doesn’t have a home button. Classic iPhones <em>could</em> have supported them though — there’s no reason Apple couldn’t have added the swipe-up-from-bottom-to-go-home gesture to all iOS devices. And they could have then moved Control Center to a swipe down from the top right corner on all devices, too. I think they didn’t because they wanted a clean break, a clear division between the old and the new, the familiar and the novel.</p>
  1980. <p>And some aspects of the iPhone X experience wouldn&#8217;t work on older devices. You could in theory swipe up from the bottom to go home on a non-X iPhone, but you couldn&#8217;t swipe-up-from-the-bottom to unlock the lock screen, because that requires Face ID. Conversely, there is no room in the iPhone X experience for Touch ID. There is no &#8220;rest your finger here&#8221; in the experience. It wouldn&#8217;t matter if the fingerprint scanner were at the bottom of the display or on the back of the device &#8212; it would be incongruous.</p>
  1982. <p>What we’re left with, though, is truly a unique situation. Apple is attempting to move away from iOS&#8217;s historical interface one device at a time. Just the iPhone X this year. Maybe a few iPhone models next year. iPad Pros soon, too?<sup id="fnr6-2017-12-26"><a href="#fn6-2017-12-26">6</a></sup> But next thing you know, all new iOS devices will be using this, and within a few years after that, most iPhones in active use will be using it &#8212; without ever once having a single dramatic (or if you prefer, <em>traumatic</em>) platform-wide change.</p>
  1984. <p>The iPhone X is not the work of an overcautious company. It’s a risk to so fundamentally change the most profitable platform in the world. But Apple is gambling on the taste of the team who lived with the iPhone X during its development. Ossification is a risk with a platform as popular and successful as the iPhone &#8212; fear of making unpopular changes can lead a platform vendor to make no significant changes. Another risk, though, is hubris &#8212; making changes just for the sake of making changes that show off how clever the folks at Apple still are.</p>
  1986. <p>After two months using an iPhone X, I&#8217;m convinced Apple succeeded. The iPhone X is a triumph, a delightful conceptual modernization of a ten-year-old platform that, prior to using the iPhone X, I didn&#8217;t think needed a modernization. Almost nothing<sup id="fnr7-2017-12-26"><a href="#fn7-2017-12-26">7</a></sup> about the iPhone X calls undue attention to its cleverness. It all just seems like the new normal, and it&#8217;s a lot of fun.</p>
  1988. <div class="footnotes">
  1989. <hr />
  1990. <ol>
  1992. <li id="fn1-2017-12-26">
  1993. <p>How multitasking came to be on the original Mac <a href=";story=Switcher.txt">is a great story</a>. Long story short, Andy Hertzfeld single-handedly created Switcher while on a leave of absence from Apple. It just goes to show how insanely primitive the original Mac OS was that something like multitasking &#8212; even if it was, technically, more like the illusion of multitasking &#8212; could be added by a third-party system extension.&nbsp;<a href="#fnr1-2017-12-26"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1994. </li>
  1996. <li id="fn2-2017-12-26">
  1997. <p>Dating back to the NeXT era, Apple&#8217;s OS and API framework teams have proven themselves to be really good at building systems that, in their early days, push the limits of what is technically possible on the era&#8217;s hardware, but do so in ways that lay a solid foundation that scales for decades to come. It&#8217;s really quite remarkable the original 2007 iPhone&#8217;s OS and framework underpinnings could be traced back directly to a 1989 Unix workstation system. The same system now runs on wristwatches.&nbsp;<a href="#fnr2-2017-12-26"  class="footnoteBackLink"  title="Jump back to footnote 2 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  1998. </li>
  2000. <li id="fn3-2017-12-26">
  2001. <p>I find it hard to consider a world where that button was marked by an icon that looked like a house (the overwhelmingly common choice for a &#8220;home&#8221; icon) or printed with the word &#8220;<strong>HOME</strong>&#8221; (the way iPods <a href="">had a &#8220;<strong>MENU</strong>&#8221; button</a>). Early iPhone prototypes did, in fact, <a href="">have a &#8220;<strong>MENU</strong>&#8221; label on the button</a>.</p>
  2003. <p>I truly consider the iPhone home button icon the single best icon ever. It perfectly represented anything and everything apps could be &#8212; it was iconic in every sense of the word.&nbsp;<a href="#fnr3-2017-12-26"  class="footnoteBackLink"  title="Jump back to footnote 3 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  2004. </li>
  2007. <li id="fn4-2017-12-26">
  2008. <p><a href="">Apple added a similar indicator under the cellular/Wi-Fi/battery icons in iOS 11.2</a>, as an affordance to suggest where you go to invoke Control Center. Rather than solid black or white, though, it is translucent. This is exactly what I&#8217;d like to see Apple do with the home indicator.&nbsp;<a href="#fnr4-2017-12-26"  class="footnoteBackLink"  title="Jump back to footnote 4 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  2009. </li>
  2011. <li id="fn5-2017-12-26">
  2012. <p>My score to date: 4,134 strokes through 1,575 holes.&nbsp;<a href="#fnr5-2017-12-26"  class="footnoteBackLink"  title="Jump back to footnote 5 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  2013. </li>
  2015. <li id="fn6-2017-12-26">
  2016. <p>As for how the iPhone X-style Face ID/no-home-button experience will work on iPad, it&#8217;s unclear to me whether Apple has already thought this all the way through. Why, for example, did Apple just this year introduce a new small-swipe-up-from-the-bottom gesture for the iPad to show the new Dock, when the iPhone X suggests that a small swipe up from the bottom is the future of getting back to the home screen?&nbsp;<a href="#fnr6-2017-12-26"  class="footnoteBackLink"  title="Jump back to footnote 6 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  2017. </li>
  2019. <li id="fn7-2017-12-26">
  2020. <p>The way Apple wants software to handle the notch, in landscape orientation, is the one exception that springs to mind.&nbsp;<a href="#fnr7-2017-12-26"  class="footnoteBackLink"  title="Jump back to footnote 7 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  2021. </li>
  2023. </ol>
  2024. </div>
  2028.    ]]></content>
  2029.  <title>★ The iPhone X</title></entry><entry>
  2031.    <link rel="alternate" type="text/html" href="" />
  2032. <link rel="shorturl" href="" />
  2033. <id>,2017://1.34408</id>
  2034. <published>2017-12-23T20:28:25Z</published>
  2035. <updated>2017-12-24T02:32:46Z</updated>
  2036. <author>
  2037. <name>John Gruber</name>
  2038. <uri></uri>
  2039. </author>
  2040. <summary type="text">In short, Apple’s goal should be to make it easier for developers to create good Mac apps, and easier for Mac and iOS app siblings to share code. Apple’s goal should not be to make it easier to get iOS apps to run on the Mac in slightly modified form.</summary>
  2041. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  2042. <p>Mark Gurman had an intriguing story at Bloomberg this week, but the problems start with the headline itself: &#8220;<a href="">Apple Plans Combined iPhone, iPad and Mac Apps to Create One User Experience</a>&#8221;.</p>
  2044. <p>Gurman probably didn&#8217;t write the headline, but it doesn&#8217;t even make sense. iOS has no concept of a mouse cursor and runs only on touchscreen devices. MacOS has no support for touchscreen devices and requires a mouse pointer. &#8220;One user experience&#8221; is neither possible nor desirable. The truth is that this effort by Apple is almost certainly not about cross-platform <em>applications</em> but instead cross-platform <em>frameworks</em> for developers. It&#8217;s developer news, not user news.</p>
  2046. <p>Gurman:</p>
  2048. <blockquote>
  2049.  <p>Starting as early as next year, software developers will be able
  2050. to design a single application that works with a touchscreen or
  2051. mouse and trackpad depending on whether it’s running on the iPhone
  2052. and iPad operating system or on Mac hardware, according to people
  2053. familiar with the matter.</p>
  2055. <p>Developers currently must design two different apps &#8212; one for
  2056. iOS, the operating system of Apple’s mobile devices, and one for
  2057. macOS, the system that runs Macs. That’s a lot more work. What’s
  2058. more, Apple customers have long complained that some Mac apps get
  2059. short shrift. [&#8230;]</p>
  2061. <p>Apple is developing the strategy as part of the next major iOS and
  2062. macOS updates, said the people, who requested anonymity to discuss
  2063. an internal matter. Codenamed “Marzipan,” the secret project is
  2064. planned as a multiyear effort that will start rolling out as early
  2065. as next year and may be announced at the company’s annual
  2066. developers conference in the summer.</p>
  2067. </blockquote>
  2069. <p>Gus Mueller, designer and developer of the excellent <a href="">Acorn</a>, wrote <a href="">an excellent piece reading between the lines of Gurman&#8217;s report</a>:</p>
  2071. <blockquote>
  2072.  <p>I feel like this article from Gurman could have been reduced down
  2073. to: &#8220;We think Apple might some day have a shared UI framework for
  2074. iOS and MacOS. Apple could even create some sort of cross store
  2075. bundling or a single store with a single binary for all platforms
  2076. when using this framework (even though there&#8217;s nothing stopping
  2077. Apple from doing this today). That sounds neat and wouldn&#8217;t it be
  2078. cool if all platforms also used the same processor to boot? This
  2079. may or may not happen starting next year, and it could very
  2080. likely be canceled as well. Apple declined to comment on our
  2081. sensational story.&#8221;</p>
  2083. <p>What about the crux of the article, that Apple is working on a
  2084. shared UI framework between iOS and MacOS? I wouldn&#8217;t find it
  2085. surprising. I could also see it being written completely in Swift
  2086. (though personally I&#8217;d rather it be in Obj-C for maximum interop
  2087. with existing frameworks).</p>
  2089. <p>But history is filled with cross platform UIs and write-once
  2090. run-anywhere dreams. None of them turned out insanely great.</p>
  2091. </blockquote>
  2093. <p>My only quibble with Mueller&#8217;s piece is that &#8220;None of them turned out insanely great&#8221; is way too generous a description of write-once/run-anywhere application frameworks. Most of them are <a href="">terrible</a>; none of them are good. Or at least none of them are good from the perspective of what makes truly native Mac and iOS apps good &#8212; which isn&#8217;t everyone&#8217;s perspective, but is certainly Apple&#8217;s.</p>
  2095. <p>There is a lot of work involved getting an iPhone app to work well on an iPad. That&#8217;s why you still see iPhone-only apps. Even with good new cross-platform Mac/iOS frameworks, there would be <em>way</em> more work involved to bring an iPhone app to Mac than there is to bring to iPad. There would be less work than there is today, but still far more than supporting iPad.</p>
  2097. <p>At a high level, the user interfaces for native Mac apps are written using a framework called AppKit. <a href="">AppKit traces its roots all the way back to NeXTStep in the late 1980s</a>. AppKit&#8217;s NeXTStep roots remain so pervasive today that the class names developers use while writing Cocoa apps for the Mac are still prefixed with &#8220;NS&#8221;.</p>
  2099. <p>When Apple created iOS, rather than port AppKit, they effectively hit the reset button and created a new-from-the-ground-up set of frameworks called UIKit. What AppKit is for the Mac, UIKit is for iOS (and now tvOS). UIKit was a fresh start &#8212; in short, a sort of &#8220;<em>if we could do it all over again, what would we do differently?</em>&#8221; take on AppKit. The result benefitted from decades of lessons learned and unwanted baggage dropped.</p>
  2101. <p>To name just one of many differences, where AppKit has <a href="">NSColor</a>, UIKIt has <a href="">UIColor</a>. NSColor and UIColor serve the same purpose, but they are not the same. Specifying an entire user interface can never be the same on platforms as fundamentally different as the Mac and iPhone. Specifying things like, say, colors, could be.</p>
  2103. <p>I&#8217;ve never seen anyone argue for AppKit to be brought to iOS. There have been many calls &#8212; ever since the first SDK for the iPhone appeared &#8212; for UIKit to be brought to the Mac. Guilherme Rambo wrote such a piece last year, &#8220;<a href="">UXKit and Why &#8216;UIKit for macOS&#8217; Is Important</a>&#8221;:</p>
  2105. <blockquote>
  2106.  <p>The painfulness of working with AppKit is killing the Mac
  2107. platform. There are some really awesome iOS apps out there which
  2108. would benefit a lot from a macOS counterpart, but their developers
  2109. simply can&#8217;t cope with the burden of developing for both, so they
  2110. choose the one that&#8217;s most popular (hint: it is not macOS).
  2111. Instead, people are making crappy web-based apps, shoving them on
  2112. a .app with hundreds of megabytes and calling them &#8220;macOS apps&#8221;.</p>
  2114. <p>I didn&#8217;t believe it would be possible to have a single UI
  2115. framework for iOS and macOS, but I changed my mind when I saw how
  2116. UIKit works on tvOS. Think about it: it&#8217;s the same framework, but
  2117. with a different visual language and functionality added/removed
  2118. based on the needs of the platform:</p>
  2120. <ul>
  2121. <li><p>UIKit on tvOS has facilities to work with the remote control,
  2122. controlling focus and the parallax effect that is ubiquitous on
  2123. the platform.</p></li>
  2124. <li><p>UIKit on iOS has touch input, gesture recognizers, toolbars and
  2125. navigation bars</p></li>
  2126. <li><p>UIKit on macOS would have window controllers, contextual menus
  2127. and statusbar items</p></li>
  2128. </ul>
  2129. </blockquote>
  2131. <p>It&#8217;s more than a little hyperbolic to say that anything is &#8220;killing the Mac platform&#8221; today. <a href="">The Mac is thriving</a>. But there&#8217;s no question that maintaining parallel iOS and Mac apps is more work today than it could be. And it&#8217;s also true that for many companies, native Mac apps are prioritized lower than native iOS apps.<sup id="fnr1-2017-12-23"><a href="#fn1-2017-12-23">1</a></sup></p>
  2133. <p><a href="">Gurman cites Twitter as an example</a>:</p>
  2135. <blockquote>
  2136.  <p>For example, while the iPhone and iPad Twitter app is regularly
  2137. updated with the social network’s latest features, the Mac version
  2138. hasn’t been refreshed recently and is widely considered
  2139. substandard. With a single app for all machines, Mac, iPad and
  2140. iPhone users will get new features and updates at the same time.</p>
  2141. </blockquote>
  2143. <p>That &#8220;will&#8221; in the last sentence is naive. If Twitter could somehow generate a &#8220;Mac app&#8221; from their iOS app without any effort at all, it would be a terrible Mac app. Nobody wants an iOS app running in a window on their Mac. At best, it would take less work than it does today to maintain the Mac app &#8212; but there&#8217;s no guarantee Twitter would do that work, regardless of how much easier it would be than today.</p>
  2145. <p><a href="">Gus Mueller</a>:</p>
  2147. <blockquote>
  2148.  <p>There&#8217;s an easy solution for updating the Mac version of Twitter
  2149. to have the same features as its iOS peers. Twitter has to care
  2150. enough to update it. That&#8217;s it. It&#8217;s not as if there needs to be
  2151. massive engineering efforts put behind it. It&#8217;s not as if the road
  2152. hasn&#8217;t already been explored and the server APIs already exposed
  2153. (which they must have done for the iOS version). They just need to
  2154. put some effort and care to it. Tweetie for the Mac, which Twitter
  2155. for the Mac is based on, was built from the ground up by a single
  2156. person. All Twitter had to to was maintain it. And Twitter, Inc.
  2157. couldn&#8217;t be bothered.</p>
  2158. </blockquote>
  2160. <p><em>Caring</em> is ultimately what makes true Mac apps Mac apps. Caring about the details, caring about the Mac way of doing things. No amount of shared frameworks between MacOS and iOS can make iOS developers care about doing things properly on the Mac.</p>
  2162. <p>Apple&#8217;s Mac Photos app is implemented largely using a private framework called UXKit, which is in many ways UIKit for Mac. Curious about UXKit, <a href="">Rambo figured out how to create an app using it</a>:</p>
  2164. <blockquote>
  2165.  <p>But the most interesting things are the UX-prefixed classes. Most
  2166. of them are implementations of UIKit controls on top of AppKit.
  2167. There&#8217;s UXLabel, UXCollectionView, UXNavigationController,
  2168. UXViewController and much more. To see for myself whether I was
  2169. right, I decided to try and build a really simple app using UXKit.
  2170. <a href="">The code is available on my Github</a>. This app lets the user search
  2171. for photos on Flickr and select them to see a bigger version,
  2172. really simple.</p>
  2174. <p>While working on the app I noticed that it felt like I was working
  2175. on an iOS app. [&#8230;]</p>
  2177. <p>I think a developer who is familiar with UIKit would have no
  2178. problem making macOS apps using UXKit. From what I know, the only
  2179. apps that use UXKit currently are the macOS Photos app and the
  2180. Pricing app (the one used at Apple Stores).</p>
  2181. </blockquote>
  2183. <p>My concern with this whole situation is that even if this is all true &#8212; if Apple is indeed working on creating cross-platform UIKit-like frameworks for iOS and MacOS, <em>and</em> that the existence of such frameworks would spur more developers and companies to create Mac apps &#8212; it wouldn&#8217;t inevitably lead to the creation of <em>good</em> Mac apps.</p>
  2185. <p>Even Apple, much to my concern, has fallen short in this regard. Photos for Mac is one of the worst Mac apps I use. I love iCloud Photo Library syncing. Having the same set of thousands (tens of thousands, actually, in my case) of photos and videos in sync between all my devices, knowing that they&#8217;re all backed up on Apple&#8217;s servers, is a great experience. In terms of serving as a repository for your photos and videos, Photos for Mac works well.</p>
  2187. <p>But in terms of acting like a good Mac app, it does not. Even something as simple and fundamental to the Mac experience as drag-and-drop is all screwed up in Photos. When you drag an image out of Photos, you pretty much have to drop in the Finder first, then start a new drag with the new file copied to the Finder, before you can actually drop it into many contexts. Developer <a href="">Ilja A. Iwas complained about this recently</a>:</p>
  2189. <blockquote>
  2190.  <p>For almost a year now you cannot drag images from Photos to
  2191. Safari, and in extension every other macOS application that uses
  2192. WebViews, like our own GarageSale and many other 3rd party apps
  2193. that work with images.</p>
  2195. <p>Imagine that: The default image handling app on the Mac platform
  2196. cannot communicate via drag &amp; drop with the default browser. And
  2197. that’s been going on for almost a year now. On the desktop
  2198. platform that used to excel in drag and drop!</p>
  2200. <p>Not a day goes by without frustrated users in asking our support
  2201. team why GarageSale cannot receive drags from Photos.</p>
  2202. </blockquote>
  2204. <p>Try dragging an image out of Photos while the main Photos window is in the background. It doesn&#8217;t work. You need to activate the window first, then drag. Any other file manager-type app on the Mac allows drags to be initiated from background windows.<sup id="fnr2-2017-12-23"><a href="#fn2-2017-12-23">2</a></sup> <sup id="fnr3-2017-12-23"><a href="#fn3-2017-12-23">3</a></sup></p>
  2206. <p>Now try this: double-click and hold on an image in Photos, then drag. (That is to say, double-click on an image but don&#8217;t let go of the button on the second click.) In Photos for Mac, this initiates a drag. That&#8217;s nuts. Double-click, hold, and drag is how you create a selected range of multiple items in a list &#8212; the item you double-click on is the first item in the selection, and the ones you drag over are added to the selection. In a non-list view (like icon view in Finder), double-click-and-drag does nothing.</p>
  2208. <p>In addition to being non-standard, this particular behavior can get in the way when you just want to open an image, because Photos for Mac doesn&#8217;t allow for <a href="">hysteresis</a> for pointer movement during a double-click. Most Mac users will never notice this, but when you double-click on something on the Mac, the mouse pointer is allowed to move slightly between the first and second clicks. Such slight movements are especially common when using a trackpad, but they can happen with a mouse too. You don&#8217;t notice because the result is always what you intended. In early versions of Windows, which lacked hysteresis, double-clicking felt brittle, if not unreliable, because slight mouse movement between the first and second clicks would render the double-click attempt void. So it is with Photos for Mac &#8212; try to double-click on an image in Photos but inadvertently move the mouse pointer between clicks, and you wind up starting a drag instead of opening the image. If you&#8217;ve ever felt clumsy while trying to open images in Photos, it&#8217;s not your fault &#8212; it&#8217;s Apple&#8217;s.</p>
  2210. <p>And don&#8217;t get me started on some of the keyboard shortcuts in Photos. To get back from an image opened in detail view to the list of thumbnails, the Esc (Escape) key doesn&#8217;t work &#8212; you have to use the space bar. The shortcut for this might as well be Esc-<em>swear</em>-Space bar, because even after a few years now, I can&#8217;t get used to it.</p>
  2212. <p>It&#8217;s as though Photos for Mac was created by iOS developers who saw a Mac one time and said, &#8220;Sure, we can do that.&#8221;</p>
  2214. <p>Again, I use Photos &#8212; but only despite its crummy Mac interface. Photos is a poor poster child for the argument that Apple should make it easier for developers with experience only on iOS to create Mac apps.</p>
  2216. <p>Long-time Mac developer Michael Tsai (author of <a href="">EagleFiler</a> and <a href="">SpamSieve</a>) <a href="">has similar concerns</a>:</p>
  2218. <blockquote>
  2219.  <p>This has long seemed like an obvious thing for Apple to do, but
  2220. I’m not sure it’s good for the Mac platform. The upside is that
  2221. we’ll get lots of ports of iOS apps where previously there was no
  2222. Mac app or only a poor quality Web-based one. The downside is that
  2223. I don’t want to be using lowest common denominator iOS ports. I
  2224. like using a Mac because of the apps that really take advantage of
  2225. what the desktop has to offer. I’m continually annoyed by the apps
  2226. that essentially put an iOS-style interface in a window and don’t
  2227. support standard Mac conventions or features. I also worry that
  2228. bifurcating the platform with UXKit and AppKit apps will
  2229. inevitably mean that Apple will focus less on enhancing AppKit,
  2230. while at the same time doubling the surface area for bugs. Having
  2231. two classes of Mac apps would not be good, but AppKit going the
  2232. way of Carbon would be even worse.</p>
  2233. </blockquote>
  2235. <p><a href="">Jeff Johnson, on Twitter</a>:</p>
  2237. <blockquote>
  2238.  <p>There seems to be a big cultural divide between iOS developers who
  2239. came from the Mac and iOS developers who didn’t. Many in the
  2240. latter group are OK with destroying the Mac, and that’s very
  2241. frustrating to me.</p>
  2242. </blockquote>
  2244. <p><a href="">And also from Johnson</a> (this tweet is the start of a good thread):</p>
  2246. <blockquote>
  2247.  <p>Something that crystalized for me yesterday is how afraid many
  2248. UIKit developers are of AppKit. Which is unfortunate, because the
  2249. similarities vastly outnumber the differences.</p>
  2250. </blockquote>
  2252. <p>In short, Apple&#8217;s goal should be to make it easier for developers to create good Mac apps, and easier for Mac and iOS app siblings to share code. Apple&#8217;s goal should not be to make it easier to get iOS apps to run on the Mac in slightly modified form. And I think it&#8217;s nonsensical to think that Apple is working toward a single unified OS. The best reason for hope on this front is the <a href="">recent redoubling</a> of Apple&#8217;s efforts on pro Mac hardware. The iMac Pro was not designed to run iPhone apps.<sup id="fnr4-2017-12-23"><a href="#fn4-2017-12-23">4</a></sup></p>
  2254. <div class="footnotes">
  2255. <hr />
  2256. <ol>
  2258. <li id="fn1-2017-12-23">
  2259. <p>The priority order at many companies is (1) native mobile apps, (2) website, (3) native desktop app. Priorities (1) and (2) are sometimes flipped, but native desktop apps generally remain third. One reason for this is that &#8212; as a general rule &#8212; only Mac users care about native desktop apps, and even there, only <em>some</em> Mac users. So for most companies and services, they never even get around to a native Mac app, because the website running in a desktop browser tab is &#8220;good enough&#8221;. I could probably list dozens &#8212; maybe hundreds &#8212; of examples, but just off the top of my head, think about services like OpenTable and Yelp. Native mobile apps, websites for desktop. Facebook is all-in on mobile apps, but I&#8217;ll bet they&#8217;ve never even <em>considered</em> building a native Mac app for Facebook or Instagram.</p>
  2261. <p>And then there&#8217;s Twitter. When Twitter <a href="">acquired Loren Brichter&#8217;s Tweetie</a>, they not only had what I considered the best native Mac Twitter client, but <a href="">one of the best and most forward-thinking Mac apps</a>, period. First they let it languish, then <a href="">they replaced it with a ground-up rewrite with none of Tweetie&#8217;s charm or appeal</a>, and now it has gotten to the point where today it&#8217;s surprising they even keep their official Mac client around. Clearly they think Mac users should use their website.&nbsp;<a href="#fnr1-2017-12-23"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  2262. </li>
  2264. <li id="fn2-2017-12-23">
  2265. <p>Well, iTunes doesn&#8217;t seem to. But it used to. And if you&#8217;re taking your UI cues from iTunes, you&#8217;ve got bigger problems.&nbsp;<a href="#fnr2-2017-12-23"  class="footnoteBackLink"  title="Jump back to footnote 2 in the text.">&#x21A9;&#xFE0E;</a></p>
  2266. </li>
  2268. <li id="fn3-2017-12-23">
  2269. <p>It&#8217;s also worth pointing out that iPhoto, which Photos effectively replaced on the Mac, also did some really weird shit with double-clicking (iPhoto would open an image on a double-click&#8217;s second mousedown event, rather than waiting for the second mouseup &#8212; gross), drag-and-drop (you couldn&#8217;t drag from iPhoto when it was in the background, and keyboard shortcuts (same thing as Photos, where space bar, rather than Esc, is the shortcut for going back from an image&#8217;s detail view to the list of thumbnails). So it&#8217;s quite possible that some of my complaints about the non-idiomatic Mac-like-ness of Photos for Mac are not the result of it being made by iOS developers unfamiliar with the Mac, but because they copied bad ideas from iPhoto.&nbsp;<a href="#fnr3-2017-12-23"  class="footnoteBackLink"  title="Jump back to footnote 3 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  2270. </li>
  2273. <li id="fn4-2017-12-23">
  2274. <p>Well, except for running them in the iOS Simulator, which it does with aplomb.&nbsp;<a href="#fnr4-2017-12-23"  class="footnoteBackLink"  title="Jump back to footnote 4 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  2275. </li>
  2279. </ol>
  2280. </div>
  2284.    ]]></content>
  2285.  <title>★ Marzipan</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