[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>2017-07-26T00:27:31Z</updated><rights>Copyright © 2017, John Gruber</rights><entry>
  11. <title>Trump Says Tim Cook Has Promised to Build Three Manufacturing Plants in U.S.</title>
  12. <link rel="alternate" type="text/html" href="" />
  13. <link rel="shorturl" type="text/html" href="" />
  14. <link rel="related" type="text/html" href="" />
  15. <id>,2017:/linked//6.33929</id>
  16. <published>2017-07-26T00:27:29Z</published>
  17. <updated>2017-07-26T00:27:31Z</updated>
  18. <author>
  19. <name>John Gruber</name>
  20. <uri></uri>
  21. </author>
  22. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  23. <p>Tripp Mickle and Peter Nicholas, reporting for The Wall Street Journal:</p>
  25. <blockquote>
  26.  <p>Mr. Trump, in a 45-minute interview with The Wall Street Journal,
  27. said Mr. Cook promised him Apple would build “three big plants,
  28. beautiful plants.” Mr. Trump didn’t elaborate on where those
  29. plants would be located or when they would be built.</p>
  31. <p>“I spoke to [Mr. Cook], he’s promised me three big plants &#8212; big,
  32. big, big,” Mr. Trump said as part of a discussion about
  33. business-tax reform and business investment. “I said you know,
  34. Tim, unless you start building your plants in this country, I
  35. won’t consider my administration an economic success. He called
  36. me, and he said they are going forward.”</p>
  38. <p>Apple declined to comment.</p>
  39. </blockquote>
  41. <p>This is odd in so many ways. If it&#8217;s true, this is a massive strategic shift for Apple, and it makes me wonder why Cook would share this news with Trump prior to Apple announcing it on their own terms. And if it&#8217;s not true, boy did Trump just send Cook a huge shit sandwich.</p>
  43. <p>Apple&#8217;s most recent foray into U.S. assembly is <a href="">a facility in Texas for the Mac Pro</a>. <a href="">There was quite a bit of publicity</a> about that, but until now it doesn&#8217;t seem to have led to anything else. And Apple doesn&#8217;t even own that plant &#8212; <a href="">they partnered with a company named Flex</a>. <a href="">According to Vindu Goel</a>, Apple only owns one factory in the world &#8212; in Ireland.</p>
  45. <div>
  46. <a  title="Permanent link to ‘Trump Says Tim Cook Has Promised to Build Three Manufacturing Plants in U.S.’"  href="">&nbsp;★&nbsp;</a>
  47. </div>
  49. ]]></content>
  50.  </entry><entry>
  51. <title>Adobe Announces End-of-Life for Flash</title>
  52. <link rel="alternate" type="text/html" href="" />
  53. <link rel="shorturl" type="text/html" href="" />
  54. <link rel="related" type="text/html" href="" />
  55. <id>,2017:/linked//6.33928</id>
  56. <published>2017-07-25T22:33:56Z</published>
  57. <updated>2017-07-25T22:34:50Z</updated>
  58. <author>
  59. <name>John Gruber</name>
  60. <uri></uri>
  61. </author>
  62. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  63. <p>Adobe:</p>
  65. <blockquote>
  66.  <p>Today, most browser vendors are integrating capabilities once
  67. provided by plugins directly into browsers and deprecating
  68. plugins.</p>
  70. <p>Given this progress, and in collaboration with several of our
  71. technology partners &#8212; including <a href="">Apple</a>, <a href="">Facebook</a>, <a href="">Google</a>,
  72. <a href="">Microsoft</a> and <a href="">Mozilla</a> &#8212; Adobe is planning to end-of-life Flash.
  73. Specifically, we will stop updating and distributing the Flash
  74. Player at the end of 2020 and encourage content creators to
  75. migrate any existing Flash content to these new open formats.</p>
  76. </blockquote>
  78. <p>Apple&#8217;s key decision was never supporting Flash on iOS, and sticking with that decision even when they were under significant marketing pressure to do so. Steve Jobs&#8217;s famous &#8220;<a href="">Thoughts on Flash</a>&#8221; was not the cause of Flash&#8217;s demise &#8212; it was an explanation for why Flash was doomed.</p>
  80. <p>iOS never supporting Flash, combined with the size and appealing demographics of iOS users, hastened the demise of Flash by several years. Web publishers switched to HTML5 technologies for video and interactive content sooner than they would have otherwise. But I think Flash was doomed regardless. The world was going mobile whether Apple led the way or not, and Flash was never a good fit for mobile computing.</p>
  82. <p>This official &#8220;end of life&#8221; statement is an important step, but Adobe saw the writing on the wall six years ago <a href="">when they officially stopped developing Flash Player for Android</a>. Strategically, that was the death of Flash.</p>
  84. <div>
  85. <a  title="Permanent link to ‘Adobe Announces End-of-Life for Flash’"  href="">&nbsp;★&nbsp;</a>
  86. </div>
  88. ]]></content>
  89.  </entry><entry>
  90. <title>David Remnick Interviews Maggie Haberman</title>
  91. <link rel="alternate" type="text/html" href="" />
  92. <link rel="shorturl" type="text/html" href="" />
  93. <link rel="related" type="text/html" href="" />
  94. <id>,2017:/linked//6.33927</id>
  95. <published>2017-07-25T20:09:43Z</published>
  96. <updated>2017-07-25T20:09:45Z</updated>
  97. <author>
  98. <name>John Gruber</name>
  99. <uri></uri>
  100. </author>
  101. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  102. <p>The New Yorker&#8217;s David Remnick has a terrific interview with New York Times reporter Maggie Haberman. Much of what we know of the inner workings of the Trump White House, we know from Haberman.</p>
  104. <blockquote>
  105.  <p>D.R.: What do you make out to be the ideology of Donald Trump? Or
  106. is it purely situational? We saw him running as a new kind of
  107. populist. At moments, he seems very right-wing; at other times he
  108. undermines that kind of conservative ideology.</p>
  110. <p>M.H.: I think he has no clear ideology. I think he has a couple of
  111. base impulses he’s held onto since the nineteen-eighties, when he
  112. was taking out those newspaper ads about how Japan is “ripping us
  113. off.” A lot of the language that he used then is the same as what
  114. he uses now, but it’s more of a feeling than an ideology. It’s a
  115. sense that the United States is being taken advantage of. Can he
  116. name by whom, accurately? Not necessarily. He ran as a Republican,
  117. and he really appealed to this hard-right base that believes in
  118. less government. But, in reality, this is a man who grew up in Ed
  119. Koch’s New York City, and I think he has a very specific view of
  120. the role that government is supposed to play in people’s lives.</p>
  121. </blockquote>
  123. <div>
  124. <a  title="Permanent link to ‘David Remnick Interviews Maggie Haberman’"  href="">&nbsp;★&nbsp;</a>
  125. </div>
  127. ]]></content>
  128.  </entry><entry>
  129. <title>The Verge: Bragi Dash Pro Wireless Earbuds</title>
  130. <link rel="alternate" type="text/html" href="" />
  131. <link rel="shorturl" type="text/html" href="" />
  132. <link rel="related" type="text/html" href="" />
  133. <id>,2017:/linked//6.33926</id>
  134. <published>2017-07-25T19:35:43Z</published>
  135. <updated>2017-07-25T19:35:46Z</updated>
  136. <author>
  137. <name>John Gruber</name>
  138. <uri></uri>
  139. </author>
  140. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  141. <p>Sean O&#8217;Kane, writing for The Verge:</p>
  143. <blockquote>
  144.  <p>Bragi hasn’t completely solved this problem with the Dash Pro, and
  145. I still think its other, cheaper, wireless earbuds are a better
  146. buy. But the company’s gotten much closer this time around. You
  147. can put your phone in basically any pocket, or in a bag, and the
  148. connection only hiccups about 10 percent of the time, maybe even
  149. less depending on your height.</p>
  150. </blockquote>
  152. <p>I&#8217;m not saying my AirPods never suffer Bluetooth hiccups, but it happens very rarely. Apple is so far ahead of its competition on this front.</p>
  154. <div>
  155. <a  title="Permanent link to ‘The Verge: Bragi Dash Pro Wireless Earbuds’"  href="">&nbsp;★&nbsp;</a>
  156. </div>
  158. ]]></content>
  159.  </entry><entry>
  160. <title>Neuropathologist Examined the Brains of 111 NFL Players; 110 of Them Showed Signs of C.T.E.</title>
  161. <link rel="alternate" type="text/html" href="" />
  162. <link rel="shorturl" type="text/html" href="" />
  163. <link rel="related" type="text/html" href="" />
  164. <id>,2017:/linked//6.33925</id>
  165. <published>2017-07-25T19:25:21Z</published>
  166. <updated>2017-07-25T19:25:22Z</updated>
  167. <author>
  168. <name>John Gruber</name>
  169. <uri></uri>
  170. </author>
  171. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  172. <p>The New York Times:</p>
  174. <blockquote>
  175.  <p>Dr. Ann McKee, a neuropathologist, has examined the brains of 202
  176. deceased football players. A broad survey of her findings was
  177. published on Tuesday in The Journal of the American Medical
  178. Association.</p>
  180. <p>Of the 202 players, 111 of them played in the N.F.L. &#8212; and 110 of
  181. those were found to have chronic traumatic encephalopathy, or
  182. C.T.E., the degenerative disease believed to be caused by repeated
  183. blows to the head. [&#8230;]</p>
  185. <p>The set of players posthumously tested by Dr. McKee is far from
  186. a random sample of N.F.L. retirees. “There’s a tremendous
  187. selection bias,” she has cautioned, noting that many families
  188. have donated brains specifically because the former player
  189. showed symptoms of C.T.E.</p>
  191. <p>But 110 positives remain significant scientific evidence of an
  192. N.F.L. player’s risk of developing C.T.E., which can be diagnosed
  193. only after death. About 1,300 former players have died since the
  194. B.U. group began examining brains. So even if every one of the
  195. other 1,200 players had tested negative &#8212; which even the
  196. heartiest skeptics would agree could not possibly be the case &#8212;
  197. the minimum C.T.E. prevalence would be close to 9 percent, vastly
  198. higher than in the general population.</p>
  199. </blockquote>
  201. <p>I keep thinking change will come inevitably from the ground up &#8212; <a href="">fewer and fewer parents are allowing their kids to play football each year</a>. But at the high school level, <a href="">participation only dropped by 2.5 percent from 2008 through 2015</a>.</p>
  203. <div>
  204. <a  title="Permanent link to ‘Neuropathologist Examined the Brains of 111 NFL Players; 110 of Them Showed Signs of C.T.E.’"  href="">&nbsp;★&nbsp;</a>
  205. </div>
  207. ]]></content>
  208.  </entry><entry>
  209. <title>The Talk Show: ‘Actually, You Can Buy a Better Coke’</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>,2017:/linked//6.33924</id>
  214. <published>2017-07-21T21:23:52Z</published>
  215. <updated>2017-07-21T21:23:54Z</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>Rene Ritchie returns to the show to talk about the rumors and speculation regarding this year’s upcoming new iPhones.</p>
  223. <p>Brought to you by these excellent sponsors:</p>
  225. <ul>
  226. <li><a href="">Hullo Pillow</a>: Sleep better with a new buckwheat pillow. It’ll be your favorite pillow, guaranteed.</li>
  227. <li><a href="">Casper</a>: An obsessively engineered mattress at a shockingly fair price. Use code <strong>thetalkshow</strong> for $50 toward your mattress.</li>
  228. <li><a href=""></a>: With Audible, you’ll find what you’re looking for. Get a free 30-day trial.</li>
  229. </ul>
  231. <div>
  232. <a  title="Permanent link to ‘The Talk Show: &#8216;Actually, You Can Buy a Better Coke&#8217;’"  href="">&nbsp;★&nbsp;</a>
  233. </div>
  235. ]]></content>
  236.  </entry><entry>
  237. <title>In Urban China, Cash Is Rapidly Becoming Obsolete</title>
  238. <link rel="alternate" type="text/html" href="" />
  239. <link rel="shorturl" type="text/html" href="" />
  240. <link rel="related" type="text/html" href="" />
  241. <id>,2017:/linked//6.33923</id>
  242. <published>2017-07-21T16:04:37Z</published>
  243. <updated>2017-07-21T16:04:39Z</updated>
  244. <author>
  245. <name>John Gruber</name>
  246. <uri></uri>
  247. </author>
  248. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  249. <p>Paul Mozur, writing for The New York Times:</p>
  251. <blockquote>
  252.  <p>Almost everyone in major Chinese cities is using a smartphone to
  253. pay for just about everything. At restaurants, a waiter will ask
  254. if you want to use WeChat or Alipay &#8212; the two smartphone payment
  255. options &#8212; before bringing up cash as a third, remote possibility.</p>
  257. <p>Just as startling is how quickly the transition has happened. Only
  258. three years ago there would be no question at all, because
  259. everyone was still using cash.</p>
  260. </blockquote>
  262. <div>
  263. <a  title="Permanent link to ‘In Urban China, Cash Is Rapidly Becoming Obsolete’"  href="">&nbsp;★&nbsp;</a>
  264. </div>
  266. ]]></content>
  267.  </entry><entry>
  268. <title>The iPhone Paradox</title>
  269. <link rel="alternate" type="text/html" href="" />
  270. <link rel="shorturl" type="text/html" href="" />
  271. <link rel="related" type="text/html" href="" />
  272. <id>,2017:/linked//6.33922</id>
  273. <published>2017-07-21T15:36:31Z</published>
  274. <updated>2017-07-21T15:38:53Z</updated>
  275. <author>
  276. <name>John Gruber</name>
  277. <uri></uri>
  278. </author>
  279. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  280. <p>The Macalope:</p>
  282. <blockquote>
  283.  <p>Maybe it’s just the horny one, but if you have information that
  284. shows the iPhone 8 is going to be a logical paradox &#8212; like a real
  285. life M.C. Escher painting &#8212; that is somehow simultaneously too
  286. expensive for anyone to want to buy and so wildly popular they
  287. can’t make them fast enough, you should probably lead with that.
  288. That would be big news, quantum mechanically speaking.</p>
  289. </blockquote>
  291. <p>It&#8217;s like the <a href="">Yogi-ism</a>: &#8220;Nobody goes there anymore, it&#8217;s too crowded.&#8221;</p>
  293. <div>
  294. <a  title="Permanent link to ‘The iPhone Paradox’"  href="">&nbsp;★&nbsp;</a>
  295. </div>
  297. ]]></content>
  298.  </entry><entry>
  299. <title>Called It</title>
  300. <link rel="alternate" type="text/html" href="" />
  301. <link rel="shorturl" type="text/html" href="" />
  302. <link rel="related" type="text/html" href="" />
  303. <id>,2017:/linked//6.33921</id>
  304. <published>2017-07-20T00:18:24Z</published>
  305. <updated>2017-07-21T16:04:57Z</updated>
  306. <author>
  307. <name>John Gruber</name>
  308. <uri></uri>
  309. </author>
  310. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  311. <p>Yours truly on Google Glass back in 2013:</p>
  313. <blockquote>
  314.  <p>And the idea that people will wear things like this everywhere (as
  315. opposed to special specific scenarios, such as workers in an
  316. environment where their hands are otherwise occupied, like, say,
  317. surgeons) strikes me as creepy as hell.</p>
  318. </blockquote>
  320. <div>
  321. <a  title="Permanent link to ‘Called It’"  href="">&nbsp;★&nbsp;</a>
  322. </div>
  324. ]]></content>
  325.  </entry><entry>
  326. <title>Samsung Describes Its Male and Female Bixby Assistants With Sexist Descriptions</title>
  327. <link rel="alternate" type="text/html" href="" />
  328. <link rel="shorturl" type="text/html" href="" />
  329. <link rel="related" type="text/html" href="" />
  330. <id>,2017:/linked//6.33920</id>
  331. <published>2017-07-20T00:17:21Z</published>
  332. <updated>2017-07-20T21:59:41Z</updated>
  333. <author>
  334. <name>John Gruber</name>
  335. <uri></uri>
  336. </author>
  337. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  338. <p>Alejandro Alba, writing for Gizmodo:</p>
  340. <blockquote>
  341.  <p>After months of delays, Samsung’s much ballyhooed voice assistant
  342. Bixby is here &#8212; and users on social media are already noticing
  343. the company’s <a href="">loaded</a>, <a href="">sexist</a> <a href=";">characterizations</a> of its
  344. female and male voices.</p>
  346. <p>Inside Bixby’s “language and speaking style” menu, Samsung
  347. describes its female voice as “chipper” and “cheerful,” while the
  348. male voice is described as “confident” and “assertive.”</p>
  349. </blockquote>
  351. <p><a href="">Not a new problem for Samsung</a>.</p>
  353. <div>
  354. <a  title="Permanent link to ‘Samsung Describes Its Male and Female Bixby Assistants With Sexist Descriptions’"  href="">&nbsp;★&nbsp;</a>
  355. </div>
  357. ]]></content>
  358.  </entry><entry>
  360.    <link rel="alternate" type="text/html" href="" />
  361. <link rel="shorturl" href="" />
  362. <id>,2017://1.33919</id>
  363. <published>2017-07-19T22:47:17Z</published>
  364. <updated>2017-07-21T17:05:23Z</updated>
  365. <author>
  366. <name>John Gruber</name>
  367. <uri></uri>
  368. </author>
  369. <summary type="text">The single biggest misconception about iOS is that it’s good digital hygiene to force quit apps that you aren’t using.</summary>
  370. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  371. <p>The single biggest misconception about iOS is that it&#8217;s good digital hygiene to force quit apps that you aren&#8217;t using. The idea is that apps in the background are locking up unnecessary RAM and consuming unnecessary CPU cycles, thus hurting performance and wasting battery life.</p>
  373. <p>That&#8217;s not how iOS works. The iOS system is designed so that <em>none</em> of the above justifications for force quitting are true. Apps in the background are effectively &#8220;frozen&#8221;, severely limiting what they can do in the background and freeing up the RAM they were using. iOS is really, really good at this. It is so good at this that unfreezing a frozen app takes up <em>way</em> less CPU (and energy) than relaunching an app that had been force quit. Not only does force quitting your apps not help, it actually <em>hurts</em>. Your battery life will be worse and it will take much longer to switch apps if you force quit apps in the background.</p>
  375. <p><a href="">Here&#8217;s a short and sweet answer from Craig Federighi</a>, in response to an email from a customer asking if he force quits apps and whether doing so preserves battery life: &#8220;No and no.&#8221;</p>
  377. <p>Here, from the official support document on forcing applications to close, is <a href="">Apple&#8217;s own advice on <em>when</em> to use this feature</a>:</p>
  379. <blockquote>
  380.  <p>When you double-click the Home button, your recently used apps
  381. appear. The apps aren’t open, but they&#8217;re in standby mode to help
  382. you navigate and multitask. You should force an app to close only
  383. when it’s unresponsive.</p>
  384. </blockquote>
  386. <p><strong>Update:</strong> MacDailyNews quotes a 2010 email from Steve Jobs:</p>
  388. <blockquote>
  389.  <p>Just use [iOS multitasking] as designed, and you’ll be happy. No
  390. need to ever quit apps.</p>
  391. </blockquote>
  393. <p>Just in case you don&#8217;t believe Apple&#8217;s senior vice president for software, Apple&#8217;s own official support documentation, or Steve Jobs, here are some other articles pointing out how this habit is actually detrimental to iPhone battery life:</p>
  395. <ul>
  396. <li>Fraser Speirs (back in 2012!): &#8220;<a href="">Misconceptions About iOS Multitasking</a>&#8221;</li>
  397. <li>Thorin Klosowski: &#8220;<a href="">Quitting All Your Apps in iOS Can Actually Worsen Battery Life</a>&#8221;</li>
  398. <li>Kendall Baker: &#8220;<a href="https:[email protected]/stop-force-quitting-your-iphone-apps-eb13d86caaa5">Stop Force Quitting Your iPhone Apps</a>&#8221;</li>
  399. <li>The Wirecutter: &#8220;<a href="">What You Should (and Shouldn&#8217;t) Do to Extend Your Phone&#8217;s Battery Life</a>&#8221;</li>
  400. <li>Kyle Richter: &#8220;<a href="">The Force Quit Fallacy</a>&#8221;</li>
  401. </ul>
  403. <p>This thing about force quitting apps in the background is such a pernicious myth that I&#8217;ve heard numerous stories from DF readers <a href="">about Apple Store Genius Bar staff recommending it to customers</a>. Those &#8220;geniuses&#8221; are anything but geniuses.</p>
  405. <p>It occurs to me that some of the best examples <em>proving</em> that this notion is wrong (at least in terms of performance) are YouTube &#8220;speed test&#8221; benchmarks. There&#8217;s an entire genre of YouTube videos devoted to benchmarking new phones by running them through a series of apps and CPU-intensive tasks repeatedly, going through the loop twice. Once from a cold boot and the second time immediately after the first loop. <a href="">Here&#8217;s a perfect example, pitting a Samsung Galaxy S8 against an iPhone 7 Plus</a>. Note that no apps are manually force quit on either device. The iPhone easily wins on the first loop, but where the iPhone really shines is on the second loop. The S8 has to relaunch all (or at least almost all) of the apps, because Android has forced them to quit while in the background to reclaim the RAM they were using. On the iPhone, all (or nearly all) of the apps re-animate almost instantly.</p>
  407. <p>In fact, apps frozen in the background on iOS unfreeze so quickly that I think it actually helps perpetuate the myth that you should force quit them: if you&#8217;re worried that background apps are draining your battery and you see how quickly they load from the background, it&#8217;s a reasonable assumption to believe that they never stopped running. But they did. They really do get frozen, the RAM they were using really does get reclaimed by the system, and they really do unfreeze and come back to life that quickly.<sup id="fnr1-2017-07-19"><a href="#fn1-2017-07-19">1</a></sup></p>
  409. <p>An awful lot of very hard work went into making iOS work like this. It&#8217;s a huge technical advantage that iOS holds over Android. And every iPhone user in the world who habitually force quits background apps manually is wasting all of the effort that went into this while simultaneously wasting their own device&#8217;s battery life and making everything slower for themselves.</p>
  411. <p>This pernicious myth is longstanding and seemingly will not die. <a href="">I wrote about it at length back in 2012</a>:</p>
  413. <blockquote>
  414.  <p>Like with any voodoo, there are die-hard believers. I’m quite
  415. certain that I am going to receive email from people who will
  416. swear up-and-down that emptying this list of used applications
  417. every hour or so keeps their iPhone running better than it would
  418. otherwise. Nonsense.</p>
  420. <p><a href="">As Fraser mentions</a>, yes, there are exceptional situations where an
  421. app with background privileges can get stuck, and you need to kill
  422. that app. The argument here is not that you should never have to
  423. kill any app using the multitasking switcher &#8212; the argument is
  424. that you don’t need to do it on a regular basis, and you’re not
  425. making anything “better” by clearing the list. Shame on the
  426. “geniuses” who are peddling this advice.</p>
  427. </blockquote>
  429. <p>And don&#8217;t even get me started on people who completely power down their iPhones while putting them back into their pockets or purses.</p>
  431. <div class="footnotes">
  432. <hr />
  433. <ol>
  434. <li id="fn1-2017-07-19">
  435. <p>The other contributing factor to believing that force quitting is good for your iPhone are the handful of apps that have been found to be repeated abusers of loopholes in iOS, such that they really do continue running in the background, wasting battery life. Most infamously, Facebook was caught playing silent audio tracks in the background to take advantage of APIs that allow audio-playing apps to play audio from the background. <a href="">They called it a &#8220;bug&#8221;</a>. In those cases force-quitting the apps really did help, and I see no reason to trust Facebook. So if you want to keep force quitting Facebook, go right ahead. But don&#8217;t let one bad app spoil the whole barrel. The Battery section in the iOS Settings app can show you which apps are actually consuming energy in the background &#8212; tap the clock icon under &#8220;Battery Usage&#8221; and don&#8217;t force quit any app that isn&#8217;t a genuine culprit.&nbsp;<a href="#fnr1-2017-07-19"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  436. </li>
  437. </ol>
  438. </div>
  442.    ]]></content>
  443.  <title>★ Public Service Announcement: You Should Not Force Quit Apps on iOS</title></entry><entry>
  444. <title>Apple Machine Learning Journal</title>
  445. <link rel="alternate" type="text/html" href="" />
  446. <link rel="shorturl" type="text/html" href="" />
  447. <link rel="related" type="text/html" href="" />
  448. <id>,2017:/linked//6.33918</id>
  449. <published>2017-07-19T16:19:26Z</published>
  450. <updated>2017-07-19T21:42:56Z</updated>
  451. <author>
  452. <name>John Gruber</name>
  453. <uri></uri>
  454. </author>
  455. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  456. <p>New publication from Apple, where Apple engineers can publish their work and research on machine learning. The writing is more accessible than a peer-reviewed technical journal, but alas (but unsurprisingly for Apple), the articles are un-bylined. The approachability without avoiding nitty-gritty technical details reminds me of Dr. Dobb&#8217;s Journal back in the day.</p>
  458. <p>My assumption here is that this doesn’t replace <a href="">publishing in established peer-reviewed journals</a>, but rather acts as a public-facing, more accessible filter for research that Apple engineers publish in peer-reviewed journals &#8212; perhaps along with original content at some point.</p>
  460. <p>(Also: no RSS feed. <strong>Update:</strong> <a href="">There <em>is</em> an RSS feed</a> &#8212; <a href="">the URL</a> just isn&#8217;t published anywhere in the HTML. <strong>Update 2:</strong> The site now has a <code>&lt;link&gt;</code> tag with the URL for the feed so you can just point any feed reader at its home page to discover the feed. Nice.)</p>
  462. <div>
  463. <a  title="Permanent link to ‘Apple Machine Learning Journal’"  href="">&nbsp;★&nbsp;</a>
  464. </div>
  466. ]]></content>
  467.  </entry><entry>
  468. <title>Acorn 6</title>
  469. <link rel="alternate" type="text/html" href="" />
  470. <link rel="shorturl" type="text/html" href="" />
  471. <link rel="related" type="text/html" href="" />
  472. <id>,2017:/linked//6.33917</id>
  473. <published>2017-07-19T00:37:57Z</published>
  474. <updated>2017-07-19T00:37:59Z</updated>
  475. <author>
  476. <name>John Gruber</name>
  477. <uri></uri>
  478. </author>
  479. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  480. <p>Gus Mueller, Flying Meat Software:</p>
  482. <blockquote>
  483.  <p>What&#8217;s new and awesome?</p>
  485. <p>For a number of years, text on a path has been our number one
  486. feature request and we finally got to deliver it with version 6.
  487. Acorn has always had great text support; it handles unicode
  488. effortlessly, and you can have multiple font faces and weights in
  489. a single text block. You can even have emoji as part of your text
  490. block. All of these same features work perfectly with text on a
  491. path. Inline editing, selection, etc- it just works. And it was a
  492. ton of fun to code on as well. Buy me a beer someday and I&#8217;ll
  493. spill the details on how I coded it.</p>
  495. <p>We also implemented our number two feature request, clone tool
  496. improvements. You can now select any layer as a clone source
  497. (bitmap layers, a group of layers, even shape layers) and then
  498. clone to any other layer, or even another image. We also added
  499. stamping to the clone tool, which works by holding down the shift
  500. key when you click on your image.</p>
  501. </blockquote>
  503. <p>Another excellent update to another one of my favorite and most-depended-upon apps. Compared to the old days of &#8220;Photoshop or bust&#8221;, we Mac users today have a veritable cornucopia of excellent image editing apps to choose from. Acorn just best fits my needs and my way of thinking about how a Mac image editor should look and work. On sale for just $15 &#8212; that&#8217;s 50 percent off &#8212; for a limited time.</p>
  505. <div>
  506. <a  title="Permanent link to ‘Acorn 6’"  href="">&nbsp;★&nbsp;</a>
  507. </div>
  509. ]]></content>
  510.  </entry><entry>
  511. <title>Transmit 5</title>
  512. <link rel="alternate" type="text/html" href="" />
  513. <link rel="shorturl" type="text/html" href="" />
  514. <link rel="related" type="text/html" href="" />
  515. <id>,2017:/linked//6.33916</id>
  516. <published>2017-07-19T00:31:29Z</published>
  517. <updated>2017-07-19T00:32:39Z</updated>
  518. <author>
  519. <name>John Gruber</name>
  520. <uri></uri>
  521. </author>
  522. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  523. <p>Cabel Sasser:</p>
  525. <blockquote>
  526.  <p>Seven years after the first release of Transmit 4, our well-loved
  527. and widely-used macOS file transfer app, we sat down with an
  528. incredibly exhaustive list of ideas, and &#8212; this’ll sound like I’m
  529. exaggerating but I’m mostly sure I’m not &#8212; we did it all.</p>
  531. <p>With one massive update we’ve brought everyone’s favorite
  532. file-transferring truck into the future with more speed, more
  533. servers, more features, more fixes, a better UI, and even Panic
  534. Sync. Everything from the core file transfer engine to the “Get
  535. Info” experience was rethought, overhauled, and improved.</p>
  536. </blockquote>
  538. <p>A tremendous update to one of my very favorite and most-depended-upon apps. Worth checking out just to see <a href="">the 3D rotating truck icon on their website</a>. On sale for one week only for just $35.</p>
  540. <div>
  541. <a  title="Permanent link to ‘Transmit 5’"  href="">&nbsp;★&nbsp;</a>
  542. </div>
  544. ]]></content>
  545.  </entry><entry>
  547.    <link rel="alternate" type="text/html" href="" />
  548. <link rel="shorturl" href="" />
  549. <id>,2017://1.33915</id>
  550. <published>2017-07-19T00:09:03Z</published>
  551. <updated>2017-07-19T00:09:05Z</updated>
  552. <author>
  553. <name>John Gruber</name>
  554. <uri></uri>
  555. </author>
  556. <summary type="text">In a broad sense, that’s my idea for the iPhone Pro — a premium-priced product that offers us early access to technologies and components that will be (or even just might be) in all iPhones in another year or two.
  557. </summary>
  558. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  559. <p>Rene Ritchie, &#8220;<a href="">iPhones of Future Past: Understanding iPhone 8</a>&#8221;:</p>
  561. <blockquote>
  562.  <p>iPhone 8 will simply let Apple impress in a different way &#8212; by
  563. including technologies that don&#8217;t yet reach iPhone scale. In other
  564. words, by bringing tomorrow&#8217;s iPhone to market today.</p>
  566. <p>In terms of the business, it&#8217;s really no different than getting an
  567. iPhone onto Verizon, onto China Mobile, with bigger and bigger
  568. displays, or with smaller displays again &#8212; it&#8217;s about annexing
  569. adjacent markets and maximizing the revenue potential for iPhone.</p>
  571. <p>As it becomes harder to sell more iPhones &#8212; the population of
  572. earth is now a limiting factor &#8212; selling <em>more of an iPhone</em>
  573. becomes beneficial. It&#8217;s the same benefit Apple gets from selling
  574. services revenue on top of iPhone, but in atoms, not bits.</p>
  575. </blockquote>
  577. <p>Ritchie is using the name &#8220;iPhone 8&#8221; to refer to what I&#8217;ve called the &#8220;iPhone Pro&#8221; &#8212; the high-end OLED-display model that I think might start at over $1000. Name aside, I think he&#8217;s got exactly the right idea on how Apple can position this: <em>a future iPhone today</em>.</p>
  579. <p>Honda used to sell a car in the U.S. called the Prelude. <a href="">Edmunds&#8217;s description</a>:</p>
  581. <blockquote>
  582.  <p>Honda established itself in America with the Civic and Accord &#8212;
  583. both good, solid but basic cars. But big profits in the automotive
  584. world don&#8217;t come from basic cars that sell for commodity prices.
  585. Those profits come from cars that get consumers so excited that
  586. they&#8217;ll pay a premium price just to have one. The Prelude was
  587. Honda&#8217;s first attempt at an exciting car.</p>
  589. <p>The Prelude was Honda&#8217;s technological leading edge. Features that
  590. are now expected from Honda, like the double-wishbone suspension
  591. under the Accord, fuel injection, and VTEC electronic variable
  592. valve timing system showed up first on the Prelude before
  593. migrating across the Honda line (though VTEC first showed up on
  594. the 1990 Acura NSX). The Prelude was also a test bed for some
  595. technologies that went nowhere, like four-wheel steering.</p>
  596. </blockquote>
  598. <p>In a broad sense, that&#8217;s my idea for the iPhone Pro &#8212; a premium-priced product that offers us early access to technologies and components that will be (or even just might be) in all iPhones in another year or two.</p>
  602.    ]]></content>
  603.  <title>★ iPhone Prelude</title></entry><entry>
  604. <title>The Return of Google Glass</title>
  605. <link rel="alternate" type="text/html" href="" />
  606. <link rel="shorturl" type="text/html" href="" />
  607. <link rel="related" type="text/html" href="" />
  608. <id>,2017:/linked//6.33914</id>
  609. <published>2017-07-18T18:36:57Z</published>
  610. <updated>2017-07-18T18:36:58Z</updated>
  611. <author>
  612. <name>John Gruber</name>
  613. <uri></uri>
  614. </author>
  615. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  616. <p>Laura Stevens, reporting for The Wall Street Journal:</p>
  618. <blockquote>
  619.  <p>Google parent Alphabet Inc. is relaunching Glass, its head-worn
  620. computer, targeting corporate customers after its initial version
  621. flopped because of privacy concerns.</p>
  623. <p>Dubbed Glass Enterprise Edition, the product has been in testing
  624. at about 50 companies, including Boeing Co., General Electric Co.
  625. and Volkswagen AG, Alphabet said Tuesday.</p>
  627. <p>The new device, which is designed to snap on eyeglass frames and
  628. display information, videos and images in the line of a person’s
  629. sight, allow workers to see instructional content. They can also
  630. use the device to broadcast what they are viewing back to others
  631. for real-time instruction.</p>
  632. </blockquote>
  634. <p>Still looks goofy (in fact, it pretty much looks the same), but I can see how it could prove popular in work environments so long as it&#8217;s useful. People ranging from mechanics to surgeons have long worn industrial-looking eyewear on the job.</p>
  636. <div>
  637. <a  title="Permanent link to ‘The Return of Google Glass’"  href="">&nbsp;★&nbsp;</a>
  638. </div>
  640. ]]></content>
  641.  </entry><entry>
  642. <title>Jonathan Chait: ‘Trumpcare Collapsed Because Republicans Cannot Govern’</title>
  643. <link rel="alternate" type="text/html" href="" />
  644. <link rel="shorturl" type="text/html" href="" />
  645. <link rel="related" type="text/html" href="" />
  646. <id>,2017:/linked//6.33913</id>
  647. <published>2017-07-18T17:28:59Z</published>
  648. <updated>2017-07-18T17:29:00Z</updated>
  649. <author>
  650. <name>John Gruber</name>
  651. <uri></uri>
  652. </author>
  653. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  654. <p>Jonathan Chait:</p>
  656. <blockquote>
  657.  <p>In truth, it was never possible to reconcile public standards for
  658. a humane health-care system with conservative ideology. In a pure
  659. market system, access to medical care will be unaffordable for a
  660. huge share of the public. Giving them access to quality care means
  661. mobilizing government power to redistribute resources, either
  662. through direct tax and transfers or through regulations that raise
  663. costs for the healthy and lower them for the sick. Obamacare uses
  664. both methods, and both are utterly repugnant and unacceptable to
  665. movement conservatives. That commitment to abstract
  666. anti-government dogma, without any concern for the practical
  667. impact, is the quality that makes the Republican Party unlike
  668. right-of-center governing parties in any other democracy. In no
  669. other country would a conservative party develop a plan for health
  670. care that every major industry stakeholder calls completely
  671. unworkable.</p>
  672. </blockquote>
  674. <p>The Republicans control the House, Senate, and White House, and cannot pass health insurance legislation. One can argue about why this is so, but I think Chait nails it: they can&#8217;t square their anti-government dogma with the need for the government to play a role in any humane health care system.</p>
  676. <div>
  677. <a  title="Permanent link to ‘Jonathan Chait: &#8216;Trumpcare Collapsed Because Republicans Cannot Govern&#8217;’"  href="">&nbsp;★&nbsp;</a>
  678. </div>
  680. ]]></content>
  681.  </entry><entry>
  682. <title>Garry Kasparov on Trump and Putin</title>
  683. <link rel="alternate" type="text/html" href="" />
  684. <link rel="shorturl" type="text/html" href="" />
  685. <link rel="related" type="text/html" href="" />
  686. <id>,2017:/linked//6.33912</id>
  687. <published>2017-07-18T16:53:59Z</published>
  688. <updated>2017-07-18T16:54:55Z</updated>
  689. <author>
  690. <name>John Gruber</name>
  691. <uri></uri>
  692. </author>
  693. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  694. <p>Garry Kasparov, in a column for The New York Daily News:</p>
  696. <blockquote>
  697.  <p>For autocrats, angry denial is the first phase of responding to
  698. accurate charges against them. &#8220;No! Never! A complete
  699. fabrication!&#8221;</p>
  701. <p>As evidence accumulates, this shifts to feigning ignorance and
  702. claiming misunderstanding, along with attempts to distract by
  703. slandering the accusers, blaming others for similar sins and
  704. discrediting the concept of knowable truth. &#8220;I didn&#8217;t know it was
  705. wrong! The media is out to get me! Others have done worse! Who
  706. knows what really happened?&#8221;</p>
  708. <p>When even this proves insufficient, it&#8217;s time for the final step,
  709. confession. Not the kind that is said to be good for the soul, but
  710. the aggressive, defiant boasting of someone who is sure that they
  711. won&#8217;t be punished in this life or the next for the crime they
  712. denied for so long. &#8220;I did it, but so what? There&#8217;s nothing wrong
  713. with it! What are you going to do about it?&#8221;</p>
  715. <p>After many months of denials, lies and distractions in an effort
  716. to dismiss the mounting evidence that the Trump campaign knowingly
  717. worked with Russia to win the 2016 presidential election, the
  718. Trump train is approaching the final station.</p>
  719. </blockquote>
  721. <p>It&#8217;s not like Kasparov knows anything about strategic thinking or Vladimir Putin.</p>
  723. <div>
  724. <a  title="Permanent link to ‘Garry Kasparov on Trump and Putin’"  href="">&nbsp;★&nbsp;</a>
  725. </div>
  727. ]]></content>
  728.  </entry><entry>
  729. <title>Only 45 Percent of Trump Voters Believe Don Jr. Met With the Russians, After Junior Admitted It</title>
  730. <link rel="alternate" type="text/html" href="" />
  731. <link rel="shorturl" type="text/html" href="" />
  732. <link rel="related" type="text/html" href="" />
  733. <id>,2017:/linked//6.33911</id>
  734. <published>2017-07-18T16:48:14Z</published>
  735. <updated>2017-07-18T16:48:38Z</updated>
  736. <author>
  737. <name>John Gruber</name>
  738. <uri></uri>
  739. </author>
  740. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  741. <p>John Aravosis:</p>
  743. <blockquote>
  744.  <p>Public Policy Polling has a <a href="">new poll</a> out that’s depressing as
  745. hell, and a sign of just how fact-deprived Trump voters truly are.</p>
  747. <p>Among other findings, only 45% of Trump voters think Donald Trump
  748. Jr. met with Russians last year to discuss their offer to help his
  749. father win the election. And 32% say it didn’t happen at all.</p>
  751. <p>This is after Donald Trump Jr. already admitted publicly that he
  752. met with the Russians, and Donald Trump Sr. tweeted the fact
  753. that his son met with the Russians. After all that, only 45%
  754. believe it.</p>
  755. </blockquote>
  757. <p>He not only admitted it, <a href="">he publicly released the emails documenting it</a>. </p>
  759. <div>
  760. <a  title="Permanent link to ‘Only 45 Percent of Trump Voters Believe Don Jr. Met With the Russians, After Junior Admitted It’"  href="">&nbsp;★&nbsp;</a>
  761. </div>
  763. ]]></content>
  764.  </entry><entry>
  765. <title>Dov Charney’s 2.0: Los Angeles Apparel</title>
  766. <link rel="alternate" type="text/html" href="" />
  767. <link rel="shorturl" type="text/html" href="" />
  768. <link rel="related" type="text/html" href="" />
  769. <id>,2017:/linked//6.33910</id>
  770. <published>2017-07-18T16:29:56Z</published>
  771. <updated>2017-07-18T16:29:58Z</updated>
  772. <author>
  773. <name>John Gruber</name>
  774. <uri></uri>
  775. </author>
  776. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  777. <p>Matthew Townsend, reporting for Bloomberg:</p>
  779. <blockquote>
  780.  <p>But American Apparel’s 2015 bankruptcy wiped out most of his net
  781. worth, so where would he get the money? Didn’t his tawdry past of
  782. sexual harassment allegations make him radioactive? And shouldn’t
  783. American Apparel’s collapse prove that making clothes in the U.S.
  784. is a fool’s errand?</p>
  786. <p>Yet here he is, at 48, overseeing a startup with seamstresses
  787. and fabric cutters and boxes of T-shirts waiting to be shipped
  788. across the country. He’s on, he&#8217;s riffing, he’s explaining the
  789. benefits of immigration, he’s envisioning a company that will
  790. someday hit $1 billion in revenue. (American Apparel topped out
  791. at $634 million in 2013.) “We’re building, grooving, growing,”
  792. Charney says.</p>
  794. <p>His new company, <a href="">Los Angeles Apparel</a>, was launched late last
  795. year as a wholesale business &#8212; just like American Apparel’s
  796. origins in 1989 &#8212; selling blank basics such as T-shirts and
  797. sweatshirts.</p>
  798. </blockquote>
  800. <p>Very similar brand aesthetic to American Apparel, too, but with Microgramma subbed in for Helvetica Neue as the company typeface.</p>
  802. <div>
  803. <a  title="Permanent link to ‘Dov Charney&#8217;s 2.0: Los Angeles Apparel’"  href="">&nbsp;★&nbsp;</a>
  804. </div>
  806. ]]></content>
  807.  </entry><entry>
  808. <title>Apple’s Risky Balancing Act With the Next iPhone</title>
  809. <link rel="alternate" type="text/html" href="" />
  810. <link rel="shorturl" type="text/html" href="" />
  811. <link rel="related" type="text/html" href="" />
  812. <id>,2017:/linked//6.33909</id>
  813. <published>2017-07-17T23:53:37Z</published>
  814. <updated>2017-07-17T23:53:38Z</updated>
  815. <author>
  816. <name>John Gruber</name>
  817. <uri></uri>
  818. </author>
  819. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  820. <p>Jason Snell, in a terrific column for Macworld:</p>
  822. <blockquote>
  823.  <p>This is one of those areas where Apple may be the victim of its
  824. own success. The iPhone is so popular a product that Apple can’t
  825. include any technology or source any part if it can’t be made more
  826. than 200 million times a year. If the supplier of a cutting-edge
  827. part Apple wants can only provide the company with 50 million per
  828. year, it simply can’t be used in the iPhone. Apple sells too many,
  829. too fast.</p>
  831. <p>Contrast that to Apple’s competition. On the smaller end, former
  832. Android chief Andy Rubin announced <a href="">the Essential phone</a>, but even
  833. Rubin admitted that he’d only be able to sell in thousands, not
  834. millions. Same for the <a href="">RED Hydrogen One</a> &#8212; groundbreaking phone,
  835. hardly likely to sell in any volume. The Google Pixel looks like
  836. it’s <a href="">in the one million range</a>. Apple’s biggest competitor,
  837. Samsung, has to deal with a scale more similar to Apple’s &#8212; but
  838. it’s still only expected to sell <a href="">50 or 60 million units of the
  839. flagship Galaxy S8</a>.</p>
  840. </blockquote>
  842. <p>As one DF reader (thanks, <em>SH</em>) put it in an email a few weeks ago:</p>
  844. <blockquote>
  845.  <p>People commonly think that scale is an unambiguously good thing in
  846. production, but the tremendous scale at which Apple operates shows
  847. this not to be the case. Annual iPhone production is so large that
  848. Apple is likely experiencing <em>dis</em>economies of scale, a phenomenon
  849. one doesn&#8217;t often hear about. What significant, break-through
  850. technology can a company practically introduce to 300 million new
  851. devices in a year? I’m not even sure it would be physically
  852. possible to manufacture 300 million OLED screens in a single year,
  853. for instance. Much less any more dramatic change, like new
  854. materials or manufacturing processes.</p>
  855. </blockquote>
  857. <p>It&#8217;s not just this year that Apple has to pull off a risky balancing act regarding the features and components of the new flagship iPhone. It&#8217;s <em>every</em> year. I don&#8217;t think that balance is attainable without a change in strategy to add a new higher-priced lower-volume tier.</p>
  859. <div>
  860. <a  title="Permanent link to ‘Apple’s Risky Balancing Act With the Next iPhone’"  href="">&nbsp;★&nbsp;</a>
  861. </div>
  863. ]]></content>
  864.  </entry><entry>
  865. <title>Jeet Heer: ‘We Are Living in the Coen Brothers’ Darkest Comedy’</title>
  866. <link rel="alternate" type="text/html" href="" />
  867. <link rel="shorturl" type="text/html" href="" />
  868. <link rel="related" type="text/html" href="" />
  869. <id>,2017:/linked//6.33907</id>
  870. <published>2017-07-17T17:00:50Z</published>
  871. <updated>2017-07-17T17:03:01Z</updated>
  872. <author>
  873. <name>John Gruber</name>
  874. <uri></uri>
  875. </author>
  876. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  877. <p>Jeet Heer, writing for The New Republic:</p>
  879. <blockquote>
  880.  <p>Imagine a group of dunderheaded Americans who think they would benefit from a covert alliance with the Russian government. They make overtures to that country’s ambassador, blithely ignorant that they’ll be monitored by U.S. intelligence. A series of cascading mistakes ultimately brings disaster crashing down on their heads.</p>
  882. <p>That might sound like a summary of the latest news about the White House, but it is also the plot of <em>Burn After Reading</em>, the 2008 film that stands as singularly prophetic of the Trump era. The Coen Brothers’ black comedy echoes this unique period in history not only because of the Trump campaign’s collusion with Russian operatives, but the wider culture of deceit that made Donald Trump’s rise possible. More than just a satire on espionage, the movie is a scathing critique of modern America as a superficial, post-political society where cheating of all sorts comes all too easily.</p>
  883. </blockquote>
  885. <div>
  886. <a  title="Permanent link to ‘Jeet Heer: &#8216;We Are Living in the Coen Brothers’ Darkest Comedy&#8217;’"  href="">&nbsp;★&nbsp;</a>
  887. </div>
  889. ]]></content>
  890.  </entry><entry>
  891. <title>Benedict Evans: ‘Creation and Consumption’</title>
  892. <link rel="alternate" type="text/html" href="" />
  893. <link rel="shorturl" type="text/html" href="" />
  894. <link rel="related" type="text/html" href="" />
  895. <id>,2017:/linked//6.33906</id>
  896. <published>2017-07-17T16:55:08Z</published>
  897. <updated>2017-07-17T16:57:25Z</updated>
  898. <author>
  899. <name>John Gruber</name>
  900. <uri></uri>
  901. </author>
  902. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  903. <p>Benedict Evans:</p>
  905. <blockquote>
  906.  <p>It seems to me that when people talk about what you ‘can’t’ do on a device, there are actually two different meanings of ‘can’t’ in computing. There is ‘can’t’ as meaning the feature doesn’t exist, and there is ‘can’t’ as meaning you don’t know how to do it. If you don’t know how to do it, the feature might as well not be there. So, there is what an expert can’t do on a smartphone or tablet that they could do on a PC. But then there are all of the things that a normal person (the other 90% or 95%) can’t do on a PC but can do on a smartphone, because the step change in user interface abstraction and simplicity means that they know how to do it on a phone and didn’t know how to do it on a PC. That is, the step change in user interface models that comes with the shift from Windows and Mac to iOS and Android is really a shift in the accessibility of capability. A small proportion of people might temporarily go from can to can’t, but vastly more go from can’t to can.</p>
  907. </blockquote>
  909. <div>
  910. <a  title="Permanent link to ‘Benedict Evans: &#8216;Creation and Consumption&#8217;’"  href="">&nbsp;★&nbsp;</a>
  911. </div>
  913. ]]></content>
  914.  </entry><entry>
  915. <title>Chaim Gartenberg: ‘The Future of the Smartwatch Should Be Smart Watch Bands’</title>
  916. <link rel="alternate" type="text/html" href="" />
  917. <link rel="shorturl" type="text/html" href="" />
  918. <link rel="related" type="text/html" href="" />
  919. <id>,2017:/linked//6.33905</id>
  920. <published>2017-07-17T15:59:07Z</published>
  921. <updated>2017-07-17T16:11:46Z</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>Chaim Gartenberg, writing for The Verge:</p>
  929. <blockquote>
  930.  <p>Despite the best efforts from Apple (with the Apple Watch), Google (with Android Wear), Samsung (with the Galaxy Gear), Pebble (with the, uh, Pebble), and dozens of other companies, the dream of the smartwatch hasn’t really taken off. Turns out that turning a smartphone into a wrist device isn’t really that appealing. Even if you can somehow get the right balance of battery life, device size, and developer support, people just aren’t really interested in getting anything more than notifications and fitness tracking from the devices they wear on their wrists.</p>
  931. </blockquote>
  933. <p>I disagree completely. I&#8217;m on my way home from a family vacation at Disney World. I saw Apple Watches <em>everywhere</em>. (I would estimate that over 95 percent of them were the aluminum models.) Apple Watch is a hit product.</p>
  935. <p>I think notifications and fitness tracking simply are what people want from their smart watches.</p>
  937. <p>I think smart bands for non-smart watches are a non-starter &#8212; and I say that as someone who packed two mechanical watches and no Apple Watch for this trip. The analog nature of mechanical watches is central to their appeal.</p>
  939. <div>
  940. <a  title="Permanent link to ‘Chaim Gartenberg: &#8216;The Future of the Smartwatch Should Be Smart Watch Bands&#8217;’"  href="">&nbsp;★&nbsp;</a>
  941. </div>
  943. ]]></content>
  944.  </entry><entry>
  945. <title>Apple Previews New Emoji</title>
  946. <link rel="alternate" type="text/html" href="" />
  947. <link rel="shorturl" type="text/html" href="" />
  948. <link rel="related" type="text/html" href="" />
  949. <id>,2017:/linked//6.33904</id>
  950. <published>2017-07-17T15:56:20Z</published>
  951. <updated>2017-07-17T15:57:20Z</updated>
  952. <author>
  953. <name>John Gruber</name>
  954. <uri></uri>
  955. </author>
  956. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  957. <p>Apple:</p>
  959. <blockquote>
  960.  <p>In celebration of World Emoji Day, Apple is sharing some of the new emoji coming to iOS, macOS and watchOS later this year.</p>
  961. </blockquote>
  963. <p>It&#8217;s crazy to me that there hasn&#8217;t been a sandwich emoji until now.</p>
  965. <div>
  966. <a  title="Permanent link to ‘Apple Previews New Emoji’"  href="">&nbsp;★&nbsp;</a>
  967. </div>
  969. ]]></content>
  970.  </entry><entry>
  971. <title>Thom Holwerda: ‘Android Is a Dead End’</title>
  972. <link rel="alternate" type="text/html" href="" />
  973. <link rel="shorturl" type="text/html" href="" />
  974. <link rel="related" type="text/html" href="" />
  975. <id>,2017:/linked//6.33903</id>
  976. <published>2017-07-17T15:34:56Z</published>
  977. <updated>2017-07-17T15:34:59Z</updated>
  978. <author>
  979. <name>John Gruber</name>
  980. <uri></uri>
  981. </author>
  982. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  983. <p>Thom Holwerda, writing for OSNews:</p>
  985. <blockquote>
  986.  <p>Android in its current form suffers from several key architectural
  987. problems - it&#8217;s not nearly as resource-efficient as, say, iOS, has
  988. consistent update problems, and despite hefty hardware, still
  989. suffers from the occasional performance problems, among other
  990. things - that Google clearly hasn&#8217;t been able to solve. It feels
  991. like Android is in limbo, waiting for something, as if Google is
  992. working on something else that will eventually succeed Android.</p>
  994. <p>Is that something <a href="">Fuchsia</a>? Is <a href="">Project Treble</a> part of the
  995. plan, to make it easier for Google to eventually replace Android&#8217;s
  996. Linux base with something else? If Android as it exists today was
  997. salvageable, why are some of the world&#8217;s greatest operating
  998. systems engineers employed by Google not working on Android, <a href="">but
  999. on Fuchsia</a>? If Fuchsia is just a research operating system,
  1000. why did its developers recently add <a href="">actual wallpapers to the
  1001. repository</a>? Why does every design choice for Fuchsia seem
  1002. specifically designed for and targeted at solving Android&#8217;s core
  1003. problems?</p>
  1004. </blockquote>
  1006. <div>
  1007. <a  title="Permanent link to ‘Thom Holwerda: &#8216;Android Is a Dead End&#8217;’"  href="">&nbsp;★&nbsp;</a>
  1008. </div>
  1010. ]]></content>
  1011.  </entry><entry>
  1012. <title>Android Killed Windows Phone</title>
  1013. <link rel="alternate" type="text/html" href="" />
  1014. <link rel="shorturl" type="text/html" href="" />
  1015. <link rel="related" type="text/html" href="" />
  1016. <id>,2017:/linked//6.33902</id>
  1017. <published>2017-07-17T15:26:32Z</published>
  1018. <updated>2017-07-17T18:24:47Z</updated>
  1019. <author>
  1020. <name>John Gruber</name>
  1021. <uri></uri>
  1022. </author>
  1023. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1024. <p>Dieter Bohn, The Verge:</p>
  1026. <blockquote>
  1027.  <p>So while Microsoft didn’t do itself any favors, I’d argue strongly
  1028. that all these machinations and flailings weren’t a response (or
  1029. weren’t only a response) to the iPhone. The real enemy was the
  1030. company that had set its sights on Microsoft’s phone ambitions
  1031. since before the iPhone was released.</p>
  1033. <p>That company was Google, of course, and it only tangentially
  1034. wanted to take on the iPhone. Google’s real target was always
  1035. Microsoft, and it hit the bullseye.</p>
  1036. </blockquote>
  1038. <p>This is so obvious to me I&#8217;m surprised Bohn even thought to write it, but judging by the response, it seems a lot of people haven&#8217;t really thought about this. Conceptually, the iPhone changed the industry by raising the bar for just how a modern phone should work. Android and Windows Phone were designed in the iPhone&#8217;s wake.</p>
  1040. <p>But business-wise, the iPhone is exactly like the Mac. It&#8217;s not something Apple licenses to other companies. So all other companies that want to make phones but can&#8217;t create their own OS need something to license. On the PC, that OS is Windows. For mobile, it&#8217;s Android. It&#8217;s hard to imagine how different the world would be today if Microsoft had created the Android of mobile.</p>
  1042. <div>
  1043. <a  title="Permanent link to ‘Android Killed Windows Phone’"  href="">&nbsp;★&nbsp;</a>
  1044. </div>
  1046. ]]></content>
  1047.  </entry><entry>
  1048. <title>Squarespace</title>
  1049. <link rel="alternate" type="text/html" href="" />
  1050. <link rel="shorturl" type="text/html" href="" />
  1051. <link rel="related" type="text/html" href="" />
  1052. <id>,2017:/linked//6.33901</id>
  1053. <published>2017-07-16T00:19:58Z</published>
  1054. <updated>2017-07-16T00:20:00Z</updated>
  1055. <author>
  1056. <name>John Gruber</name>
  1057. <uri></uri>
  1058. </author>
  1059. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1060. <p>My thanks to Squarespace for once again sponsoring the DF RSS feed.</p>
  1062. <p>Create a beautiful portfolio website with Squarespace. You can showcase your work to the world with stunning galleries and project pages. Try Squarespace for free. When you’re ready to subscribe, <a href="">get 10 percent off at</a> with offer code <strong>DARING17</strong>.</p>
  1064. <div>
  1065. <a  title="Permanent link to ‘Squarespace’"  href="">&nbsp;★&nbsp;</a>
  1066. </div>
  1068. ]]></content>
  1069.  </entry><entry>
  1071.    <link rel="alternate" type="text/html" href="" />
  1072. <link rel="shorturl" href="" />
  1073. <id>,2017://1.33900</id>
  1074. <published>2017-07-14T00:01:51Z</published>
  1075. <updated>2017-07-18T00:03:14Z</updated>
  1076. <author>
  1077. <name>John Gruber</name>
  1078. <uri></uri>
  1079. </author>
  1080. <summary type="text">Apple is months ahead of these rumors — what we hear now with reports like this are just echoes of decisions that have already been made.</summary>
  1081. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1082. <p>Yours truly, <a href="">in a tweet on July 7</a>:</p>
  1084. <blockquote>
  1085.  <p>I’ve heard that inductive charging will (a) be sold separately,
  1086. and (b) might be late, waiting for iOS 11.1 (a la Portrait mode
  1087. last year).
  1088. <a href=""></a></p>
  1089. </blockquote>
  1091. <p>On July 11, Mark Sullivan reported a piece for Fast Company under the headline “<a href="">Source: A &#8216;Sense of Panic&#8217; at Apple as the Next Flagship iPhone’s Software Problems Persist</a>”:</p>
  1093. <blockquote>
  1094.  <p>June was a tense month for the engineers and designers on Apple’s
  1095. iPhone team with “a sense of panic in the air,” a source with
  1096. knowledge of the situation tells me.</p>
  1098. <p>The company has been working feverishly to fix software problems
  1099. in its hotly anticipated 10th-anniversary iPhone that could
  1100. ultimately cause production and delivery delays, the source says.
  1101. If the software problems aren’t resolved quickly, the new flagship
  1102. iPhone could even launch with major features disabled. [&#8230;]</p>
  1104. <p>One of those is wireless charging. The iPhone 8 &#8212; let’s call it
  1105. that for now &#8212; will reportedly use a type of inductive charging,
  1106. where the phone sits directly on a separate charging device. (Our
  1107. source believes Apple is using the Qi wireless charging standard,
  1108. or a variant of it.) The wireless charging components, which are
  1109. provided by chipmaker Broadcom Ltd., are not the key issue, the
  1110. source said; it’s the software that’s not ready for prime time.</p>
  1111. </blockquote>
  1113. <p>That sort of matches up with what I heard — that inductive charging might miss the September debut because the software isn’t ready. I have not heard anything about any sort of “panic”. Summers are crunch time for iOS engineers, and the deadline for iOS 11.0 is probably no more than a month away at this point. But if inductive charging has to wait until 11.1 in October or November, it’ll be a disappointment, but not much more so than having to wait for the iPhone 7 Plus’s Portrait Mode to come out of beta last fall.</p>
  1115. <p><a href="">Jonny Evans, writing for Computerworld yesterday</a>:</p>
  1117. <blockquote>
  1118.  <p>It’s the same thing every year these days. It’s incredibly
  1119. predictable.</p>
  1121. <p>It goes like this: Having reported every claimed product feature
  1122. people then switch to criticizing all those features, and &#8212; when
  1123. the shelf life on &#8220;anti-reports&#8221; of this kind time out, the
  1124. self-same sources swiftly shift to shuffling speculation saying
  1125. such-and-such features will apparently be &#8220;delayed&#8221;. Seriously!</p>
  1127. <p>All of this drama and Apple hasn’t even announced anything yet.</p>
  1129. <p>How can something that hasn’t been announced ever be delayed?</p>
  1130. </blockquote>
  1132. <p>“Apple engineers are panicking” is an exciting story. “Apple engineers are in crunch mode to finish iOS 11.0 just like they are every summer” is not.</p>
  1134. <p>It could be that things are in worse shape than usual, and there truly is a panic to get iOS 11&#8217;s support for new iPhone hardware finished on schedule. But everything I&#8217;ve heard suggests it&#8217;s the same as usual at this point in the summer: busy down to the wire, yes; frantic panic, no.</p>
  1136. <p>Today Sullivan has another report, <a href="">claiming Apple is trying to integrate laser sensors into the rear of the high-end new iPhone</a>:</p>
  1138. <blockquote>
  1139.  <p>A source with knowledge of the situation tells Fast Company Apple
  1140. is working hard to add a rear-facing 3D laser system to the back
  1141. of one of the new iPhones to be announced this fall. [&#8230;]</p>
  1143. <p>The source said the VSCEL laser system is probably intended for
  1144. the 10th anniversary iPhone (which may be called the iPhone 8 or
  1145. the iPhone Pro or, hopefully, the iPhone X). Whether the sensor
  1146. will be included in that phone, or a 2018 iPhone, depends on the
  1147. progress the Apple engineers make in integrating the laser system
  1148. into the phone, our source says.</p>
  1149. </blockquote>
  1151. <p>This sounds cool &#8212; and also sounds like the sort of feature that could justify <a href="">a significantly higher price for an iPhone Pro</a>.</p>
  1153. <p>But I think it&#8217;s bonkers to think that Apple is still working on hardware decisions like this in the middle of July. Apple is super-secretive about this stuff, but from what I&#8217;ve gathered over the years, by this state in the game the hardware design has long been decided. They&#8217;re in the late stages of <a href="">validation testing</a>, not designing.</p>
  1155. <p><a href="">Greg Koenig on Twitter two days ago</a>:</p>
  1157. <blockquote>
  1158.  <p>For a volume Sep. launch, production tooling is being ground right
  1159. now. It’s been pencils down for a while.</p>
  1161. <p>If not? Huge shit show.</p>
  1162. </blockquote>
  1164. <p>With software Apple can (and does) play a bit fast and loose. iOS 11.0 won&#8217;t be baked until late August. But software can (and always is) patched. Hardware doesn&#8217;t work like that. Many of the decisions related to the hardware on this year&#8217;s new iPhones were made two years ago. (And there are decisions being made now for 2019&#8217;s new iPhones.)</p>
  1166. <p>Is there a 3D laser sensor on the back of the new iPhone? Is there a Touch ID sensor?<sup id="fnr1-2017-07-13"><a href="#fn1-2017-07-13">1</a></sup> I don&#8217;t know. But Apple knows, and has known for a while. Months, even.</p>
  1168. <p>If the hardware were still up in the air today, it&#8217;d be an impossible target for the software, never mind for Apple&#8217;s incredibly high-scale production ramp. I believe Apple is months ahead of these rumors &#8212; what we hear now with reports like this are just echoes of decisions that have already been made.</p>
  1170. <div class="footnotes">
  1171. <hr />
  1172. <ol>
  1173. <li id="fn1-2017-07-13">
  1174. <p>Might as well address this rumor here. A ton of readers have expressed deep skepticism regarding reports that the OLED iPhone doesn&#8217;t have a Touch ID sensor. &#8220;<em>That&#8217;s impossible, Apple Pay relies on Touch ID</em>&#8221; is the basic sentiment. I think it&#8217;s possible that there&#8217;s no Touch ID sensor on the OLED iPhone, but if that&#8217;s the case, then the new 3D face scanner has to be as good or better than Touch ID in every regard. It has to be just as fast, just as accurate, and just as trustworthy. It also would have to work from a wide range of angles. <a href="">As Rene Ritchie has sagely written</a>, the end game is &#8220;persistent, ambient authentication&#8221; &#8212; fingerprints are not particularly magic.</p>
  1176. <p>But, if the new iPhone ships without a Touch ID sensor <em>and</em> there is no replacement authentication technology that is as good or better than Touch ID &#8212; that would be a dead canary in the coal mine.&nbsp;<a href="#fnr1-2017-07-13"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1177. </li>
  1178. </ol>
  1179. </div>
  1183.    ]]></content>
  1184.  <title>★ iPhone Silly Season</title></entry><entry>
  1185. <title>The Mac Mini Turns 1,000 Days Old Today</title>
  1186. <link rel="alternate" type="text/html" href="" />
  1187. <link rel="shorturl" type="text/html" href="" />
  1188. <link rel="related" type="text/html" href="" />
  1189. <id>,2017:/linked//6.33899</id>
  1190. <published>2017-07-14T00:01:01Z</published>
  1191. <updated>2017-07-14T00:01:04Z</updated>
  1192. <author>
  1193. <name>John Gruber</name>
  1194. <uri></uri>
  1195. </author>
  1196. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1197. <p>&#8220;<a href="">The Mac Mini remains a product in our lineup</a>.&#8221;</p>
  1199. <div>
  1200. <a  title="Permanent link to ‘The Mac Mini Turns 1,000 Days Old Today’"  href="">&nbsp;★&nbsp;</a>
  1201. </div>
  1203. ]]></content>
  1204.  </entry><entry>
  1205. <title>Font Choice Leads to Scandal Threatening the Pakistani PM</title>
  1206. <link rel="alternate" type="text/html" href="" />
  1207. <link rel="shorturl" type="text/html" href="" />
  1208. <link rel="related" type="text/html" href="" />
  1209. <id>,2017:/linked//6.33898</id>
  1210. <published>2017-07-13T19:10:35Z</published>
  1211. <updated>2017-07-13T19:23:33Z</updated>
  1212. <author>
  1213. <name>John Gruber</name>
  1214. <uri></uri>
  1215. </author>
  1216. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1217. <p>Sune Engel Rasmussen and Pádraig Collins, reporting for The Guardian:</p>
  1219. <blockquote>
  1220.  <p>The daughter of Pakistan’s prime minister has become subject of ridicule in her home country after forensic experts cast doubts on documents central to her defence against corruption allegations. [&#8230;]</p>
  1222. <p>Documents claiming that Mariam Nawaz Sharif was only a trustee of the companies that bought the London flats, are dated February 2006, and appear to be typed in Microsoft Calibri.</p>
  1224. <p>But the font was only made commercially available in 2007, leading to suspicions that the documents are forged.</p>
  1225. </blockquote>
  1227. <p>The website Dawn <a href="">reached out to Calibri designer Lucas de Groot for comment</a>:</p>
  1229. <blockquote>
  1230.  <p>In a separate email, de Groot, the font designer himself, said that while in theory it would have been possible to create a document using Calibri in 2006, the font would have to be obtained from a beta operating system, &#8220;from the hands of computer nerds&#8221;.</p>
  1232. <p>&#8220;Why would anyone use a completely unknown font for an official document in 2006?&#8221; he went on to question.</p>
  1233. </blockquote>
  1235. <div>
  1236. <a  title="Permanent link to ‘Font Choice Leads to Scandal Threatening the Pakistani PM’"  href="">&nbsp;★&nbsp;</a>
  1237. </div>
  1239. ]]></content>
  1240.  </entry><entry>
  1241. <title>The Internet Is Fucked (Again)</title>
  1242. <link rel="alternate" type="text/html" href="" />
  1243. <link rel="shorturl" type="text/html" href="" />
  1244. <link rel="related" type="text/html" href="" />
  1245. <id>,2017:/linked//6.33897</id>
  1246. <published>2017-07-13T16:55:25Z</published>
  1247. <updated>2017-07-13T16:57:15Z</updated>
  1248. <author>
  1249. <name>John Gruber</name>
  1250. <uri></uri>
  1251. </author>
  1252. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1253. <p>Nilay Patel, writing for The Verge:</p>
  1255. <blockquote>
  1256.  <p>Most of these things are still true, even after the Obama-era FCC under Chairman Tom Wheeler reclassified internet access as a Title II telecommunications service and imposed strict net neutrality rules on wired and wireless internet providers. And most of these things will get even worse when Pai pushes through his plan to rescind Title II and those rules, despite widespread public outcry.</p>
  1258. <p>The lack of competition in the broadband access market is so acute that it doesn’t matter if <a href="">Comcast is still the most-hated company in America</a>, or that Spectrum (formerly Time Warner Cable) has <a href="">the worst customer service</a>: you don’t have a choice, so you just have to pay them anyway. Consumers and tech publications can review and argue and debate the merits of products from Apple, Google, and Microsoft, but you just have to take what you get from your ISP.</p>
  1259. </blockquote>
  1261. <div>
  1262. <a  title="Permanent link to ‘The Internet Is Fucked (Again)’"  href="">&nbsp;★&nbsp;</a>
  1263. </div>
  1265. ]]></content>
  1266.  </entry><entry>
  1268.    <link rel="alternate" type="text/html" href="" />
  1269. <link rel="shorturl" href="" />
  1270. <id>,2017://1.33896</id>
  1271. <published>2017-07-12T20:44:16Z</published>
  1272. <updated>2017-07-12T22:51:02Z</updated>
  1273. <author>
  1274. <name>John Gruber</name>
  1275. <uri></uri>
  1276. </author>
  1277. <summary type="text">What I finally decided was the most obvious replacement possible: selling Deck-like ads on my own, directly to advertisers, much like I do with the weekly feed sponsorships.</summary>
  1278. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1279. <p><a href="">After the Deck Network closed at the end of March</a>, I spent a long while thinking about what I could do to replace it. I’m a slow thinker.</p>
  1281. <p>What I finally decided was the most obvious replacement possible: selling Deck-like ads on my own, directly to advertisers, much like I do with <a href="">the weekly feed sponsorships</a>. It started in June with spots from Field Notes and Rogue Amoeba. So far in July, I’ve added MailChimp and Jamf. These are all longtime supporters of Daring Fireball, and I thank them greatly for helping to get this new thing off the ground. (Rogue Amoeba deserves special thanks: they’ve been the first sponsor of every single ad opportunity I’ve experimented with at DF over the years, including <a href="">the  debut week of the feed sponsorship</a>.)</p>
  1283. <p>So here’s the deal. I don’t know how best to sell this spot. For now, I’m going with the following:</p>
  1285. <ul>
  1286. <li>A maximum of 5 sponsors per month. Each sponsor will get 20 percent of all page views on DF (including the very popular <a href="">Markdown Syntax Documentation</a> and online <a href="">Dingus</a> pages).</li>
  1287. <li>If a sponsor wants to buy more than one spot, they can, and will get a discount for doing so. I.e. a sponsor could buy 2/5 spots to get 40 percent of all DF pages views in a given month, 3/5 for 60 percent, etc.</li>
  1288. <li>A sponsor can provide two different ads for the month if they want. Each of the two ads will get 10 percent of the month’s page views.</li>
  1289. </ul>
  1291. <p>I think this ad format is a great opportunity for everyone: sponsors, me, and DF readers.</p>
  1293. <p>For sponsors, you get to be the only graphical ad on the page each time your ad is shown. And given DF’s visual style, most of the time the ad will be <em>the only graphical element on the entire page</em> other than the DF logo mark, and <em>the only color</em> on the page other than good old #4a525a slate gray. The ads are relatively small, but I am confident they are more <em>noticeable</em> in a non-objectionable way than ads on just about any other website in the world. The ads on Daring Fireball stand out without being the least bit obtrusive. That’s the sweet spot for ads, in my opinion.</p>
  1295. <p>For readers, these are ads that, again, are visually unobjectionable, and which offer the most privacy you could hope for. Not only is there no tracking involved, there is no JavaScript involved. They’re just images, text, and HTML links. (<a href="">The images are even served from itself</a>.) You have my word that I will never allow tracking via these or any other ads on Daring Fireball without posting a big prominent “OK, DF Ads Are Now Tracking You” post on the site. I don&#8217;t expect <em>ever</em> to allow this. </p>
  1297. <p>If you&#8217;re a prospective sponsor, you might be thinking, &#8220;<em>Wait a minute, &#8216;no tracking&#8217; sounds good, but if they&#8217;re not tracked, how will I know how my ad performs?</em>&#8221; Easy. Do what (for example) <a href="">Rogue Amoeba</a> did, and provide a custom URL for the ad. Then you can track your own hits to that URL and trace them to the ad on Daring Fireball. Or just look at your referral stats (but <a href="">I highly recommend sponsors use a custom URL</a>). This is something that&#8217;s always baffled me about ad tracking &#8212; if you pay (say) Facebook for an ad, why in the world would you, the advertiser, trust Facebook&#8217;s numbers for how the ad performed? Measure the performance yourself, and you&#8217;ll know you&#8217;re getting the truth.</p>
  1299. <p>Likewise, if you&#8217;re simply a reader, do <em>not</em> click ads mindlessly thinking you&#8217;re helping. Sponsors do not pay per click, and even if they did, I wouldn&#8217;t want them paying for mindless clicks. If you want to support DF, just take a look at the ads, and when one genuinely seems interesting to you, check it out. That&#8217;s all I need.</p>
  1301. <p>For me, the ads can generate some money to make up for the revenue that was previously generated by The Deck (maybe more, depending on how it turns out — I really don’t know what to predict here), and I can sleep soundly at night because the ads (a) look good, (b) load super fast, and (c) respect the privacy of DF readers.</p>
  1303. <p>I have a few spots open for the remainder of July, and August is currently wide open. If you’re interested, get in touch via <a href="">the same email address I use for the RSS feed sponsorships</a>. (There are a couple of openings left for the weekly sponsorships this summer too, and they can be bundled with these new display ads at a discount. Get in touch.)</p>
  1307.    ]]></content>
  1308.  <title>★ New on Daring Fireball: Display Ads</title></entry><entry>
  1309. <title>Michael Tsai on Fantastical 2.4 for Mac</title>
  1310. <link rel="alternate" type="text/html" href="" />
  1311. <link rel="shorturl" type="text/html" href="" />
  1312. <link rel="related" type="text/html" href="" />
  1313. <id>,2017:/linked//6.33895</id>
  1314. <published>2017-07-12T19:28:43Z</published>
  1315. <updated>2017-07-12T19:32:19Z</updated>
  1316. <author>
  1317. <name>John Gruber</name>
  1318. <uri></uri>
  1319. </author>
  1320. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1321. <p>Michael Tsai on <a href="">the latest update to Fantastical for Mac</a>:</p>
  1323. <blockquote>
  1324.  <p>It’s like they read my mind and implemented my four most-wanted features. Great update.</p>
  1325. </blockquote>
  1327. <p>It really is a great update. I’m not even sure what to ask for at this point. No app is ever “done”, but at this point Fantastical feels feature complete.</p>
  1329. <div>
  1330. <a  title="Permanent link to ‘Michael Tsai on Fantastical 2.4 for Mac’"  href="">&nbsp;★&nbsp;</a>
  1331. </div>
  1333. ]]></content>
  1334.  </entry><entry>
  1335. <title>Kottke’s Buyer’s Guide for Next Month’s Solar Eclipse</title>
  1336. <link rel="alternate" type="text/html" href="" />
  1337. <link rel="shorturl" type="text/html" href="" />
  1338. <link rel="related" type="text/html" href="" />
  1339. <id>,2017:/linked//6.33894</id>
  1340. <published>2017-07-12T17:56:16Z</published>
  1341. <updated>2017-07-12T17:59:42Z</updated>
  1342. <author>
  1343. <name>John Gruber</name>
  1344. <uri></uri>
  1345. </author>
  1346. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1347. <p>Jason Kottke:</p>
  1349. <blockquote>
  1350.  <p>On August 21, 2017 across the entire United States, the Moon will move in front of the Sun, partially blocking it from our view. For those on <a href="">the path of totality</a>, the Moon will entirely block out the Sun for more than 2 minutes. I’ve been looking forward to seeing a total solar eclipse since I was a little kid, so I’ve been doing a lot of research on what to buy to enjoy the eclipse safely. Here’s what I’ve come up with.</p>
  1351. </blockquote>
  1353. <div>
  1354. <a  title="Permanent link to ‘Kottke’s Buyer’s Guide for Next Month’s Solar Eclipse’"  href="">&nbsp;★&nbsp;</a>
  1355. </div>
  1357. ]]></content>
  1358.  </entry><entry>
  1359. <title>Google Pays Academics for Publishing Favorable Articles About Google</title>
  1360. <link rel="alternate" type="text/html" href="" />
  1361. <link rel="shorturl" type="text/html" href="" />
  1362. <link rel="related" type="text/html" href="" />
  1363. <id>,2017:/linked//6.33893</id>
  1364. <published>2017-07-12T16:34:29Z</published>
  1365. <updated>2017-07-12T16:41:21Z</updated>
  1366. <author>
  1367. <name>John Gruber</name>
  1368. <uri></uri>
  1369. </author>
  1370. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1371. <p>Madison Malone Kircher, writing for New York Magazine:</p>
  1373. <blockquote>
  1374.  <p>Over the last ten years, Google (er, um, Alphabet) has paid thousands of dollars to people in the academic community working on research that directly involves the company’s business, <a href="">The Wall Street Journal reported earlier Tuesday</a>. Dollar amounts ranged from $5,000 to $400,000, and Google’s financial contributions to the research were often not disclosed in the finished products, the Journal also reported. A former Google employee said the company had assembled a list of research papers, complete with “working titles, abstracts and budgets,” Google wanted to see produced and then used that list to find academics willing to work with them on those projects. Around 100 such papers have been funded by Google since 2009.</p>
  1375. </blockquote>
  1377. <p>I love this bit from the Journal story:</p>
  1379. <blockquote>
  1380.  <p>University of Illinois law professor Paul Heald pitched an idea on copyrights he thought would be useful to Google, and he received $18,830 to fund the work. <a href="">The paper</a>, published in 2012, didn’t mention his sponsor. “Oh, wow. No, I didn’t. That’s really bad,” he said in an interview. “That’s purely oversight.”</p>
  1381. </blockquote>
  1383. <p>“Oh, wow”. He’s shocked — <em>shocked</em> — that he himself didn’t disclose this. <a href="">The Journal even got him to pose for a photograph</a> — he’s got exactly the deer-in-the-headlights “<em>Why did I agree to this interview?</em>” look on his face that you’d expect.</p>
  1385. <p>Don’t be ethical.</p>
  1387. <div>
  1388. <a  title="Permanent link to ‘Google Pays Academics for Publishing Favorable Articles About Google’"  href="">&nbsp;★&nbsp;</a>
  1389. </div>
  1391. ]]></content>
  1392.  </entry><entry>
  1393. <title>Android Police: ‘This Is the 2017 Google Pixel “XL”’</title>
  1394. <link rel="alternate" type="text/html" href="" />
  1395. <link rel="shorturl" type="text/html" href="" />
  1396. <link rel="related" type="text/html" href="" />
  1397. <id>,2017:/linked//6.33892</id>
  1398. <published>2017-07-11T22:47:02Z</published>
  1399. <updated>2017-07-12T00:40:57Z</updated>
  1400. <author>
  1401. <name>John Gruber</name>
  1402. <uri></uri>
  1403. </author>
  1404. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1405. <p>Looks great. If this is legit, they’ll sell thousands more of them than last year.</p>
  1407. <div>
  1408. <a  title="Permanent link to ‘Android Police: ‘This Is the 2017 Google Pixel “XL”’’"  href="">&nbsp;★&nbsp;</a>
  1409. </div>
  1411. ]]></content>
  1412.  </entry><entry>
  1413. <title>Apple Extends Free Repairs of First-Generation Apple Watches With Detached Back Covers</title>
  1414. <link rel="alternate" type="text/html" href="" />
  1415. <link rel="shorturl" type="text/html" href="" />
  1416. <link rel="related" type="text/html" href="" />
  1417. <id>,2017:/linked//6.33891</id>
  1418. <published>2017-07-11T21:01:13Z</published>
  1419. <updated>2017-07-11T21:13:04Z</updated>
  1420. <author>
  1421. <name>John Gruber</name>
  1422. <uri></uri>
  1423. </author>
  1424. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1425. <p>It&#8217;s good that Apple is doing this, but the fact that these things are just glued together shows how different Apple Watches are from traditional mechanical watches. You can buy <a href="">a $60 watch from Seiko</a> with better assembly quality than an Apple Watch Edition.</p>
  1427. <div>
  1428. <a  title="Permanent link to ‘Apple Extends Free Repairs of First-Generation Apple Watches With Detached Back Covers’"  href="">&nbsp;★&nbsp;</a>
  1429. </div>
  1431. ]]></content>
  1432.  </entry><entry>
  1433. <link rel="alternate" type="text/html" href="" />
  1434. <link rel="shorturl" href="" />
  1435. <link rel="related" type="text/html" href="" />
  1436. <id>,2017:/feeds/sponsors//11.33890</id>
  1437. <author><name>Daring Fireball Department of Commerce</name></author>
  1438. <published>2017-07-11T11:16:27-04:00</published>
  1439. <updated>2017-07-11T11:16:28-04:00</updated>
  1440. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1441. <p>Create a beautiful portfolio website with Squarespace. You can showcase your work to the world with stunning galleries and project pages. Try Squarespace for free. When you’re ready to subscribe, <a href="">get 10 percent off at</a> with offer code <strong>DARING17</strong>.</p>
  1443. <div>
  1444. <a  title="Permanent link to ‘Squarespace’"  href="">&nbsp;★&nbsp;</a>
  1445. </div>
  1447. ]]></content>
  1448. <title>[Sponsor] Squarespace</title></entry><entry>
  1449. <title>Max Boot: ‘Trump Has Picked America’s Enemies in Russia Over Its Friends in Europe’</title>
  1450. <link rel="alternate" type="text/html" href="" />
  1451. <link rel="shorturl" type="text/html" href="" />
  1452. <link rel="related" type="text/html" href="" />
  1453. <id>,2017:/linked//6.33889</id>
  1454. <published>2017-07-10T18:40:49Z</published>
  1455. <updated>2017-07-10T21:23:10Z</updated>
  1456. <author>
  1457. <name>John Gruber</name>
  1458. <uri></uri>
  1459. </author>
  1460. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1461. <p>Max Boot, writing for Foreign Policy:</p>
  1463. <blockquote>
  1464.  <p>His nutty behavior is bad enough at home; it’s even worse abroad when he is supposed to be representing not just his rabid base of “deplorables” but, rather, the whole country. That is something Trump simply does not know how to do.</p>
  1466. <p>Thus, in the course of this trip, he trashed his predecessor, the U.S. intelligence community, and the “fake news” media. Can you imagine Ronald Reagan in 1981 going abroad and attacking Jimmy Carter for not doing more to stand up to Soviet aggression? Or attacking the press for being hostile to him in the 1980 campaign (as they were) and the intelligence community for not predicting the Iranian revolution (as they did not)? It’s unimaginable, yet Trump somehow thinks that it’s appropriate.</p>
  1467. </blockquote>
  1469. <div>
  1470. <a  title="Permanent link to ‘Max Boot: ‘Trump Has Picked America’s Enemies in Russia Over Its Friends in Europe’’"  href="">&nbsp;★&nbsp;</a>
  1471. </div>
  1473. ]]></content>
  1474.  </entry><entry>
  1475. <title>FlightLogger</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>,2017:/linked//6.33888</id>
  1480. <published>2017-07-09T15:01:10Z</published>
  1481. <updated>2017-07-09T15:01:12Z</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>My thanks to FlightLogger for sponsoring this week&#8217;s DF RSS feed. FlightLogger lets you search for and save flights, get up-to-date notifications on any changes, share your travel coordinates with friends and family, and much more &#8212; all from one easy-to-use app.</p>
  1489. <p>Get real-time flight tracking for updates on departure and arrival times, delays, cancellations, gate and baggage claim information.</p>
  1491. <p>Available on all your devices: Add your flights on your iPhone and your flight information will be automatically synced to your iPad and Apple Watch all with an easy-to-use and clutter-free interface.</p>
  1493. <p><a href="">Get FlightLogger as a free download on the App Store</a> today.</p>
  1495. <div>
  1496. <a  title="Permanent link to ‘FlightLogger’"  href="">&nbsp;★&nbsp;</a>
  1497. </div>
  1499. ]]></content>
  1500.  </entry><entry>
  1502.    <link rel="alternate" type="text/html" href="" />
  1503. <link rel="shorturl" href="" />
  1504. <id>,2017://1.33887</id>
  1505. <published>2017-07-07T21:26:03Z</published>
  1506. <updated>2017-07-11T00:19:30Z</updated>
  1507. <author>
  1508. <name>John Gruber</name>
  1509. <uri></uri>
  1510. </author>
  1511. <summary type="text">In the same way it made sense for Honda and Toyota to create their Acura and Lexus divisions to sell higher-end cars without eroding the value or popularity of their best-selling Accords and Camrys, it makes sense for Apple to create a premium tier for the iPhone, the best-selling product the company has ever made and likely will ever make.</summary>
  1512. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1513. <p>I created <a href="">a bit of a stir</a> the other day when <a href="">I suggested the OLED iPhone &#8220;Pro&#8221; could start at $1,500</a>.</p>
  1515. <p>Let’s take a serious look at this. $1,500 as a starting price is probably way too high. But I think $1,200 is quite likely as the starting price, with the high-end model at $1,300 or $1,400.</p>
  1517. <p>First, consider the problems Apple faces with any new iPhone. Here are the prices for the iPhone 7:</p>
  1519. <ul>
  1520. <li>iPhone 7 32 GB: $649</li>
  1521. <li>iPhone 7 128 GB: $749</li>
  1522. <li>iPhone 7 256 GB: $849</li>
  1523. </ul>
  1525. <p>And 7 Plus:</p>
  1527. <ul>
  1528. <li>iPhone 7 Plus 32 GB: $769</li>
  1529. <li>iPhone 7 Plus 128 GB: $869</li>
  1530. <li>iPhone 7 Plus 256 GB: $969</li>
  1531. </ul>
  1533. <p>These prices have remained unchanged ever since the &#8220;Plus&#8221; era began with the iPhone 6 models in 2014. [<strong>Update:</strong> Several astute readers have reminded me that the 6 Plus and 6S Plus were $749/849/949 — the prices went up by $20 with the 7 Plus, presumably due to the cost of the dual camera module, but perhaps also as a small test of the iPhone’s price elasticity.] Apple reports its company-wide profit margin each quarter, which tends to hover around 37 or 38 percent. Apple does not report margins per-device or per-product-line, but considering that the iPhone accounts for around 70 percent of all Apple revenue, the margins for new iPhones almost certainly are somewhere between 35–40 percent. The exact number doesn’t really matter for the sake of this argument, so let’s just say that any new iPhone must have a profit margin of at least 35 percent for Apple to maintain its company-wide profit margin, and let’s further assume that maintaining company-wide margins in the high 30s is non-negotiable for the company.</p>
  1535. <p>Based on reactions to my post earlier this week, I think many people assume that the only thinking that goes into iPhone pricing is how much it costs for Apple to produce each iPhone. In other words, that the specs for the iPhone 7 were decided by how much Apple could put into them with $649/749/849 retail prices while achieving a profit margin of at least 35 percent. And that the specs for this year’s new iPhones have been set by the same logic.</p>
  1537. <p>But that’s too simplistic. You can’t talk about iPhone specs and pricing without considering scale. It’s not enough for Apple to create a phone that can be sold for $649/749/849 with 35 percent profit margins. They have to create a phone that can be sold at those prices, with those margins, <em>and which can be manufactured at scale</em>. And for Apple that scale is massive: anything less than 60–70 million in the quarter in which it goes on sale is a failure &#8212; possibly a catastrophic failure.</p>
  1539. <p>In short, new iPhones aren’t defined by what Apple can build for a certain price, but by what Apple can make for a certain price <em>at a certain incredibly high quantity</em>.</p>
  1541. <p>The iPhone’s scale — particularly the incredible popularity of the new high-end models each year — is Apple’s biggest financial strength but simultaneously its biggest potential strategic weakness. It prevents Apple from using <em>any</em> components in new iPhones that can’t be produced at a rate of 20-25 million per month, or roughly a rate of 1 million <em>per day</em>. The differences between regular and Plus models complicate this a little — only the Plus models need the dual camera systems, for example — but to date, even considering the Plus models, it has been true that all new iPhones need to be able to be produced in sufficient quantity to meet massive demand.</p>
  1543. <p>Based on the rumor mill this year — particularly <a href="">reports from KGI Securities analyst Ming-Chi Kuo</a> — it sounds like Apple is trying to expand the iPhone product line at the high end to get out of this trap. The best available iPhone should be, at least arguably, the best phone in the world. That might not be possible if all new iPhones must be capable of being manufactured in the same quantities as in recent years.</p>
  1545. <p>What Apple has traditionally done is make one new iPhone each year, priced at the same points as the previous year’s models. And the previous year’s models move down $100 each in the lineup, and the two-year-old models move down to the entry level. A lot of people seem to expect Apple to do the same this year, with the OLED minimal-bezel new iPhone starting out at the same or roughly the same prices as the iPhone 7 and 7 Plus. I think that’s why so many people are referring to this phone as the &#8220;iPhone 8&#8221;.</p>
  1547. <p>But that’s not what the rumors are saying at all. Ming-Chi Kuo’s overall record is a bit mixed, but his record on the iPhone (or perhaps better put, for Apple products assembled by Foxconn) is excellent. And <a href="">Kuo has been reporting all along</a> that Apple is creating <em>three</em> new phones for 2017:</p>
  1549. <ul>
  1550. <li>A new 4.7-inch phone with an LCD display, same or similar form factor as iPhone 7.</li>
  1551. <li>A new 5.5-inch phone with an LCD display, same or similar form factor as iPhone 7 Plus.</li>
  1552. <li>An all-new form factor with a tall, skinny OLED display and new edge-to-edge bezel-less display.</li>
  1553. </ul>
  1555. <p>In other words, marketing-wise, an iPhone 7S, iPhone 7S Plus, and an iPhone Deluxe. The iPhone 7S and 7S Plus sound like exactly what you’d expect from an S model year: same form factors as last year, with upgraded components and a new A-series system on a chip. There is no reason to expect these phones to cost less than today’s iPhone 7 and 7 Plus do. If Apple were going to sell the fancy new OLED iPhone Deluxe at the same prices as today’s iPhone 7 models, there would be no 7S or 7S Plus — they would just keep the existing 7 and 7 Plus and lower their prices by $100.</p>
  1557. <p>But that’s not what the rumors are saying.</p>
  1559. <p>Furthermore, Kuo has been saying all along that the fancy new OLED iPhone is going to be supply-constrained compared to previous new iPhone launches:</p>
  1561. <blockquote>
  1562.  <p>We predict October-November &amp; August-September as production ramp-up schedules of OLED iPhone &amp; LCD iPhone, respectively. &#8220;For optimized promotional effect, we think Apple may unveil the three models simultaneously in September, though the launch date of the OLED version may trail that of LCD models, and supply tightness may not improve before 1H18.&#8221; </p>
  1564. <p>We forecast shipments of the three new models in 2017F will be 80-85mn units, with an equal split between OLED &amp; LCD versions.</p>
  1565. </blockquote>
  1567. <p>Apple’s 2017 financial year ends September 30, so I’m assuming that “2017F” means the fourth quarter of the 2017 calendar year. But I don’t see how an even split between LCD and OLED iPhones makes sense if the OLED model’s “supply tightness may not improve before 1H18”. If supply is tight for six months or longer, how can half of Apple’s iPhone sales be for the OLED model?</p>
  1569. <p>It sounds to me like the OLED iPhone is a phone which Apple can’t make 40 million of per quarter, at least not today. And if that’s true, that means it should be more expensive. Not <em>should</em> in any moral sense, but simply because that’s how the principle of supply and demand works. When supply is constrained and demand is high, prices go higher. The higher prices alleviate demand.</p>
  1571. <p>Intriguingly, regarding device storage, Kuo also says:</p>
  1573. <blockquote>
  1574.  <p>Three new models will all come with 64GB and 256GB storage options</p>
  1575. </blockquote>
  1577. <p>Assuming that’s true and that Kuo means the phones will <em>only</em> come in 64 and 256 GB configurations, I can see two ways this plays out for the 7S and 7S Plus:</p>
  1579. <p>Scenario 1:</p>
  1581. <ul>
  1582. <li>32 GB 7, no-S: $549</li>
  1583. <li>64 GB 7S: $649</li>
  1584. <li>256 GB 7S: $749</li>
  1585. <li>32 GB 7 Plus, no-S: $669</li>
  1586. <li>64 GB 7S Plus: $769</li>
  1587. <li>256 GB 7S Plus: $869</li>
  1588. </ul>
  1590. <p>Scenario 2:</p>
  1592. <ul>
  1593. <li>32 GB 7, no-S: $649</li>
  1594. <li>64 GB 7S: $749</li>
  1595. <li>256 GB 7S: $849</li>
  1596. <li>32 GB 7 Plus, no-S: $769</li>
  1597. <li>64 GB 7S Plus: $869</li>
  1598. <li>256 GB 7S Plus: $969</li>
  1599. </ul>
  1601. <p>If it wasn’t for the fact that I’m basing this analysis on Ming-Chi Kuo’s reporting, I would expect 32/128/256 configurations of the 7S models, at the same prices as today’s 7 models. Apple was very slow to move beyond 16 GB base configurations; it seems odd to me that they’d be so quick to move beyond 32 GB base configurations. It also seems odd that Apple would move away from the successful good-better-best strategy of having three storage tiers. But that’s what Kuo is reporting.</p>
  1603. <p>So in my Scenario 2, where the 256 GB 7S and 7S Plus cost $849 and $969 respectively, the base model 64 GB OLED iPhone would have to cost at least $999, and I think more likely $1099, and the 256 GB model would cost at least $1099 or $1199.</p>
  1605. <p>But if Apple expects severe supply constraints on these iPhones, I think prices of $1199 (64 GB) and $1299 (256 GB) are more likely. I honestly don’t think something like $1249/1399 is out of the question.</p>
  1607. <p>The prices for these iPhones need to be high enough so that tens of millions of people still want to buy the iPhone 7S and 7S Plus. If the “iPhone Pro” or “iPhone Edition” or whatever it is that Apple is going to call this phone starts at $800 or even $900, who is going to buy an iPhone 7S or 7S Plus? Not enough people, that’s who. Apple needs tens of millions of people to buy the 7S and 7S Plus because they aren’t going to be able to produce the “Pro/Edition” model in sufficient quantity.</p>
  1609. <p>Think about it: if Apple thought they were going to be able to produce the iPhone Pro/Edition model in sufficient quantity (say, at least 50 or 60 million per quarter, starting this year) <em>and</em> could do so for a $700-800 starting price point, <em>and</em> maintain their desired profit margins, why would the 7S and 7S Plus even exist?</p>
  1611. <p>Conversely, if the iPhone Pro/Edition were something Apple suspected it could only manufacture at a quantity of, say, 10 million or so units per quarter (perhaps simply by maxing out the world’s OLED production capabilities), wouldn’t the rumor mill look exactly like it does today: with the Pro/Edition model looking like a new premium tier and the new 7S and 7S Plus models set to occupy the existing “regular” price points for new iPhones?</p>
  1613. <p>What many people want, obviously, is for the new OLED iPhone to simply be the “iPhone 8” and wow us with a new design at the same old prices. But what is Apple supposed to do if, say, Samsung can only produce 10 million OLED displays for Apple per quarter? Apple can’t magically produce whatever it wants in sufficient quantity at current prices.</p>
  1615. <p>Furthermore, why shouldn’t there be a deluxe “Pro” tier for phones? For many people, phones are every bit as much an essential professional tool as their laptops. For some people, even more so. And I’d bet my bottom dollar there are more people who consider their iPhone a “pro” tool (and are willing to pay “pro” prices) than who think so regarding their iPad, and we’ll have had iPad Pros for two years by the time new iPhones are announced in September. If there are iPad Pros and MacBook Pros, why not iPhone Pros?</p>
  1617. <p>If you want to argue that Apple should never create an iPhone with a higher starting price than what we have today, you’re implicitly arguing that Apple should never put any components into a new iPhone that can’t be made at iPhone 7 scale. I think that’s dangerous strategically, leaving Apple open to attack from competitors making premium phones with components (cameras, displays, new sensors, new battery technologies, etc.) that can only be produced in single-digit millions per quarter.</p>
  1619. <p>On the other hand, without question, this “new premium tier” strategy that I’m suggesting poses its own significant risk for Apple. The mere existence of the new edge-to-edge OLED iPhone could dampen excitement for the iPhone 7S and 7S Plus, leading to a decrease in overall sales. “<em>I don’t want a 7S because it’s boring, but I don’t want to spend $1,200 on an iPhone Pro/Edition because that’s too much for a phone, no matter how nice it is.</em>” That sentiment could be trouble for Apple.</p>
  1621. <p>Personally, I think this strategy makes sense, and arguably is overdue. In the same way it made sense for Honda and Toyota to create their Acura and Lexus divisions to sell higher-end cars without eroding the value or popularity of their best-selling Accords and Camrys, it makes sense for Apple to create a premium tier for the iPhone, the best-selling product the company has ever made and likely will ever make. But Apple won’t have the luxury (pardon the pun) of doing so under an Acura- or Lexus-like new brand. They’ll have to do it as Apple.</p>
  1625.    ]]></content>
  1626.  <title>★ Speculation Regarding the Pricing of and Strategy Behind This Year’s New iPhones</title></entry><entry>
  1627. <title>Justin Williams Got Hacked and All He Got Was This New SIM Card</title>
  1628. <link rel="alternate" type="text/html" href="" />
  1629. <link rel="shorturl" type="text/html" href="" />
  1630. <link rel="related" type="text/html" href="" />
  1631. <id>,2017:/linked//6.33886</id>
  1632. <published>2017-07-07T17:29:32Z</published>
  1633. <updated>2017-07-07T17:32:16Z</updated>
  1634. <author>
  1635. <name>John Gruber</name>
  1636. <uri></uri>
  1637. </author>
  1638. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1639. <p>Justin Williams:</p>
  1641. <blockquote>
  1642.  <p>I like to think I take an above average amount of steps to secure myself online: I use a password manager, unique passwords as complex as the site will allow, and turn on 2-factor authentication when possible. A true security expert will likely find some sort of flaw in my setup, but I&#8217;ll argue that I am doing more than 95% of the planet.</p>
  1644. <p>So how did I, someone who is reasonably secure, have his cell phone disabled, his PayPal account compromised, and a few hundred dollars withdrawn from his bank account?</p>
  1645. </blockquote>
  1647. <p>Two-factor authentication using your cell number is only as secure as your wireless carrier’s protection against social engineering — which, alas, might be terrible.</p>
  1649. <div>
  1650. <a  title="Permanent link to ‘Justin Williams Got Hacked and All He Got Was This New SIM Card’"  href="">&nbsp;★&nbsp;</a>
  1651. </div>
  1653. ]]></content>
  1654.  </entry><entry>
  1655. <title>Apple’s Bad Beta Decision on Em and En Dashes in iOS 11</title>
  1656. <link rel="alternate" type="text/html" href="" />
  1657. <link rel="shorturl" type="text/html" href="" />
  1658. <link rel="related" type="text/html" href="" />
  1659. <id>,2017:/linked//6.33885</id>
  1660. <published>2017-07-07T16:29:10Z</published>
  1661. <updated>2017-07-07T20:44:17Z</updated>
  1662. <author>
  1663. <name>John Gruber</name>
  1664. <uri></uri>
  1665. </author>
  1666. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1667. <p>Glenn Fleishman:</p>
  1669. <blockquote>
  1670.  <p>Terrible news. Apple is replacing the long-running convention of typing two hyphens to obtain an em dash or “long dash.” That is, if you type “<code>--</code>”, many places in the interface in which autocorrection is enabled or third-party software takes advantage of autocorrection, it’s turned into —. [&#8230;]</p>
  1672. <p>Why is this terrible news? Some have argued with me on Twitter that it’s more logical: “<code>-</code>” for hyphen, “<code>--</code>” for the longer en dash, and “<code>---</code>” for the longest em dash. You type more hyphens to get a longer dash.</p>
  1674. <p>My rejoinder is twofold. First, most people rarely use an en dash, although I’d like to increase that number. Second, a billion people have learned that typing “<code>--</code>” leads to a long dash. I may be exaggerating the number, but given that Microsoft Word, Pages, and other desktop software performs this substitution silently, it’s a widespread convention being overturned.</p>
  1675. </blockquote>
  1677. <p>I really hope this gets changed before iOS 11 ships.</p>
  1679. <p>Also, I’m not sure why dash conversion is part of “smart punctuation”. Converting simple hyphens to en- and em-dashes could be handled by iOS’s text substitutions. By default, for example, iOS has long had a substitution to change “(c)” to “©”. If en- and em-dashes were handled there, everyone could be happy because they could change it.</p>
  1681. <p>The only punctuation marks that needs to be “smart” are quotes. Right now in the iOS 11 betas, “smart” punctuation is all-or-nothing — to get smart quotes you have to accept smart dashes too.</p>
  1683. <div>
  1684. <a  title="Permanent link to ‘Apple’s Bad Beta Decision on Em and En Dashes in iOS 11’"  href="">&nbsp;★&nbsp;</a>
  1685. </div>
  1687. ]]></content>
  1688.  </entry><entry>
  1689. <title>Jon Bois: ‘What Football Will Look Like in the Future’</title>
  1690. <link rel="alternate" type="text/html" href="" />
  1691. <link rel="shorturl" type="text/html" href="" />
  1692. <link rel="related" type="text/html" href="" />
  1693. <id>,2017:/linked//6.33884</id>
  1694. <published>2017-07-06T22:36:27Z</published>
  1695. <updated>2017-07-06T22:38:20Z</updated>
  1696. <author>
  1697. <name>John Gruber</name>
  1698. <uri></uri>
  1699. </author>
  1700. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1701. <p>I implore you to drop everything and read this now, regardless if you care about or even understand the rules of the game.</p>
  1703. <p>Trust me.</p>
  1705. <div>
  1706. <a  title="Permanent link to ‘Jon Bois: &#8216;What Football Will Look Like in the Future&#8217;’"  href="">&nbsp;★&nbsp;</a>
  1707. </div>
  1709. ]]></content>
  1710.  </entry><entry>
  1711. <title>Speaking of $1,200–1,600 Phones</title>
  1712. <link rel="alternate" type="text/html" href="" />
  1713. <link rel="shorturl" type="text/html" href="" />
  1714. <link rel="related" type="text/html" href="" />
  1715. <id>,2017:/linked//6.33883</id>
  1716. <published>2017-07-06T17:55:45Z</published>
  1717. <updated>2017-07-06T18:01:25Z</updated>
  1718. <author>
  1719. <name>John Gruber</name>
  1720. <uri></uri>
  1721. </author>
  1722. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1723. <p>Red has announced (and is accepting pre-orders for) a 2018 high-end Android phone with a &#8220;holographic display&#8221;. $1,200 for aluminum, $1,600 for titanium. (<a href="">Via The Verge</a>.)</p>
  1725. <div>
  1726. <a  title="Permanent link to ‘Speaking of $1,200–1,600 Phones’"  href="">&nbsp;★&nbsp;</a>
  1727. </div>
  1729. ]]></content>
  1730.  </entry><entry>
  1731. <link rel="alternate" type="text/html" href="" />
  1732. <link rel="shorturl" href="" />
  1733. <link rel="related" type="text/html" href="" />
  1734. <id>,2017:/feeds/sponsors//11.33878</id>
  1735. <author><name>Daring Fireball Department of Commerce</name></author>
  1736. <published>2017-07-03T21:26:45-04:00</published>
  1737. <updated>2017-07-03T21:26:46-04:00</updated>
  1738. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1739. <p>Traveling has never been this easy. Now, you can search and save your flights, get up-to-date notifications on any changes, share your travel coordinates with friends and family, and much more &#8212; all from one easy-to-use app.</p>
  1741. <p>Get real-time flight tracking for updates on departure and arrival times, delays, cancellations, gate and baggage claim information.</p>
  1743. <p>Available on all your devices: Add your flights on your iPhone and your flight information will be automatically synced to your iPad and Apple Watch all with an easy-to-use and clutter-free interface.</p>
  1745. <p><a href="">Get FlightLogger as a free download on the App Store</a> today.</p>
  1747. <div>
  1748. <a  title="Permanent link to ‘FlightLogger’"  href="">&nbsp;★&nbsp;</a>
  1749. </div>
  1751. ]]></content>
  1752. <title>[Sponsor] FlightLogger</title></entry><entry>
  1754.    <link rel="alternate" type="text/html" href="" />
  1755. <link rel="shorturl" href="" />
  1756. <id>,2017://1.33868</id>
  1757. <published>2017-06-29T22:00:00Z</published>
  1758. <updated>2017-06-30T00:57:27Z</updated>
  1759. <author>
  1760. <name>John Gruber</name>
  1761. <uri></uri>
  1762. </author>
  1763. <summary type="text">Apple had amazing product introductions before the iPhone, and it’s had a few good ones after. But the iPhone was the only product introduction that felt *impossible*.</summary>
  1764. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1765. <p>In January 2007, 26 minutes into his Macworld Expo keynote address, <a href="">Steve Jobs introduced the iPhone</a> with his justly-famous &#8220;three revolutionary products&#8221; framing:</p>
  1767. <blockquote>
  1768.  <p>This is a day I’ve been looking forward to for
  1769. two-and-a-half years.</p>
  1771. <p>Every once in a while, a revolutionary product comes along that
  1772. changes everything. … One’s very fortunate if you get to work on
  1773. just one of these in your career.</p>
  1775. <p>Apple’s been very fortunate. It’s been able to introduce a few of
  1776. these into the world. In 1984, we introduced the Macintosh. It
  1777. didn’t just change Apple, it changed the whole computer industry.
  1778. In 2001, we introduced the first iPod, and it didn’t just change
  1779. the way we all listen to music, it changed the entire music
  1780. industry.</p>
  1782. <p>Well, today, we’re introducing three revolutionary products of
  1783. this class.</p>
  1785. <p>The first one is a widescreen iPod with touch controls.</p>
  1787. <p>The second is a revolutionary mobile phone.</p>
  1789. <p>And the third is a breakthrough Internet communications device.</p>
  1791. <p>So, three things: a widescreen iPod with touch controls; a
  1792. revolutionary mobile phone; and a breakthrough Internet
  1793. communications device. An iPod, a phone, and an Internet
  1794. communicator. An iPod, a phone … are you getting it?</p>
  1796. <p>These are not three separate devices, this is one device, and we
  1797. are calling it iPhone.</p>
  1798. </blockquote>
  1800. <p>Ten years ago today, the iPhone went on sale.</p>
  1802. <p>I almost never watch an Apple keynote event after it has faded from being new. But I&#8217;ve watched the iPhone introduction at least half a dozen times over the years. I still get excited. The words Jobs used, as quoted above, are perfect. But you really have to watch it, to listen to his voice, to feel his conviction. He knew then what we all know now: this was <em>it</em>. This was the keynote we had all been waiting for. This was the reason why people lined up overnight for Apple keynotes &#8212; in the hopes of an announcement like this one. The iPhone was <em>the</em> product Apple had been founded to create &#8212; the epitome of everything both of Apple&#8217;s founding Steves stood for and obsessed about. The home run of all home runs.</p>
  1804. <p>With hindsight, though, I think even Jobs himself underestimated what the iPhone was.</p>
  1806. <p>The Apple I, the Apple II, the Macintosh, the iPod &#8212; yes, these were all industry-changing products. The iPhone never would have happened without each of them. But the iPhone wasn&#8217;t merely industry-changing. It wasn&#8217;t merely multi-industry-changing. It wasn&#8217;t merely <em>many</em>-industry-changing.</p>
  1808. <p>The iPhone changed the world.</p>
  1810. <p>There is no way to overstate it. The iPhone was the inflection point where &#8220;personal computing&#8221; truly became personal. Apple had amazing product introductions before the iPhone, and it&#8217;s had a few good ones after. But the iPhone was the only product introduction I&#8217;ve ever experienced that felt <em>impossible</em>. Apple couldn&#8217;t have shrunk Mac OS X &#8212; a Unix-based workstation OS, <em>including</em> the Cocoa frameworks &#8212; to a point where it could run on a cell phone. Scrolling couldn&#8217;t be that smooth and fluid. A touchscreen — especially one in a phone — couldn&#8217;t be so responsive. Apple couldn&#8217;t possibly have gotten a major carrier to cede them control over every aspect of the device, both hardware and software. I can recall sitting in the hall at Moscone West, watching the keynote unfold, 90 percent excited as hell, 10 percent concerned that I was losing my goddamn mind. <em>Literally mind-blowing.</em></p>
  1812. <p>For nearly six interminable months we waited. And then even once I had my own iPhone in my hands on the evening of Friday, 29 June 2007, I kept thinking, <em>I can&#8217;t believe this.</em></p>
  1814. <p>The iPhone&#8217;s potential was obviously deep, but it was so deep as to be unfathomable at the time. The original iPhone didn&#8217;t even shoot video; today the iPhone and iPhone-like Android phones have largely killed the point-and-shoot camera industry. It has obviated portable music players, audio recorders, paper maps, GPS devices, flashlights, walkie-talkies, music radio (with streaming music), talk radio (with podcasts), and more. Ride-sharing services like Uber and Lyft wouldn&#8217;t even make sense pre-iPhone. Social media is mobile-first, and in some cases mobile-only. More people read Daring Fireball on iPhones than on desktop computers.</p>
  1816. <p>In just a handful of years, Nokia and BlackBerry, both seemingly impregnable in 2006, were utterly obliterated. <a href="">The makers of ever-more-computer-like gadgets were simply unable to compete with ever-more-gadget-like computers</a>.</p>
  1818. <p>Ten years in and the full potential of the iPhone <em>still</em> <a href="">hasn&#8217;t been fully tapped</a>. No product in the computing age compares to the iPhone in terms of societal or financial impact. Few products in the history of the world compare. We may never see anything like it again &#8212; from Apple or from anyone else.</p>
  1822.    ]]></content>
  1823.  <title>★ Perfect Ten</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