[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>
  9. <updated>2017-01-21T23:02:00Z</updated><rights>Copyright © 2017, John Gruber</rights><entry>
  10. <title>V for Wikipedia</title>
  11. <link rel="alternate" type="text/html" href=";ct=df&amp;mt=8" />
  12. <link rel="shorturl" type="text/html" href="" />
  13. <link rel="related" type="text/html" href="" />
  14. <id>,2017:/linked//6.33326</id>
  15. <published>2017-01-21T23:01:30Z</published>
  16. <updated>2017-01-21T23:02:00Z</updated>
  17. <author>
  18. <name>John Gruber</name>
  19. <uri></uri>
  20. </author>
  21. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  22. <p>My thanks to Raureif for sponsoring this week&#8217;s DF RSS feed to promote V for Wikipedia. V for Wikipedia is an opinionated iOS app with nit-picky typography hailed by no less than Erik Spiekermann as the “best on the small screen yet.” It is a gorgeous app, and it&#8217;s amazing to me personally how much better Wikipedia reads when it actually looks good.</p>
  24. <p>V for Wikipedia&#8217;s design is more than just typography, though. The map visualization lets you explore nearby places &#8212; interesting both for your own neighborhood and anywhere you might travel. You can even find articles on your Apple Watch (which sounds crazy, but works great).</p>
  26. <p><a href=";ct=df&amp;mt=8">Download V for Wikipedia on the App Store</a>. It&#8217;s a great app, well worth a couple of bucks.</p>
  28. <div>
  29. <a  title="Permanent link to ‘V for Wikipedia’"  href="">&nbsp;★&nbsp;</a>
  30. </div>
  32. ]]></content>
  33.  </entry><entry>
  34. <title>‘American Carnage’</title>
  35. <link rel="alternate" type="text/html" href="" />
  36. <link rel="shorturl" type="text/html" href="" />
  37. <link rel="related" type="text/html" href="" />
  38. <id>,2017:/linked//6.33325</id>
  39. <published>2017-01-21T02:03:53Z</published>
  40. <updated>2017-01-21T02:27:11Z</updated>
  41. <author>
  42. <name>John Gruber</name>
  43. <uri></uri>
  44. </author>
  45. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  46. <p>The Economist:</p>
  48. <blockquote>
  49.  <p>But there was nothing for those hoping to see a more pragmatic,
  50. moderate President Trump take office, or to hear him admit that
  51. the world is complex and less pliable than he pretended on the
  52. campaign trail. All populists are at heart conspiracy theorists,
  53. who pretend that easy solutions exist to society’s woes and have
  54. only not been tried to date because elites are wicked and deaf to
  55. the sturdy common-sense of decent, ordinary folk.</p>
  57. <p>That was the Trump approach.</p>
  58. </blockquote>
  60. <p>That&#8217;s Trumpism in a nut.</p>
  62. <div>
  63. <a  title="Permanent link to ‘&#8216;American Carnage&#8217;’"  href="">&nbsp;★&nbsp;</a>
  64. </div>
  66. ]]></content>
  67.  </entry><entry>
  68. <title>On the Inauguration of Donald Trump: Preserve, Protect, and Defend</title>
  69. <link rel="alternate" type="text/html" href="" />
  70. <link rel="shorturl" type="text/html" href="" />
  71. <link rel="related" type="text/html" href="" />
  72. <id>,2017:/linked//6.33324</id>
  73. <published>2017-01-21T01:26:07Z</published>
  74. <updated>2017-01-21T01:46:11Z</updated>
  75. <author>
  76. <name>John Gruber</name>
  77. <uri></uri>
  78. </author>
  79. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  80. <p>David Remnick, writing for The New Yorker:</p>
  82. <blockquote>
  83.  <p>The reason so many people are having fever dreams and waking up
  84. with a knot in the gut is not that they are political crybabies,
  85. not that a Republican defeated a Democrat. It’s not that an
  86. undifferentiated mass of “coastal élites” is incapable of
  87. recognizing that globalization, automation, and
  88. deindustrialization have left millions of people in reduced and
  89. uncertain circumstances. It is not that they “don’t get it.” It’s
  90. that they do.</p>
  92. <p>Since Election Day, Trump has managed to squander good faith and
  93. guarded hope with flagrant displays of self-indulgent tweeting,
  94. chaotic administration, willful ignorance, and ethical sludge.
  95. Setting the tone for his Presidency, he refused, or was unable, to
  96. transcend the willful ugliness of his campaign. He goes on
  97. continuing to conceal his taxes, the summary of his professional
  98. life; he refuses to isolate himself from his businesses in a way
  99. that satisfies any known ethical standard; he rants on social
  100. media about every seeming offense that catches his eye; he sets
  101. off gratuitous diplomatic brushfires everywhere from Beijing to
  102. Berlin. (Everywhere, that is, except Moscow.)</p>
  103. </blockquote>
  105. <p>Whatever he did to become popular enough to win the election, he&#8217;s squandered that too &#8212; <a href="">even Fox News&#8217;s poll</a> shows him to be staggeringly unpopular. The stands were nearly empty for today&#8217;s parade. <a href="">Look at this</a>. <a href="">No one showed up</a>. <a href="">Crickets chirping</a>.</p>
  107. <p>It&#8217;s going to be a long four years, but take comfort in this: Trump is already deeply unpopular.</p>
  109. <div>
  110. <a  title="Permanent link to ‘On the Inauguration of Donald Trump: Preserve, Protect, and Defend’"  href="">&nbsp;★&nbsp;</a>
  111. </div>
  113. ]]></content>
  114.  </entry><entry>
  115. <title>Paul Ryan: The Magazine</title>
  116. <link rel="alternate" type="text/html" href="" />
  117. <link rel="shorturl" type="text/html" href="" />
  118. <link rel="related" type="text/html" href="" />
  119. <id>,2017:/linked//6.33323</id>
  120. <published>2017-01-20T22:51:57Z</published>
  121. <updated>2017-01-20T23:07:05Z</updated>
  122. <author>
  123. <name>John Gruber</name>
  124. <uri></uri>
  125. </author>
  126. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  127. <p>Remember <a href="">The Neu Jorker</a> &#8212; Andrew Lipstein and James Folta&#8217;s cover-to-cover parody issue of The New Yorker? They&#8217;re back, with a Kickstarter to raise money for a new project: &#8220;Paul Ryan: The Unofficial Magazine of Paul Ryan&#8221;.</p>
  129. <p>I&#8217;m in.</p>
  131. <div>
  132. <a  title="Permanent link to ‘Paul Ryan: The Magazine’"  href="">&nbsp;★&nbsp;</a>
  133. </div>
  135. ]]></content>
  136.  </entry><entry>
  137. <title>John McTiernan’s First Film in 14 Years: ‘The Red Dot’, a Short Promoting ‘Tom Clancy’s Ghost Recon: Wildlands’</title>
  138. <link rel="alternate" type="text/html" href="" />
  139. <link rel="shorturl" type="text/html" href="" />
  140. <link rel="related" type="text/html" href="" />
  141. <id>,2017:/linked//6.33322</id>
  142. <published>2017-01-20T22:24:09Z</published>
  143. <updated>2017-01-20T22:24:10Z</updated>
  144. <author>
  145. <name>John Gruber</name>
  146. <uri></uri>
  147. </author>
  148. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  149. <p><a href="">Watch the short first</a>. It&#8217;s terrific. (Warning: violence.) Then follow the link and read Drew Taylor&#8217;s piece for Vulture:</p>
  151. <blockquote>
  152.  <p>McTiernan&#8217;s involvement in <em>The Red Dot</em> hasn&#8217;t been widely
  153. publicized (or even particularly acknowledged), which is a shame,
  154. especially considering it&#8217;s his first filmed project in a whopping
  155. 14 years. (His last movie was the rainy <em>Rashomon</em>-on-a-military
  156. base thriller <em>Basic</em>.) McTiernan&#8217;s inauspicious reemergence leads
  157. to a couple of bigger questions: Where, exactly, has he been? And
  158. what makes this ad so special?</p>
  160. <p>To answer the first question, you have to go back to 2006, when
  161. Anthony Pellicano, a private eye with ties to some of the most
  162. powerful people in Hollywood, was <a href="">arraigned on federal
  163. wiretapping charges</a>. It was the conclusion of both a
  164. three-year investigation and Pellicano&#8217;s 30-day stint in prison
  165. for illegally keeping explosives in his West Hollywood office. The
  166. resulting trial would <a href="">eventually embroil</a> some of Hollywood&#8217;s
  167. biggest executives (Michael Ovitz and Brad Grey) and shiniest
  168. stars (Tom Cruise and Chris Rock). At the time, Vanity Fair
  169. described the scandal as <a href="">Hollywood&#8217;s Watergate</a>.</p>
  171. <p>But only one member of the Hollywood elite would actually get sent
  172. to prison for to his relationship with the notoriously scuzzy
  173. Pellicano: John McTiernan.</p>
  174. </blockquote>
  176. <p>This is an amazing story, and despite being a huge fan of <a href="">McTiernan&#8217;s work</a>, I had no idea about any of it until today.</p>
  178. <p>Good to have McTiernan back.</p>
  180. <div>
  181. <a  title="Permanent link to ‘John McTiernan&#8217;s First Film in 14 Years: &#8216;The Red Dot&#8217;, a Short Promoting &#8216;Tom Clancy&#8217;s Ghost Recon: Wildlands&#8217;’"  href="">&nbsp;★&nbsp;</a>
  182. </div>
  184. ]]></content>
  185.  </entry><entry>
  186. <title>Walt Mossberg: ‘Lousy Ads Are Ruining the Online Experience’</title>
  187. <link rel="alternate" type="text/html" href="" />
  188. <link rel="shorturl" type="text/html" href="" />
  189. <link rel="related" type="text/html" href="" />
  190. <id>,2017:/linked//6.33321</id>
  191. <published>2017-01-20T21:41:49Z</published>
  192. <updated>2017-01-20T22:30:37Z</updated>
  193. <author>
  194. <name>John Gruber</name>
  195. <uri></uri>
  196. </author>
  197. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  198. <p>Walt Mossberg:</p>
  200. <blockquote>
  201.  <p>Last Saturday, as the New England Patriots were sloppily beating
  202. the Houston Texans 34–16 in a playoff game, I wanted to look at
  203. the highlight video of a play using the NFL app on my iPad. To
  204. watch that 14-second clip, I had to suffer through a 30-second
  205. ad for something so irrelevant to me that I can’t even recall
  206. what it was.</p>
  207. </blockquote>
  209. <p>A preroll ad twice as along as the actual video clip is absurd.</p>
  211. <p>Here&#8217;s Mossberg, on his experience after launching Recode:</p>
  213. <blockquote>
  214.  <p>About a week after our launch, I was seated at a dinner next to a
  215. major advertising executive. He complimented me on our new site’s
  216. quality and on that of a predecessor site we had created and run,
  217. I asked him if that meant he’d be placing ads on
  218. our fledgling site. He said yes, he’d do that for a little while.
  219. And then, after the cookies he placed on Recode helped him to
  220. track our desirable audience around the web, his agency would
  221. begin removing the ads and placing them on cheaper sites our
  222. readers also happened to visit. In other words, our quality
  223. journalism was, to him, nothing more than a lead generator for
  224. target-rich readers, and would ultimately benefit sites that might
  225. care less about quality.</p>
  226. </blockquote>
  228. <p>So backwards, so shortsighted. User tracking is a plague that benefits no one.</p>
  230. <div>
  231. <a  title="Permanent link to ‘Walt Mossberg: &#8216;Lousy Ads Are Ruining the Online Experience&#8217;’"  href="">&nbsp;★&nbsp;</a>
  232. </div>
  234. ]]></content>
  235.  </entry><entry>
  236. <title>Apple Sues Qualcomm for $1 Billion</title>
  237. <link rel="alternate" type="text/html" href="" />
  238. <link rel="shorturl" type="text/html" href="" />
  239. <link rel="related" type="text/html" href="" />
  240. <id>,2017:/linked//6.33320</id>
  241. <published>2017-01-20T21:23:58Z</published>
  242. <updated>2017-01-20T21:23:59Z</updated>
  243. <author>
  244. <name>John Gruber</name>
  245. <uri></uri>
  246. </author>
  247. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  248. <p>Anita Balakrishnan, reporting for CNBC:</p>
  250. <blockquote>
  251.  <p>Apple is suing Qualcomm for roughly $1 billion, saying Qualcomm
  252. has been &#8220;charging royalties for technologies they have nothing to
  253. do with.&#8221; The suit follows the U.S. Federal Trade Commission&#8217;s
  254. lawsuit against Qualcomm earlier this week over unfair patent
  255. licensing practices.</p>
  257. <p>Shares of Qualcomm, which had been up 1 percent earlier in the
  258. day, were were down nearly 2.5 percent by the closing bell.</p>
  260. <p>Apple says that Qualcomm has taken &#8220;radical steps,&#8221; including
  261. &#8220;withholding nearly $1 billion in payments from Apple as
  262. retaliation for responding truthfully to law enforcement agencies
  263. investigating them.&#8221;</p>
  265. <p>Apple added, &#8220;Despite being just one of over a dozen companies who
  266. contributed to basic cellular standards, Qualcomm insists on
  267. charging Apple at least five times more in payments than all the
  268. other cellular patent licensors we have agreements with combined.&#8221;</p>
  269. </blockquote>
  271. <p>That answers <a href="">my question the other day</a> about who initiated the complaint against Qualcomm with the FTC.</p>
  273. <div>
  274. <a  title="Permanent link to ‘Apple Sues Qualcomm for $1 Billion’"  href="">&nbsp;★&nbsp;</a>
  275. </div>
  277. ]]></content>
  278.  </entry><entry>
  280.    <link rel="alternate" type="text/html" href="" />
  281. <link rel="shorturl" href="" />
  282. <id>,2017://1.33319</id>
  283. <published>2017-01-20T20:34:50Z</published>
  284. <updated>2017-01-21T02:11:51Z</updated>
  285. <author>
  286. <name>John Gruber</name>
  287. <uri></uri>
  288. </author>
  289. <summary type="html"><![CDATA[<p>Why I consider Tesla one of Apple&#8217;s handful of serious rivals, even though they don&#8217;t yet (and perhaps never will) compete with Apple directly.</p>
  290. ]]></summary>
  291. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  292. <p><a href="">Chris Matyszczyk, writing for CNet</a>:</p>
  294. <blockquote>
  295.  <p>Research consultancy Brand Keys has just released its <a href="">2017
  296. Customer Loyalty Engagement Index</a>. This seeks to find the
  297. &#8220;category drivers that engage customers, engender loyalty and
  298. drive real profits.&#8221; It&#8217;s based on the views and emotions of
  299. 49,168 consumers aged between 16 and 65.</p>
  301. <p>And when he looks at <a href="">the results</a>, I fear we may see Tim Cook
  302. dancing on the tables at some local Cupertino hostelry.</p>
  304. <p>When it comes to the smartphone category, the top driver is Apple.
  305. In tablets, it&#8217;s Apple. In laptop computers, it&#8217;s Apple. Yes, this
  306. despite the launch of the somewhat deflating MacBook Pro.</p>
  308. <p>What about online music? Goodness me, it isn&#8217;t Spotify. It&#8217;s
  309. Apple Music.</p>
  311. <p>Even in the headphones product category, Apple-owned Beats ties
  312. with LG as the category driver.</p>
  313. </blockquote>
  315. <p>Take these results with a grain of salt, considering that Brand Keys is the same outfit that published a piece titled &#8220;<a href="">Apple iPhone 7 Sucks (When It Comes Building Loyalty)</a>&#8221; on September 19.</p>
  317. <p>But with the possible exception of music, isn&#8217;t it inarguable that Apple leads in all these categories? Who else even <em>could</em> be named the customer loyalty or brand leader in tablets or laptops? No one. You can make the case for Samsung in phones, but I think most observers would agree that they&#8217;ve always been Pepsi to the iPhone&#8217;s Coke, and their position is shakier than ever in the wake of the Note 7 fiasco.</p>
  319. <p>I think one reason there&#8217;s so much consternation today about the state of Apple is simply the fear that their clear leadership in these categories could or already has led to complacency. I wrote nine years ago <a href="">that it would be better for Apple if they had <em>more</em> competition</a> from design- and innovation-focused competitors, and I think that remains true today. That&#8217;s why I consider Tesla one of Apple&#8217;s handful of serious rivals, even though they don&#8217;t yet (and perhaps never will) compete with Apple directly, other than through the <a href="">recruiting</a> of <a href="">talent</a>.</p>
  323.    ]]></content>
  324.  <title>★ Apple’s Continuing Need for Worthy Rivals</title></entry><entry>
  325. <title>Chris Lattner on ATP</title>
  326. <link rel="alternate" type="text/html" href="" />
  327. <link rel="shorturl" type="text/html" href="" />
  328. <link rel="related" type="text/html" href="" />
  329. <id>,2017:/linked//6.33318</id>
  330. <published>2017-01-20T19:16:31Z</published>
  331. <updated>2017-01-20T19:16:32Z</updated>
  332. <author>
  333. <name>John Gruber</name>
  334. <uri></uri>
  335. </author>
  336. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  337. <p>Now out of Apple and soon to be leading Tesla&#8217;s autopilot team, Chris Lattner was the guest on ATP this week. Outstanding interview.</p>
  339. <div>
  340. <a  title="Permanent link to ‘Chris Lattner on ATP’"  href="">&nbsp;★&nbsp;</a>
  341. </div>
  343. ]]></content>
  344.  </entry><entry>
  345. <title>Hunter S. Thompson’s Obituary for Richard Nixon</title>
  346. <link rel="alternate" type="text/html" href="" />
  347. <link rel="shorturl" type="text/html" href="" />
  348. <link rel="related" type="text/html" href="" />
  349. <id>,2017:/linked//6.33317</id>
  350. <published>2017-01-20T19:12:32Z</published>
  351. <updated>2017-01-20T19:12:34Z</updated>
  352. <author>
  353. <name>John Gruber</name>
  354. <uri></uri>
  355. </author>
  356. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  357. <p>Feels appropriate today:</p>
  359. <blockquote>
  360.  <p>Some people will say that words like <em>scum</em> and <em>rotten</em> are wrong
  361. for Objective Journalism &#8212; which is true, but they miss the
  362. point. It was the built-in blind spots of the Objective rules and
  363. dogma that allowed Nixon to slither into the White House in the
  364. first place. He looked so good on paper that you could almost vote
  365. for him sight unseen. He seemed so all-American, so much like
  366. Horatio Alger, that he was able to slip through the cracks of
  367. Objective Journalism. You had to get Subjective to see Nixon
  368. clearly, and the shock of recognition was often painful.</p>
  369. </blockquote>
  371. <div>
  372. <a  title="Permanent link to ‘Hunter S. Thompson&#8217;s Obituary for Richard Nixon’"  href="">&nbsp;★&nbsp;</a>
  373. </div>
  375. ]]></content>
  376.  </entry><entry>
  377. <title>The Team That Runs Mark Zuckerberg’s Facebook Page</title>
  378. <link rel="alternate" type="text/html" href="" />
  379. <link rel="shorturl" type="text/html" href="" />
  380. <link rel="related" type="text/html" href="" />
  381. <id>,2017:/linked//6.33316</id>
  382. <published>2017-01-19T21:59:59Z</published>
  383. <updated>2017-01-19T22:00:01Z</updated>
  384. <author>
  385. <name>John Gruber</name>
  386. <uri></uri>
  387. </author>
  388. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  389. <p>Sarah Frier, reporting for Bloomberg on the team of writers and photographers that runs Mark Zuckerberg&#8217;s personal Facebook page:</p>
  391. <blockquote>
  392.  <p>Zuckerberg has help, lots of it. Typically, a handful of Facebook
  393. employees manage communications just for him, helping write his
  394. posts and speeches, while an additional dozen or so delete
  395. harassing comments and spam on his page, say two people familiar
  396. with the matter. Facebook also has professional photographers snap
  397. Zuckerberg, say, taking a run in Beijing or reading to his
  398. daughter. Among them is Charles Ommanney, known most recently for
  399. his work <a href="">covering the refugee crisis</a> for the Washington Post.
  400. Company spokeswoman Vanessa Chan says Facebook is an easy way for
  401. executives to connect with various audiences.</p>
  403. <p>While plenty of chief executive officers have image managers, the
  404. scale of this team is something different. So is its conflation of
  405. Zuckerberg’s personal image with that of his company, the
  406. diaper-changing photos next to the user growth stats.</p>
  407. </blockquote>
  409. <p><a href="">Matt Yglesias</a>:</p>
  411. <blockquote>
  412.  <p>Key point here is that Mark Zuckerberg is much too smart to
  413. actually spend time on Facebook.</p>
  414. </blockquote>
  416. <div>
  417. <a  title="Permanent link to ‘The Team That Runs Mark Zuckerberg’s Facebook Page’"  href="">&nbsp;★&nbsp;</a>
  418. </div>
  420. ]]></content>
  421.  </entry><entry>
  422. <title>The Information: ‘Google to Expand Mid-Range “Android One” Program Into U.S.’</title>
  423. <link rel="alternate" type="text/html" href="" />
  424. <link rel="shorturl" type="text/html" href="" />
  425. <link rel="related" type="text/html" href="" />
  426. <id>,2017:/linked//6.33315</id>
  427. <published>2017-01-19T02:05:19Z</published>
  428. <updated>2017-01-19T02:05:20Z</updated>
  429. <author>
  430. <name>John Gruber</name>
  431. <uri></uri>
  432. </author>
  433. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  434. <p>Amir Efrati, reporting for The Information (behind a paywall, alas &#8212; <a href="">here&#8217;s The Verge&#8217;s regurgitated version</a> if you don&#8217;t have a subscription)</p>
  436. <blockquote>
  437.  <p>For instance, Google recently expressed its displeasure with
  438. Huawei after the China-based smartphone giant said earlier this
  439. month it would offer Amazon’s Alexa “virtual assistant” on
  440. upcoming U.S. phones, according to a person briefed about the
  441. matter. (Google developed a rival virtual assistant that will be
  442. built into Android phones besides the Pixel later this year.) It’s
  443. likely that Huawei made the decision in order to be in Amazon’s
  444. good graces, given that Amazon is an important seller of Huawei
  445. phones to U.S. customers.</p>
  446. </blockquote>
  448. <p>I think it&#8217;s more likely that Huawei went with Alexa instead of Google Assistant because Alexa is, you know, actually available to them, right now. Maybe Google shouldn&#8217;t be surprised that Android handset makers are looking to Amazon when Google keeps the best new features exclusive to its own Pixel phones. But what do I know?</p>
  450. <blockquote>
  451.  <p>Google already has lined up at least one phone maker to be a U.S.
  452. launch partner for Android One, said one of the people briefed on
  453. the program. The identity couldn’t be learned.</p>
  454. </blockquote>
  456. <p>You have to love the passive voice. It&#8217;s not that Efrati couldn&#8217;t learn the identity &#8212; the identity couldn&#8217;t be learned. It&#8217;s unknowable!</p>
  458. <div>
  459. <a  title="Permanent link to ‘The Information: &#8216;Google to Expand Mid-Range &#8220;Android One&#8221; Program Into U.S.&#8217;’"  href="">&nbsp;★&nbsp;</a>
  460. </div>
  462. ]]></content>
  463.  </entry><entry>
  464. <title>Developing an App Facing an Inevitable Sherlocking</title>
  465. <link rel="alternate" type="text/html" href="" />
  466. <link rel="shorturl" type="text/html" href="" />
  467. <link rel="related" type="text/html" href="" />
  468. <id>,2017:/linked//6.33314</id>
  469. <published>2017-01-18T23:43:19Z</published>
  470. <updated>2017-01-19T19:46:47Z</updated>
  471. <author>
  472. <name>John Gruber</name>
  473. <uri></uri>
  474. </author>
  475. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  476. <p>David Smith:</p>
  478. <blockquote>
  479.  <p>This week I’ve been working on a big update to my Apple Watch
  480. sleep tracker, <a href=";ct=sapps&amp;ls=1&amp;mt=8">Sleep++</a>. While I love the app, it is a bit funny
  481. to work on. I am pretty confident that somewhere deep within the
  482. Cupertino mothership, Apple is working on their own sleep tracking
  483. app for the Apple Watch. [&#8230;]</p>
  485. <p>In a weird way I’ve just come to peace with this reality and grown
  486. to understand that this isn’t something that I should really fear.
  487. While the indefinite nature of its arrival certainly gives me a
  488. bit of unease, once I accepted that it was inevitable things got
  489. much simpler.</p>
  490. </blockquote>
  492. <p>Good attitude for a third-party developer.</p>
  494. <p>I think sleep tracking is an inevitable feature for Apple Watch. I&#8217;ve been wearing a Series 2 to sleep lately, and I wake up with between 55-65 percent battery remaining. I can usually get to a full charge &#8212; or close enough, like say 98 percent &#8212; just by charging it while I shower and get dressed. In my use, Series 2 does not need to charge overnight. So it might as well track my sleeping. (My problem with wearing it overnight is that it gives me stand credit for most hours &#8212; I must toss and turn a lot while sleeping.)</p>
  496. <p><strong>Update:</strong> Numerous readers have written in to say that they&#8217;ve been wearing their Apple Watches to sleep for a while, and the problem where they&#8217;re getting credit for stand hours while sleeping has only started with WatchOS 3.1.1. So it seems likely it&#8217;s just a bug.</p>
  498. <div>
  499. <a  title="Permanent link to ‘Developing an App Facing an Inevitable Sherlocking’"  href="">&nbsp;★&nbsp;</a>
  500. </div>
  502. ]]></content>
  503.  </entry><entry>
  505. <link rel="alternate" type="text/html" href=";ct=df&amp;mt=8" />
  506. <link rel="shorturl" href="" />
  507. <id>,2017:/feeds/sponsors//11.33313</id>
  508. <author>
  509. <name>Daring Fireball Department of Commerce</name>
  510. </author>
  512. <published>2017-01-18T12:46:47-05:00</published>
  513. <updated>2017-01-18T12:46:48-05:00</updated>
  515. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  516. <p>You like Wikipedia. You also like obsessive attention to detail.
  517. V for Wikipedia is an opinionated iOS app with nit-picky typography that Erik Spiekermann calls the “best on the small screen yet.” </p>
  519. <p>The map visualization lets you explore nearby places &#8212; it&#8217;s surprising how much you can learn about your own neighborhood on Wikipedia! You can even find articles on your Apple Watch (which sounds crazy, but works great).</p>
  521. <p>Download V for Wikipedia on the App Store.</p>
  523. ]]></content>
  524. <title>[Sponsor] V for Wikipedia</title></entry><entry>
  525. <title>If Apple Gets Into AR or VR, It Should and Probably Will Be a New Platform</title>
  526. <link rel="alternate" type="text/html" href="" />
  527. <link rel="shorturl" type="text/html" href="" />
  528. <link rel="related" type="text/html" href="" />
  529. <id>,2017:/linked//6.33312</id>
  530. <published>2017-01-17T23:55:32Z</published>
  531. <updated>2017-01-18T01:27:24Z</updated>
  532. <author>
  533. <name>John Gruber</name>
  534. <uri></uri>
  535. </author>
  536. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  537. <p>Zach LeBar:</p>
  539. <blockquote>
  540.  <p>Here’s a crazy theory: what if Apple’s big AR play, is
  541. macOS-focused?</p>
  543. <p>We know that Tim Cook has repeatedly talked about how AR is an
  544. interest of Apple’s. On analyst calls they often deflect
  545. attention from questions about VR towards AR. Up ‘til now, most
  546. have assumed this is because Apple is more interested in
  547. iOS-based applications of these technologies, and that they’re
  548. looking to differentiate themselves from their Android-based
  549. competitors who are already offering VR options. There have even
  550. been <a href="">rumors from as recently as CES 2017</a> that talk about
  551. Carl Zeiss partnering with Apple on a set of AR glasses. The
  552. pundits are assuming it’s iPhone-related. But Scoble’s report
  553. doesn’t say one way or the other.</p>
  555. <p>What if we’re all looking in the wrong direction? What if we’re
  556. blinded by iOS and missing what a tremendous play AR for macOS
  557. could be?</p>
  558. </blockquote>
  560. <p>This isn&#8217;t how Apple typically approaches new human-computer interaction technologies. They don&#8217;t just retrofit their existing platform for the new technology. That&#8217;s what Microsoft does with Windows. The iPhone didn&#8217;t run the Mac OS. The underlying core OS, yes, but everything user-facing was done from scratch, specific to the nature of a touch screen. Apple creates new platforms for new interaction technologies.</p>
  562. <p>I strongly suspect that&#8217;s what Apple would do for AR or VR. It could piggyback on the iPhone for network connectivity, as the Watch does, but it&#8217;d be its own software platform.</p>
  564. <p>I suppose it&#8217;s possible that Apple could use AR just to impose a big virtual display in front of the user. That wouldn&#8217;t work at all with iOS&#8217;s touch-based paradigm. It could work with the Mac&#8217;s mouse pointer and keyboard paradigm. But it doesn&#8217;t sound like a good idea to me. I don&#8217;t think it would be better than a non-virtual big display on your desktop, and I don&#8217;t think toting around a bulky pair of goggles would be better than the built-in displays on MacBooks. It just seems incredibly short-sighted to treat AR or VR as an output for traditional desktop computing.</p>
  566. <div>
  567. <a  title="Permanent link to ‘If Apple Gets Into AR or VR, It Should and Probably Will Be a New Platform’"  href="">&nbsp;★&nbsp;</a>
  568. </div>
  570. ]]></content>
  571.  </entry><entry>
  572. <title>The Problem With AMP</title>
  573. <link rel="alternate" type="text/html" href="" />
  574. <link rel="shorturl" type="text/html" href="" />
  575. <link rel="related" type="text/html" href="" />
  576. <id>,2017:/linked//6.33311</id>
  577. <published>2017-01-17T23:21:51Z</published>
  578. <updated>2017-01-17T23:21:52Z</updated>
  579. <author>
  580. <name>John Gruber</name>
  581. <uri></uri>
  582. </author>
  583. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  584. <p>Kyle Schreiber:</p>
  586. <blockquote>
  587.  <p>The largest complaint by far is that the URLs for AMP links differ
  588. from the canonical URLs for the same content, making sharing
  589. difficult. The current URLs are a mess. They all begin with some
  590. form of <code></code> before showing a URL to the
  591. AMP version of the site. There is currently no way to find the
  592. canonical link to the page without guessing what the original URL
  593. is. This usually involves removing either a <code>.amp</code> or <code>?amp=1</code>
  594. from the URL to get to the actual page.</p>
  596. <p>Make no mistake. AMP is about lock-in for Google. AMP is meant to
  597. keep publishers tied to Google. Clicking on an AMP link feels like
  598. you never even leave the search page, and links to AMP content are
  599. displayed prominently in Google’s news carousel. This is their
  600. response to similar formats from both Facebook and Apple, both of
  601. which are designed to keep users within their respective
  602. ecosystems. However, Google’s implementation of AMP is more broad
  603. and far reaching than the Apple and Facebook equivalents. Google’s
  604. implementation of AMP is on the open web and isn’t limited to just
  605. an app like Facebook or Apple.</p>
  606. </blockquote>
  608. <p>Back in October <a href="">I asked why websites are publishing AMP pages</a>. The lock-in aspect makes no sense to me. Why would I want to cede control over my pages to Google? AMP pages do load fast, but if publishers want their web pages to load fast, they can just engineer them to load fast. Best answers I got were that it wasn&#8217;t really strategic &#8212; publishers are going with AMP just because their SEO people are telling them to, because Google features AMP pages in search results. I suppose that <em>is</em> a strategy, but ceding control over your content to Google isn&#8217;t a good one in the long term.</p>
  610. <p>As Schreiber points out, with things like Facebook Instant Articles and Apple News, the canonical URL for each story remains on the publisher&#8217;s own website. With AMP, from the perspective of typical users, the canonical URL is on</p>
  612. <div>
  613. <a  title="Permanent link to ‘The Problem With AMP’"  href="">&nbsp;★&nbsp;</a>
  614. </div>
  616. ]]></content>
  617.  </entry><entry>
  618. <title>Google Infrastructure Security Design Overview</title>
  619. <link rel="alternate" type="text/html" href="" />
  620. <link rel="shorturl" type="text/html" href="" />
  621. <link rel="related" type="text/html" href="" />
  622. <id>,2017:/linked//6.33309</id>
  623. <published>2017-01-17T23:07:57Z</published>
  624. <updated>2017-01-17T23:07:58Z</updated>
  625. <author>
  626. <name>John Gruber</name>
  627. <uri></uri>
  628. </author>
  629. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  630. <p>Google:</p>
  632. <blockquote>
  633.  <p>This document gives an overview of how security is designed into
  634. Google’s technical infrastructure. This global scale
  635. infrastructure is designed to provide security through the entire
  636. information processing lifecycle at Google. This infrastructure
  637. provides secure deployment of services, secure storage of data
  638. with end user privacy safeguards, secure communications between
  639. services, secure and private communication with customers over the
  640. internet, and safe operation by administrators.</p>
  641. </blockquote>
  643. <p>Quite a few interesting bits in this document, including this:</p>
  645. <blockquote>
  646.  <p>A Google data center consists of thousands of server machines
  647. connected to a local network. Both the server boards and the
  648. networking equipment are custom-designed by Google. We vet
  649. component vendors we work with and choose components with care,
  650. while working with vendors to audit and validate the security
  651. properties provided by the components. We also design custom
  652. chips, including a hardware security chip that is currently being
  653. deployed on both servers and peripherals. These chips allow us to
  654. securely identify and authenticate legitimate Google devices at
  655. the hardware level.</p>
  656. </blockquote>
  658. <div>
  659. <a  title="Permanent link to ‘Google Infrastructure Security Design Overview’"  href="">&nbsp;★&nbsp;</a>
  660. </div>
  662. ]]></content>
  663.  </entry><entry>
  664. <title>FTC Charges Qualcomm With Monopolizing Key Semiconductor Device Used in Cell Phones</title>
  665. <link rel="alternate" type="text/html" href="" />
  666. <link rel="shorturl" type="text/html" href="" />
  667. <link rel="related" type="text/html" href="" />
  668. <id>,2017:/linked//6.33308</id>
  669. <published>2017-01-17T22:59:14Z</published>
  670. <updated>2017-01-17T23:02:55Z</updated>
  671. <author>
  672. <name>John Gruber</name>
  673. <uri></uri>
  674. </author>
  675. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  676. <p>The U.S. Federal Trade Commission:</p>
  678. <blockquote>
  679.  <p><em>Extracted exclusivity from Apple in exchange for reduced patent
  680. royalties.</em> Qualcomm precluded Apple from sourcing baseband
  681. processors from Qualcomm’s competitors from 2011 to 2016. Qualcomm
  682. recognized that any competitor that won Apple’s business would
  683. become stronger, and used exclusivity to prevent Apple from
  684. working with and improving the effectiveness of Qualcomm’s
  685. competitors.</p>
  686. </blockquote>
  688. <p>I wonder who brought this complaint to the FTC &#8212; Apple, Qualcomm&#8217;s competitors, or both?</p>
  690. <blockquote>
  691.  <p>The Commission vote to file the complaint was 2-1. <a href="">Commissioner
  692. Maureen K. Ohlhausen dissented and issued a statement</a>. Both a
  693. public and sealed version of the complaint were filed in the U.S.
  694. District Court for the Northern District of California on January
  695. 17, 2017.</p>
  696. </blockquote>
  698. <p><a href="">Ohlhausen&#8217;s dissent</a> is quite brief, and worth a read.</p>
  700. <div>
  701. <a  title="Permanent link to ‘FTC Charges Qualcomm With Monopolizing Key Semiconductor Device Used in Cell Phones’"  href="">&nbsp;★&nbsp;</a>
  702. </div>
  704. ]]></content>
  705.  </entry><entry>
  706. <title>The Pipe Dream of Ara</title>
  707. <link rel="alternate" type="text/html" href="" />
  708. <link rel="shorturl" type="text/html" href="" />
  709. <link rel="related" type="text/html" href="" />
  710. <id>,2017:/linked//6.33307</id>
  711. <published>2017-01-17T21:37:18Z</published>
  712. <updated>2017-01-17T21:37:20Z</updated>
  713. <author>
  714. <name>John Gruber</name>
  715. <uri></uri>
  716. </author>
  717. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  718. <p>How far out in the weeds was Google&#8217;s modular &#8220;Project Ara&#8221; phone concept before they finally pulled the plug on it? This far out, according to Harrison Weber&#8217;s report for VentureBeat:</p>
  720. <blockquote>
  721.  <p>Imagine the modules developers might dream up. There were the
  722. obvious ideas, like specialized cameras and high-end speakers. But
  723. modules could get stranger, wilder, too. One module idea, in
  724. particular, frequently derailed meetings inside ATAP’s walls, as
  725. studio leaders strained to picture a module gold rush akin to
  726. Apple’s App Store.</p>
  728. <p>“One of the modules that we were working on was basically like a
  729. tiny aquarium for your phone,” said the source. “It was a little
  730. tiny biome that would go inside of a module and it would have a
  731. microscope on the bottom part, and it would have live tardigrades
  732. and algae &#8212; some people call them water bears. They are the
  733. tiniest living organism. We had this idea to build a tardigrade
  734. module and we’d build a microscope with it. So you’d have this app
  735. on your phone and you could essentially look at the tardigrades up
  736. close and watch them floating around.” Brooklyn-based art, design,
  737. and technology agency Midnight Commercial conceived the idea, and
  738. was commissioned by Google to build it, demonstrating the depth of
  739. what developers could create.</p>
  740. </blockquote>
  742. <div>
  743. <a  title="Permanent link to ‘The Pipe Dream of Ara’"  href="">&nbsp;★&nbsp;</a>
  744. </div>
  746. ]]></content>
  747.  </entry><entry>
  748. <title>Crowdsourcing Is No Way to Design a Phone (Or Anything Else for That Matter)</title>
  749. <link rel="alternate" type="text/html" href="" />
  750. <link rel="shorturl" type="text/html" href="" />
  751. <link rel="related" type="text/html" href="" />
  752. <id>,2017:/linked//6.33306</id>
  753. <published>2017-01-17T21:26:20Z</published>
  754. <updated>2017-01-17T23:11:23Z</updated>
  755. <author>
  756. <name>John Gruber</name>
  757. <uri></uri>
  758. </author>
  759. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  760. <p>Ashley Carman, writing for The Verge:</p>
  762. <blockquote>
  763.  <p>ZTE’s crowdsourced phone has already had quite a journey. After
  764. the phone’s concept &#8212; an eye-tracking, self-adhesive device &#8212;
  765. was voted on by ZTE users, the phone was put <a href="">on
  766. Kickstarter</a>. Now ZTE is giving us a clearer idea of what to
  767. expect specs-wise. [&#8230;]</p>
  769. <p>Although it has the hardware specs down, ZTE told me at CES that
  770. they haven’t totally figured out the phone’s software, like how to
  771. get it to eye track. The company also didn’t divulge any details
  772. around the self-adhesive case, so we have no idea how the phone
  773. will stick to different surfaces. Still, Hawkeye costs $199 on
  774. Kickstarter if you feel like preordering and waiting for more
  775. details to trickle out. ZTE could use the help too; it has only
  776. raised $32,000 out of its $500,000 goal.</p>
  777. </blockquote>
  779. <p>Good luck with that.</p>
  781. <div>
  782. <a  title="Permanent link to ‘Crowdsourcing Is No Way to Design a Phone (Or Anything Else for That Matter)’"  href="">&nbsp;★&nbsp;</a>
  783. </div>
  785. ]]></content>
  786.  </entry><entry>
  787. <title>Samsung Heir Faces Arrest on Charges of Bribing South Korea’s President</title>
  788. <link rel="alternate" type="text/html" href="" />
  789. <link rel="shorturl" type="text/html" href="" />
  790. <link rel="related" type="text/html" href="" />
  791. <id>,2017:/linked//6.33305</id>
  792. <published>2017-01-16T22:00:01Z</published>
  793. <updated>2017-01-17T00:56:08Z</updated>
  794. <author>
  795. <name>John Gruber</name>
  796. <uri></uri>
  797. </author>
  798. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  799. <p>Choe Sang-Hun, reporting for the NYT:</p>
  801. <blockquote>
  802.  <p>The sprawling investigation into President Park Geun-hye of South Korea took a dramatic turn on Monday with word that prosecutors were seeking the arrest of the de facto head of Samsung, one of the world’s largest conglomerates, on charges that he bribed the president and her secretive confidante. [&#8230;]</p>
  804. <p>Mr. Lee is accused of instructing Samsung subsidiaries to make payments totaling 43 billion won ($36 million) to the family of Ms. Park’s confidante, Choi Soon-sil, and to two foundations that Ms. Choi controlled, in exchange for help from Ms. Park in facilitating a father-to-son transfer of ownership control of Samsung.</p>
  805. </blockquote>
  807. <p>Shocking that something like this would happen to a company as morally scrupulous as Samsung. Shocking.</p>
  809. <div>
  810. <a  title="Permanent link to ‘Samsung Heir Faces Arrest on Charges of Bribing South Korea’s President’"  href="">&nbsp;★&nbsp;</a>
  811. </div>
  813. ]]></content>
  814.  </entry><entry>
  815. <title>Apple Insider: ‘Safari Not Able to Play New 4K Videos From YouTube Homepage, Likely Due to VP9 Shift’</title>
  816. <link rel="alternate" type="text/html" href="" />
  817. <link rel="shorturl" type="text/html" href="" />
  818. <link rel="related" type="text/html" href="" />
  819. <id>,2017:/linked//6.33304</id>
  820. <published>2017-01-16T21:43:06Z</published>
  821. <updated>2017-01-16T21:53:11Z</updated>
  822. <author>
  823. <name>John Gruber</name>
  824. <uri></uri>
  825. </author>
  826. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  827. <p>Mike Wuerthele, reporting for Apple Insider: </p>
  829. <blockquote>
  830.  <p>What appears to be Google&#8217;s shift to the VP9 codec for delivering 4K video on the YouTube homepage is preventing Safari users from watching videos uploaded to the service since early December in full 4K resolution, but not from viewing webpage-embedded videos in the same resolution.</p>
  832. <p>The shift appears to have taken place on Dec. 6, according to a Reddit thread delving into the issue. Google has been pushing the open and royalty-free VP9 codec as an alternative to the paid H.265 spec since 2014, but has never said that it would stop offering 4K video on the YouTube site in other formats, like the Apple-preferred H.264.</p>
  833. </blockquote>
  835. <p>I&#8217;m curious what Google&#8217;s thinking is here. My guess: a subtle nudge to get more Mac users to switch from Safari to Chrome. 4K playback is going to require H.264 support if they want it to work on iOS, though.</p>
  837. <div>
  838. <a  title="Permanent link to ‘Apple Insider: &#8216;Safari Not Able to Play New 4K Videos From YouTube Homepage, Likely Due to VP9 Shift&#8217;’"  href="">&nbsp;★&nbsp;</a>
  839. </div>
  841. ]]></content>
  842.  </entry><entry>
  843. <title>Android’s Emoji Problem</title>
  844. <link rel="alternate" type="text/html" href="" />
  845. <link rel="shorturl" type="text/html" href="" />
  846. <link rel="related" type="text/html" href="" />
  847. <id>,2017:/linked//6.33303</id>
  848. <published>2017-01-16T21:28:22Z</published>
  849. <updated>2017-01-16T21:28:24Z</updated>
  850. <author>
  851. <name>John Gruber</name>
  852. <uri></uri>
  853. </author>
  854. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  855. <p>One practical side-effect of the fact that the overwhelming majority of Android phones are running old versions of the OS: they don&#8217;t have the latest emoji.</p>
  857. <div>
  858. <a  title="Permanent link to ‘Android&#8217;s Emoji Problem’"  href="">&nbsp;★&nbsp;</a>
  859. </div>
  861. ]]></content>
  862.  </entry><entry>
  863. <title>The Unsung iPhone Sine Qua Non</title>
  864. <link rel="alternate" type="text/html" href="" />
  865. <link rel="shorturl" type="text/html" href="" />
  866. <link rel="related" type="text/html" href="" />
  867. <id>,2017:/linked//6.33302</id>
  868. <published>2017-01-16T21:26:49Z</published>
  869. <updated>2017-01-17T00:50:52Z</updated>
  870. <author>
  871. <name>John Gruber</name>
  872. <uri></uri>
  873. </author>
  874. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  875. <p>Jean-Louis Gassée:</p>
  877. <blockquote>
  878.  <p>In retrospect, the ascendency of Smartphone 2.0 and the way it has
  879. shaped our culture seems obvious and natural. But the celebration
  880. and contemplation overlooks a crucial <a href="">Sine Qua
  881. Non</a>, a necessary (but
  882. not sufficient) condition: Unlocking the carriers’ grip on handset
  883. specifications, marketing, and content distribution.</p>
  885. <p>More specifically, we owe Steve Jobs an enormous debt of gratitude
  886. for breaking the carriers’ backs (to avoid a more colorful
  887. phrase).</p>
  888. </blockquote>
  890. <p>It wasn&#8217;t enough that it was revolutionary in both hardware and software. Apple needed something no major handset maker had ever gotten before, or has gotten since: total control.</p>
  892. <div>
  893. <a  title="Permanent link to ‘The Unsung iPhone Sine Qua Non’"  href="">&nbsp;★&nbsp;</a>
  894. </div>
  896. ]]></content>
  897.  </entry><entry>
  898. <title>A Russian Journalist on What to Expect Under Trump</title>
  899. <link rel="alternate" type="text/html" href="https:[email protected]__kovalev/message-to-american-media-from-russia-6e2e76eeae77" />
  900. <link rel="shorturl" type="text/html" href="" />
  901. <link rel="related" type="text/html" href="" />
  902. <id>,2017:/linked//6.33301</id>
  903. <published>2017-01-16T21:19:06Z</published>
  904. <updated>2017-01-16T21:19:08Z</updated>
  905. <author>
  906. <name>John Gruber</name>
  907. <uri></uri>
  908. </author>
  909. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  910. <p>Russian journalist Alexey Kovalev, in the wake of Trump&#8217;s farcical press conference last week:</p>
  912. <blockquote>
  913.  <p>Given that Putin is probably a role model for Trump, it’s no
  914. surprise that he’s apparently taking a page from Putin’s playbook.
  915. I have some observations to share with my American colleagues.
  916. You’re in this for at least another four years, and you’ll be
  917. dealing with things Russian journalists have endured for almost
  918. two decades now. I’m talking about Putin here, but see if you can
  919. apply any of the below to your own leader.</p>
  921. <p>Facts don’t matter. You can’t hurt this man with facts or reason.
  922. He’ll always outmaneuver you. He’ll always wriggle out of whatever
  923. carefully crafted verbal trap you lay for him. Whatever he says,
  924. you won’t be able to challenge him. He always comes with a bag of
  925. meaningless factoids (Putin likes to drown questions he doesn’t
  926. like in dull, unverifiable stats, figures and percentages),
  927. platitudes, false moral equivalences and straight, undiluted
  928. bullshit. He knows it’s a one-way communication, not an interview.
  929. You can’t follow up on your questions or challenge him. So he can
  930. throw whatever he wants at you in response, and you’ll just have
  931. to swallow it. Some journalists will try to preempt this by asking
  932. two questions at once, against the protests of their colleagues
  933. also vying for attention, but that also won’t work: he’ll answer
  934. the one he thinks is easier, and ignore the other.</p>
  935. </blockquote>
  937. <p><a href="">Josh Marshall responds</a>:</p>
  939. <blockquote>
  940.  <p>Trump wants to bully the press and profit off the presidency. He&#8217;s
  941. told us this clearly in his own words. We need to accept the
  942. reality of both. The press should cover him on that basis, as a
  943. coward and a crook. The big corporate media organizations may not
  944. be able to use those words, I understand, but they should employ
  945. that prism. The truth is that his threats against the press to
  946. date are ones it is best to laugh at. If Trump should take some
  947. un- or extra-constitutional actions, we will deal with that when
  948. it happens. I doubt he will or can. But I won&#8217;t obsess about it in
  949. advance. Journalists should be unbowed and aggressive and with a
  950. sense of humor until something happens to prevent them from doing
  951. so. Trump is a punk and a bully. People who don&#8217;t surrender up
  952. their dignity to him unhinge him.</p>
  953. </blockquote>
  955. <div>
  956. <a  title="Permanent link to ‘A Russian Journalist on What to Expect Under Trump’"  href="">&nbsp;★&nbsp;</a>
  957. </div>
  959. ]]></content>
  960.  </entry><entry>
  961. <title>Apple in 2016: The Six Colors Report Card</title>
  962. <link rel="alternate" type="text/html" href="" />
  963. <link rel="shorturl" type="text/html" href="" />
  964. <link rel="related" type="text/html" href="" />
  965. <id>,2017:/linked//6.33300</id>
  966. <published>2017-01-16T15:25:14Z</published>
  967. <updated>2017-01-16T15:39:20Z</updated>
  968. <author>
  969. <name>John Gruber</name>
  970. <uri></uri>
  971. </author>
  972. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  973. <p>Jason Snell:</p>
  975. <blockquote>
  976.  <p>As we close the door on 2016, I thought it would be useful to look back at the year gone by and ask a panel of my peers who pay attention to Apple and related markets to take a moment and reflect on Apple’s performance in the past year.</p>
  977. </blockquote>
  979. <p>This survey is such a valuable service. The consensus scores feel like a very accurate assessment of Apple&#8217;s year.</p>
  981. <div>
  982. <a  title="Permanent link to ‘Apple in 2016: The Six Colors Report Card’"  href="">&nbsp;★&nbsp;</a>
  983. </div>
  985. ]]></content>
  986.  </entry><entry>
  987. <title>Q1 DF RSS Feed Sponsorships</title>
  988. <link rel="alternate" type="text/html" href="" />
  989. <link rel="shorturl" type="text/html" href="" />
  990. <link rel="related" type="text/html" href="" />
  991. <id>,2017:/linked//6.33298</id>
  992. <published>2017-01-15T22:39:00Z</published>
  993. <updated>2017-01-15T22:39:18Z</updated>
  994. <author>
  995. <name>John Gruber</name>
  996. <uri></uri>
  997. </author>
  998. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  999. <p>The Q1 sponsorship schedule is pretty open, including a last-minute opening for this coming week. If you&#8217;ve got a product or service to promote to DF&#8217;s discerning audience, <a href="">get in touch</a>.</p>
  1001. <div>
  1002. <a  title="Permanent link to ‘Q1 DF RSS Feed Sponsorships’"  href="">&nbsp;★&nbsp;</a>
  1003. </div>
  1005. ]]></content>
  1006.  </entry><entry>
  1007. <title>Bloomberg on Andy Rubin’s New Company, Essential</title>
  1008. <link rel="alternate" type="text/html" href="" />
  1009. <link rel="shorturl" type="text/html" href="" />
  1010. <link rel="related" type="text/html" href="" />
  1011. <id>,2017:/linked//6.33299</id>
  1012. <published>2017-01-15T22:38:45Z</published>
  1013. <updated>2017-01-15T22:38:46Z</updated>
  1014. <author>
  1015. <name>John Gruber</name>
  1016. <uri></uri>
  1017. </author>
  1018. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1019. <p>Mark Gurman and Mark Bergen, reporting for Bloomberg:</p>
  1021. <blockquote>
  1022.  <p>Rubin, creator of the Android operating system, is planning to
  1023. marry his background in software with artificial intelligence in a
  1024. risky business: consumer hardware. Armed with about a 40-person
  1025. team, filled with recruits from Apple Inc. and Alphabet Inc.&#8217;s
  1026. Google, Rubin is preparing to announce a new company called
  1027. Essential and serve as its Chief Executive Officer, according to
  1028. people familiar with the matter. [&#8230;]</p>
  1030. <p>While still in the prototyping stage, Rubin&#8217;s phone is aimed at
  1031. the top of the market where Apple Inc.&#8217;s iPhone and Alphabet
  1032. Inc.&#8217;s new Pixel reside. It&#8217;s expected to include high-end
  1033. materials and the ability to gain new hardware features over time,
  1034. the people said. Representatives for Rubin and Sprint declined to
  1035. comment.</p>
  1036. </blockquote>
  1038. <p>The problem with any sort of modular design where the goal is to &#8220;gain new hardware features over time&#8221; is that the most important hardware components in a phone are the display, camera, CPU, and GPU, and Apple updates the iPhone with industry-leading displays, cameras, CPUs, and GPUs every year.</p>
  1040. <blockquote>
  1041.  <p>At least one prototype of Rubin&#8217;s phone boasts a screen larger
  1042. than the iPhone 7 Plus&#8217;s (5.5-inches) but has a smaller overall
  1043. footprint because of the lack of bezels, one of the people said.
  1044. The startup is experimenting with enabling the phone&#8217;s screen to
  1045. sense different levels of pressure, similar to an iPhone, the
  1046. person said. Rubin&#8217;s team is testing an industrial design with
  1047. metal edges and a back made of ceramic, which is more difficult to
  1048. manufacture than typical smartphone materials, two of the people
  1049. said. [&#8230;]</p>
  1051. <p>Rubin is aiming to put the phone on sale around the middle of this
  1052. year for a price close to that of an iPhone 7 ($649), a person
  1053. familiar with the matter said, adding that all of the plans are
  1054. still in flux.</p>
  1055. </blockquote>
  1057. <p>If it&#8217;s in the prototyping stage right now, in January, and they don&#8217;t know what materials they&#8217;re going to use or what size the display will be, what chance do they possibly have of putting a phone on sale in the &#8220;middle of this year&#8221;?</p>
  1059. <p>Also, no word on what OS they&#8217;re using. I&#8217;m guessing Android with customizations, but it&#8217;s curious the story doesn&#8217;t say.</p>
  1061. <div>
  1062. <a  title="Permanent link to ‘Bloomberg on Andy Rubin&#8217;s New Company, Essential’"  href="">&nbsp;★&nbsp;</a>
  1063. </div>
  1065. ]]></content>
  1066.  </entry><entry>
  1067. <title>Speedtest Desktop Apps for Mac and Windows</title>
  1068. <link rel="alternate" type="text/html" href="" />
  1069. <link rel="shorturl" type="text/html" href="" />
  1070. <link rel="related" type="text/html" href="" />
  1071. <id>,2017:/linked//6.33297</id>
  1072. <published>2017-01-14T16:40:51Z</published>
  1073. <updated>2017-01-14T16:40:52Z</updated>
  1074. <author>
  1075. <name>John Gruber</name>
  1076. <uri></uri>
  1077. </author>
  1078. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1079. <p>My thanks to Ookla for sponsoring this week&#8217;s DF RSS feed to promote their new native apps for Mac and Windows. I&#8217;ve been using their <a href=""></a> web service since forever to diagnose network problems and measure performance. They&#8217;ve had a native app for iOS for years, and it&#8217;s great too.</p>
  1081. <p>Now they have native desktop apps. Very simple, very obvious, and beautifully designed. Try them out today by downloading the Speedtest app from the Windows or Mac App Stores &#8212; free of charge. That&#8217;s it &#8212; excellent new native apps for network speed testing, totally free.</p>
  1083. <div>
  1084. <a  title="Permanent link to ‘Speedtest Desktop Apps for Mac and Windows’"  href="">&nbsp;★&nbsp;</a>
  1085. </div>
  1087. ]]></content>
  1088.  </entry><entry>
  1089. <title>U.S. Appeals Court Allows Group to Sue Apple Over App Store ‘Monopoly’</title>
  1090. <link rel="alternate" type="text/html" href="" />
  1091. <link rel="shorturl" type="text/html" href="" />
  1092. <link rel="related" type="text/html" href="" />
  1093. <id>,2017:/linked//6.33296</id>
  1094. <published>2017-01-13T16:19:56Z</published>
  1095. <updated>2017-01-13T16:19:58Z</updated>
  1096. <author>
  1097. <name>John Gruber</name>
  1098. <uri></uri>
  1099. </author>
  1100. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1101. <p>Stephen Nellis and Dan Levine, reporting for Reuters:</p>
  1103. <blockquote>
  1104.  <p>iPhone app purchasers may sue Apple Inc over allegations that the
  1105. company monopolized the market for iPhone apps by not allowing
  1106. users to purchase them outside the App Store, leading to higher
  1107. prices, a U.S. appeals court ruled on Thursday.</p>
  1108. </blockquote>
  1110. <p>That sound you hear is thousands of indie iOS developers laughing at the notion of the App Store leading to &#8220;higher prices&#8221;.</p>
  1112. <blockquote>
  1113.  <p>Apple had argued that users did not have standing to sue it
  1114. because they purchased apps from developers, with Apple simply
  1115. renting out space to those developers. Developers pay a cut of
  1116. their revenues to Apple in exchange for the right to sell in the
  1117. App Store.</p>
  1119. <p>A lower court sided with Apple, but Judge William A. Fletcher
  1120. ruled that iPhone users purchase apps directly from Apple, which
  1121. gives iPhone users the right to bring a legal challenge against
  1122. Apple. [&#8230;]</p>
  1124. <p>The courts have yet to address the substance of the iPhone users’
  1125. allegations; up this point, the wrangling has been over whether
  1126. they have the right to sue Apple in the first place.</p>
  1127. </blockquote>
  1129. <p>I think it&#8217;s fair to say that users buy apps from Apple, not from the developers, so the fact that they can sue Apple strikes me as the correct ruling. But I don&#8217;t see how Apple can be ruled to have a &#8220;monopoly&#8221; &#8212; everyone knows Android phones comprise a majority of the market. It&#8217;s fair to object to Apple&#8217;s tight control over iOS, but you can&#8217;t fairly call it a &#8220;<a href="">monopoly</a>&#8221;. </p>
  1131. <div>
  1132. <a  title="Permanent link to ‘U.S. Appeals Court Allows Group to Sue Apple Over App Store &#8216;Monopoly&#8217;’"  href="">&nbsp;★&nbsp;</a>
  1133. </div>
  1135. ]]></content>
  1136.  </entry><entry>
  1137. <title>PodSearch</title>
  1138. <link rel="alternate" type="text/html" href="" />
  1139. <link rel="shorturl" type="text/html" href="" />
  1140. <link rel="related" type="text/html" href="" />
  1141. <id>,2017:/linked//6.33295</id>
  1142. <published>2017-01-13T16:06:34Z</published>
  1143. <updated>2017-01-13T16:06:36Z</updated>
  1144. <author>
  1145. <name>John Gruber</name>
  1146. <uri></uri>
  1147. </author>
  1148. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1149. <p>David Smith:</p>
  1151. <blockquote>
  1152.  <p>I have a knack for remembering audio. I’m awful at remembering
  1153. names and faces, but if I hear something I can often recall it
  1154. later. This has manifested itself as a bit of a party trick for
  1155. the podcasts I listen to, where I can quickly find the section of
  1156. a show where a topic was discussed even years after I heard it.
  1157. Fun, but not particularly useful.</p>
  1159. <p>This situation gave me the idea for a little side project,
  1160. <a href="">PodSearch</a>, empowering the same quick podcast recall for anyone.
  1161. The concept was simple. Take a few of my favorite podcasts and run
  1162. them through automated speech-to-text and make the result
  1163. searchable.</p>
  1164. </blockquote>
  1166. <p>This is really amazing. I really ought to pay to get true transcripts for The Talk Show (including the back catalog of episodes), but this is a pretty good way to search my show for keywords.</p>
  1168. <div>
  1169. <a  title="Permanent link to ‘PodSearch’"  href="">&nbsp;★&nbsp;</a>
  1170. </div>
  1172. ]]></content>
  1173.  </entry><entry>
  1174. <title>Chris Lattner on Ted Kremenek</title>
  1175. <link rel="alternate" type="text/html" href="" />
  1176. <link rel="shorturl" type="text/html" href="" />
  1177. <link rel="related" type="text/html" href="" />
  1178. <id>,2017:/linked//6.33294</id>
  1179. <published>2017-01-13T16:01:37Z</published>
  1180. <updated>2017-01-13T16:04:17Z</updated>
  1181. <author>
  1182. <name>John Gruber</name>
  1183. <uri></uri>
  1184. </author>
  1185. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1186. <p>Chris Lattner on Ted Kremenek, his replacement as project lead on Apple&#8217;s Swift team:</p>
  1188. <blockquote>
  1189.  <p>One thing that I don’t think is fully appreciated by the
  1190. community: Ted has been one of the quiet but incredible
  1191. masterminds behind Swift (and Clang, and the Clang Static
  1192. Analyzer) for many years. His approach and modesty has led many to
  1193. misunderstand the fact that he has actually been running the Swift
  1194. team for quite some time (misattributing it to me). While I’m
  1195. super happy to continue to participate in the ongoing evolution
  1196. and design of Swift, I’m clearly outmatched by the members of the
  1197. Apple Swift team, and by Ted’s leadership of the team. This is the
  1198. time for me to graciously hand things over to folks who are far
  1199. more qualified than me. Swift has an incredible future ahead of
  1200. it, and I’m really thrilled to be small part of the force that
  1201. helps guide its direction going forward.</p>
  1202. </blockquote>
  1204. <div>
  1205. <a  title="Permanent link to ‘Chris Lattner on Ted Kremenek’"  href="">&nbsp;★&nbsp;</a>
  1206. </div>
  1208. ]]></content>
  1209.  </entry><entry>
  1210. <title>Consumer Reports Now Recommends MacBook Pros</title>
  1211. <link rel="alternate" type="text/html" href="" />
  1212. <link rel="shorturl" type="text/html" href="" />
  1213. <link rel="related" type="text/html" href="" />
  1214. <id>,2017:/linked//6.33293</id>
  1215. <published>2017-01-12T23:03:43Z</published>
  1216. <updated>2017-01-12T23:36:34Z</updated>
  1217. <author>
  1218. <name>John Gruber</name>
  1219. <uri></uri>
  1220. </author>
  1221. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1222. <p>Consumer Reports:</p>
  1224. <blockquote>
  1225.  <p>New Apple software fixes a battery issue found in CR tests. The software, now in beta, will be part of a broad update soon.</p>
  1226. </blockquote>
  1228. <p>This makes it sound like CR found a problem with the batteries. They didn&#8217;t. They found a bug in a Safari developer mode. It&#8217;s a real bug, but it&#8217;s clear now that it didn&#8217;t justify the initial sensational &#8220;<em>Wow, first ever Apple laptop not recommended by Consumer Reports!</em>&#8221; report. There&#8217;s no way they would&#8217;ve published that rushed initial report for a laptop from any brand other than Apple. Clickbait, pure and simple.</p>
  1230. <div>
  1231. <a  title="Permanent link to ‘Consumer Reports Now Recommends MacBook Pros’"  href="">&nbsp;★&nbsp;</a>
  1232. </div>
  1234. ]]></content>
  1235.  </entry><entry>
  1236. <title>‘This Is Why You Don’t Kiss the Ring’</title>
  1237. <link rel="alternate" type="text/html" href="" />
  1238. <link rel="shorturl" type="text/html" href="" />
  1239. <link rel="related" type="text/html" href="" />
  1240. <id>,2017:/linked//6.33292</id>
  1241. <published>2017-01-12T19:24:00Z</published>
  1242. <updated>2017-01-12T19:24:02Z</updated>
  1243. <author>
  1244. <name>John Gruber</name>
  1245. <uri></uri>
  1246. </author>
  1247. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1248. <p>Good piece by Hamilton Nolan, writing for The Concourse, on Trump&#8217;s press conference yesterday, which had the tone and substance of a professional wrestling promotion:</p>
  1250. <blockquote>
  1251.  <p>These things are not normal. These things are not okay. These are
  1252. actions that flout well-established ethical and civil norms.
  1253. Admittedly, there is something thrilling about watching him do
  1254. this. What will he do next? It always keeps us tuning in, in the
  1255. same way that a violent alcoholic father will always keep his
  1256. children on his toes. But we should not fool ourselves about what
  1257. is happening in front of our eyes. We are all coming to realize
  1258. that our civil society institutions may not be strong enough to
  1259. protect the flawed but fundamentally solid democracy that we
  1260. thought we had. We are witnessing the rise to power of a leader
  1261. who does not care about norms. Since these norms were created to
  1262. prevent political, social, economic, and cultural disasters, we do
  1263. not need to wonder how this will end. It will end poorly.</p>
  1264. </blockquote>
  1266. <div>
  1267. <a  title="Permanent link to ‘&#8216;This Is Why You Don&#8217;t Kiss the Ring&#8217;’"  href="">&nbsp;★&nbsp;</a>
  1268. </div>
  1270. ]]></content>
  1271.  </entry><entry>
  1272. <title>Matthew Yglesias: ‘Beyond Wild Allegations, What’s Clearly True About Trump and Russia Is Disturbing’</title>
  1273. <link rel="alternate" type="text/html" href="" />
  1274. <link rel="shorturl" type="text/html" href="" />
  1275. <link rel="related" type="text/html" href="" />
  1276. <id>,2017:/linked//6.33291</id>
  1277. <published>2017-01-12T19:14:22Z</published>
  1278. <updated>2017-01-12T19:14:23Z</updated>
  1279. <author>
  1280. <name>John Gruber</name>
  1281. <uri></uri>
  1282. </author>
  1283. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1284. <p>Matthew Yglesias, writing for Vox:</p>
  1286. <blockquote>
  1287.  <p><a href="">Allegations</a> now floating around range from the salacious (Russia
  1288. has Trump sex tapes made at the Ritz-Carlton in Moscow) to the
  1289. serious (using intermediaries, Trump and Russia agreed to an
  1290. explicit quid pro quo in which Russia would give him electoral
  1291. help and in exchange he would shift US foreign policy). None of
  1292. this is proven, and much of it is unprovable (if the FSB has a
  1293. secret sex tape, how are we going to find it?) but the truth is
  1294. that these kind of allegations, though difficult to resist, simply
  1295. shouldn’t matter much compared to what’s in the public record.</p>
  1296. </blockquote>
  1298. <div>
  1299. <a  title="Permanent link to ‘Matthew Yglesias: &#8216;Beyond Wild Allegations, What’s Clearly True About Trump and Russia Is Disturbing&#8217;’"  href="">&nbsp;★&nbsp;</a>
  1300. </div>
  1302. ]]></content>
  1303.  </entry><entry>
  1304. <title>Maureen Dowd Interviews Peter Thiel</title>
  1305. <link rel="alternate" type="text/html" href="" />
  1306. <link rel="shorturl" type="text/html" href="" />
  1307. <link rel="related" type="text/html" href="" />
  1308. <id>,2017:/linked//6.33290</id>
  1309. <published>2017-01-12T19:09:30Z</published>
  1310. <updated>2017-01-12T19:30:13Z</updated>
  1311. <author>
  1312. <name>John Gruber</name>
  1313. <uri></uri>
  1314. </author>
  1315. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1316. <p>Maureen Dowd:</p>
  1318. <blockquote>
  1319.  <p>He recalls a story from his and Mr. Musk’s PayPal days, when Mr.
  1320. Musk joined the engineering team’s poker game and bet everything
  1321. on every hand, admitting only afterward that it was his first time
  1322. playing poker. Then there was the time they were driving in Mr.
  1323. Musk’s McLaren F1 car, “the fastest car in the world.” It hit an
  1324. embankment, achieved liftoff, made a 360-degree horizontal turn,
  1325. crashed and was destroyed.</p>
  1327. <p>“It was a miracle neither of us were hurt,” Mr. Thiel says. “I
  1328. wasn’t wearing a seatbelt, which is not advisable. Elon’s first
  1329. comment was, ‘Wow, Peter, that was really intense.’ And then it
  1330. was: ‘You know, I had read all these stories about people who made
  1331. money and bought sports cars and crashed them. But I knew it would
  1332. never happen to me, so I didn’t get any insurance.’ And then we
  1333. hitchhiked the rest of the way to the meeting.”</p>
  1334. </blockquote>
  1336. <p>Peter Thiel may well be smart, but he&#8217;s also dangerously foolish and solipsistic. You have to be a reckless fool to be that smart and get into any car without wearing a seatbelt, let alone a McLaren being driven by a daredevil like Musk.</p>
  1338. <p>On whether Thiel is concerned about Trump&#8217;s upcoming nominee (singular, I hope) for the Supreme Court:</p>
  1340. <blockquote>
  1341.  <p>“I don’t think these things will particularly change. It’s like,
  1342. even if you appointed a whole series of conservative Supreme Court
  1343. justices, I’m not sure that Roe v. Wade would get overturned,
  1344. ever. I don’t know if people even care about the Supreme Court.”</p>
  1345. </blockquote>
  1347. <p>Like I said: Peter Thiel may well be smart, but he&#8217;s also dangerously foolish and solipsistic. </p>
  1349. <div>
  1350. <a  title="Permanent link to ‘Maureen Dowd Interviews Peter Thiel’"  href="">&nbsp;★&nbsp;</a>
  1351. </div>
  1353. ]]></content>
  1354.  </entry><entry>
  1355. <title>The Math Behind a Theoretical 10.5-inch iPad</title>
  1356. <link rel="alternate" type="text/html" href="" />
  1357. <link rel="shorturl" type="text/html" href="" />
  1358. <link rel="related" type="text/html" href="" />
  1359. <id>,2017:/linked//6.33289</id>
  1360. <published>2017-01-12T17:03:02Z</published>
  1361. <updated>2017-01-12T17:03:07Z</updated>
  1362. <author>
  1363. <name>John Gruber</name>
  1364. <uri></uri>
  1365. </author>
  1366. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1367. <p>Dan Provost:</p>
  1369. <blockquote>
  1370.  <p>The math works out perfectly. This new 10.5&#8221; iPad would have the
  1371. exact same resolution as the 12.9&#8221; iPad Pro (2732&#8201;&#215;&#8201;2048), but the
  1372. same pixel density of the iPad mini (326 ppi instead of 264 ppi).
  1373. Crunch the numbers, do a little Pythagorean Theorem, and you end
  1374. up with a screen 10.5&#8221; diagonal (10.47&#8221; to be precise, but none of
  1375. Apple’s stated screen sizes are exact). In terms of physcial
  1376. dimensions, the width of this 10.5&#8221; screen would be exactly the
  1377. same as the height of the iPad mini screen.</p>
  1378. </blockquote>
  1380. <p>Can&#8217;t believe I didn&#8217;t think to do this <a href="">again</a> regarding this rumor. The math works out.</p>
  1382. <div>
  1383. <a  title="Permanent link to ‘The Math Behind a Theoretical 10.5-inch iPad’"  href="">&nbsp;★&nbsp;</a>
  1384. </div>
  1386. ]]></content>
  1387.  </entry><entry>
  1388. <title>WSJ: ‘Apple Sets Its Sights on Hollywood With Plans for Original Content’</title>
  1389. <link rel="alternate" type="text/html" href="" />
  1390. <link rel="shorturl" type="text/html" href="" />
  1391. <link rel="related" type="text/html" href="" />
  1392. <id>,2017:/linked//6.33288</id>
  1393. <published>2017-01-12T16:54:04Z</published>
  1394. <updated>2017-01-12T18:49:12Z</updated>
  1395. <author>
  1396. <name>John Gruber</name>
  1397. <uri></uri>
  1398. </author>
  1399. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1400. <p>Ben Fritz, Tripp Mickle, and Hannah Karp, reporting for the WSJ:</p>
  1402. <blockquote>
  1403.  <p>Apple Inc. is planning to build a significant new business in
  1404. original television shows and movies, according to people familiar
  1405. with the matter, a move that could make it a bigger player in
  1406. Hollywood and offset slowing sales of iPhones and iPads.</p>
  1408. <p>These people said the programming would be available to
  1409. subscribers of Apple’s $10-a-month streaming-music service, which
  1410. has struggled to catch up to the larger Spotify AB. Apple Music
  1411. already includes a limited number of documentary-style segments on
  1412. musicians, but nothing like the premium programming it is now
  1413. seeking.</p>
  1414. </blockquote>
  1416. <p>Interesting, but I don&#8217;t get why they&#8217;re framing this in the context of &#8220;offset[ting] slowing sales of iPhones and iPads&#8221;. I think Apple would be pursuing the exact same original content course regardless of whether iPhone and iPad sales were booming, stagnant, or falling. It&#8217;s just the obvious thing to do.</p>
  1418. <div>
  1419. <a  title="Permanent link to ‘WSJ: &#8216;Apple Sets Its Sights on Hollywood With Plans for Original Content&#8217;’"  href="">&nbsp;★&nbsp;</a>
  1420. </div>
  1422. ]]></content>
  1423.  </entry><entry>
  1424. <title>App Extensions Are Not a Replacement for User Automation</title>
  1425. <link rel="alternate" type="text/html" href="" />
  1426. <link rel="shorturl" type="text/html" href="" />
  1427. <link rel="related" type="text/html" href="" />
  1428. <id>,2017:/linked//6.33287</id>
  1429. <published>2017-01-12T04:31:44Z</published>
  1430. <updated>2017-01-12T04:31:46Z</updated>
  1431. <author>
  1432. <name>John Gruber</name>
  1433. <uri></uri>
  1434. </author>
  1435. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1436. <p>Sal Soghoian, writing for MacStories (there&#8217;s a byline I never expected to write &#8212; it&#8217;s going to take a while to get used to Sal as a civilian):</p>
  1438. <blockquote>
  1439.  <p>Here’s a thought experiment. Let’s imagine that Apple decided to
  1440. combine their engineering resources to form app teams that
  1441. delivered both iOS and macOS versions of applications.</p>
  1443. <p>In such a scenario it may seem logical to retain application
  1444. features common to both platforms and to remove those that were
  1445. perceived to require extra resources. Certainly Automation would
  1446. be something examined in that regard, and the idea might be
  1447. posited that: “App Extensions are equivalent to, or could be a
  1448. replacement for, User Automation in macOS.” And by User
  1449. Automation, I’m referring to Apple Event scripting, Automator,
  1450. Services, the UNIX command line utilities, etc.</p>
  1452. <p>Let’s examine the validity of that conjecture, beginning with
  1453. overviews of App Extensions and User Automation.</p>
  1454. </blockquote>
  1456. <p>It&#8217;s a great article, and I think Sal&#8217;s case is very strong. App extensions are great, but they&#8217;re no replacement for automation. His conclusion:</p>
  1458. <blockquote>
  1459.  <p>But let’s take a step back, and think about this topic
  1460. differently. <em>Why not have both?</em></p>
  1462. <p>Perhaps it is time for Apple and all of us to think of User
  1463. Automation and App Extensions in terms of &#8220;AND&#8221; instead of &#8220;OR.&#8221;
  1464. To embrace the development of a new cross-platform automation
  1465. architecture, maybe called “AutomationKit,” that would incorporate
  1466. the “everyman openness” of User Automation with the focused
  1467. abilities of developer-created plugins. App Extensions could
  1468. become the new macOS System Services, and Automator could save
  1469. workflows as Extensions with access to the Share Menu and new
  1470. “non-selection” extension points. And AutomationKit could even
  1471. include an Apple Event bridge so that it would work with the
  1472. existing macOS automation tools.</p>
  1473. </blockquote>
  1475. <p>Must-read piece for anyone who cares about the Mac as a power user platform. I&#8217;m OK with the current situation, where the Mac has these automation capabilities and iOS does not. I&#8217;d prefer to see iOS <em>gain</em> serious automation capabilities &#8212; even if it&#8217;s an altogether new technology. But I&#8217;m dreadfully afraid of a future where MacOS is devolved to iOS&#8217;s state, with no supported automation technologies.</p>
  1477. <div>
  1478. <a  title="Permanent link to ‘App Extensions Are Not a Replacement for User Automation’"  href="">&nbsp;★&nbsp;</a>
  1479. </div>
  1481. ]]></content>
  1482.  </entry><entry>
  1484.    <link rel="alternate" type="text/html" href="" />
  1485. <link rel="shorturl" href="" />
  1486. <id>,2017://1.33286</id>
  1487. <published>2017-01-11T23:32:45Z</published>
  1488. <updated>2017-01-11T23:56:39Z</updated>
  1489. <author>
  1490. <name>John Gruber</name>
  1491. <uri></uri>
  1492. </author>
  1493. <summary type="html"><![CDATA[<p>Hey, I made a YouTube video.</p>
  1494. ]]></summary>
  1495. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1496. <p>Hey, I made a YouTube video:</p>
  1498. <p><iframe width="500" height="281" src="" frameborder="0" allowfullscreen></iframe></p>
  1502.    ]]></content>
  1503.  <title>★ The Right Way to Pop Your AirPods Out of the Case</title></entry><entry>
  1504. <title>Chris Lattner Lands at Tesla</title>
  1505. <link rel="alternate" type="text/html" href="" />
  1506. <link rel="shorturl" type="text/html" href="" />
  1507. <link rel="related" type="text/html" href="" />
  1508. <id>,2017:/linked//6.33284</id>
  1509. <published>2017-01-10T22:17:28Z</published>
  1510. <updated>2017-01-11T23:38:04Z</updated>
  1511. <author>
  1512. <name>John Gruber</name>
  1513. <uri></uri>
  1514. </author>
  1515. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1516. <p>Tesla:</p>
  1518. <blockquote>
  1519.  <p>We would like to welcome Chris Lattner, who will join Tesla as
  1520. our Vice President of Autopilot Software. Chris’ reputation for
  1521. engineering excellence is well known. He comes to Tesla after 11
  1522. years at Apple where he was primarily responsible for creating
  1523. Swift, the programming language for building apps on Apple
  1524. platforms and one of the fastest growing languages for doing so
  1525. on Linux.</p>
  1526. </blockquote>
  1528. <p>This is a &#8220;holy shit!&#8221; hiring by Tesla. A year or two ago it felt like Apple was gunning for Tesla&#8217;s lead in electric cars. Now, it feels like Apple is out of the car game, and Tesla is gunning for Apple&#8217;s lead in computing. You can&#8217;t overstate what a star Chris Lattner is.</p>
  1530. <p><strong>Update:</strong> Lattner&#8217;s only public comment to date is retweeting <a href="">this observation by Daniel Jalkut</a>:</p>
  1532. <blockquote>
  1533.  <p>I hope folks will not overlook that amid all the drama of
  1534. <a href="">@clattner_llvm</a> leaving Apple, <a href="">@tkremenek</a> remains a huge asset
  1535. for them.</p>
  1536. </blockquote>
  1538. <div>
  1539. <a  title="Permanent link to ‘Chris Lattner Lands at Tesla’"  href="">&nbsp;★&nbsp;</a>
  1540. </div>
  1542. ]]></content>
  1543.  </entry><entry>
  1544. <title>Apple Statement on Consumer Reports’ MacBook Pro Battery Testing</title>
  1545. <link rel="alternate" type="text/html" href="" />
  1546. <link rel="shorturl" type="text/html" href="" />
  1547. <link rel="related" type="text/html" href="" />
  1548. <id>,2017:/linked//6.33283</id>
  1549. <published>2017-01-10T19:58:14Z</published>
  1550. <updated>2017-01-11T00:49:21Z</updated>
  1551. <author>
  1552. <name>John Gruber</name>
  1553. <uri></uri>
  1554. </author>
  1555. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1556. <p>From a statement Apple sent to TechCrunch:</p>
  1558. <blockquote>
  1559.  <p>We appreciate the opportunity to work with Consumer Reports over
  1560. the holidays to understand their battery test results. We learned
  1561. that when testing battery life on Mac notebooks, Consumer Reports
  1562. uses a hidden Safari setting for developing web sites which turns
  1563. off the browser cache. This is not a setting used by customers and
  1564. does not reflect real-world usage. Their use of this developer
  1565. setting also triggered an obscure and intermittent bug reloading
  1566. icons which created inconsistent results in their lab. After we
  1567. asked Consumer Reports to run the same test using normal user
  1568. settings, they told us their MacBook Pro systems consistently
  1569. delivered the expected battery life. We have also fixed the bug
  1570. uncovered in this test.</p>
  1571. </blockquote>
  1573. <p>So there&#8217;s a bug in Safari when you disable the cache (Develop: Disable Caches &#8212; and the entire Develop menu is off by default). Disabling the cache <em>should</em> decrease battery life in a test like CR&#8217;s. And if there&#8217;s a bug, I can see why it might dramatically decrease battery life. But that still doesn&#8217;t explain how Consumer Reports&#8217;s testing showed results ranging from 3.75 hours (poor) to 19.5 hours (seemingly too good to be true).</p>
  1575. <p>I still think something was/is wrong with Consumer Reports&#8217;s testing (19.5 hours?) but I don&#8217;t think it&#8217;s fair to say that disabling the caches is unfair or a flawed method. And while the preference setting is obscure, I wouldn&#8217;t call it &#8220;hidden&#8221;. To me, hidden preferences are the ones you can only enable from calls to <code>defaults</code> in Terminal. You can turn the Develop menu on by clicking a visible checkbox in the &#8220;Advanced&#8221; tab of Safari&#8217;s preferences.</p>
  1577. <div>
  1578. <a  title="Permanent link to ‘Apple Statement on Consumer Reports&#8217; MacBook Pro Battery Testing’"  href="">&nbsp;★&nbsp;</a>
  1579. </div>
  1581. ]]></content>
  1582.  </entry><entry>
  1583. <title>Chris Lattner Is Leaving Apple</title>
  1584. <link rel="alternate" type="text/html" href="" />
  1585. <link rel="shorturl" type="text/html" href="" />
  1586. <link rel="related" type="text/html" href="" />
  1587. <id>,2017:/linked//6.33282</id>
  1588. <published>2017-01-10T19:06:58Z</published>
  1589. <updated>2017-01-10T20:22:04Z</updated>
  1590. <author>
  1591. <name>John Gruber</name>
  1592. <uri></uri>
  1593. </author>
  1594. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1595. <p>Chris Lattner, in an email on the Swift Evolution mailing list:</p>
  1597. <blockquote>
  1598.  <p>I’m happy to announce that Ted Kremenek will be taking over for me
  1599. as “Project Lead” for the Swift project, managing the
  1600. administrative and leadership responsibility for This
  1601. recognizes the incredible effort he has already been putting into
  1602. the project, and reflects a decision I’ve made to leave Apple
  1603. later this month to pursue an opportunity in another space. This
  1604. decision wasn&#8217;t made lightly, and I want you all to know that I’m
  1605. still completely committed to Swift. I plan to remain an active
  1606. member of the Swift Core Team, as well as a contributor to the
  1607. swift-evolution mailing list.</p>
  1608. </blockquote>
  1610. <p>Sounds like an orderly, no-drama (and perhaps long-planned?) transition. Sure am curious what his &#8220;opportunity in another space&#8221; is, though.</p>
  1612. <p>Lattner is a really smart, very well-liked, and deeply respected guy. His leaving is a loss for Apple.</p>
  1614. <p>Swift really is Lattner&#8217;s baby &#8212; <a href="">he developed the earliest versions of it by himself</a> starting in 2010, before work expanded to a larger group in Apple&#8217;s Developer Tools group. (Swift wasn&#8217;t announced publicly <a href="">until June 2014</a>.) The Apple developer community is still in the middle of the transition to Swift. I&#8217;m a little surprised he&#8217;d leave in the midst of the upheaval. It&#8217;s a thriving language, but it is far from a completed project &#8212; neither the language itself nor the OS frameworks.</p>
  1616. <div>
  1617. <a  title="Permanent link to ‘Chris Lattner Is Leaving Apple’"  href="">&nbsp;★&nbsp;</a>
  1618. </div>
  1620. ]]></content>
  1621.  </entry><entry>
  1623.    <link rel="alternate" type="text/html" href="" />
  1624. <link rel="shorturl" href="" />
  1625. <id>,2017://1.33257</id>
  1626. <published>2017-01-03T23:54:25Z</published>
  1627. <updated>2017-01-04T05:08:43Z</updated>
  1628. <author>
  1629. <name>John Gruber</name>
  1630. <uri></uri>
  1631. </author>
  1632. <summary type="html"><![CDATA[<p>Updates to the same basic design would make sense. An all-new design would make sense. Getting out of the Mac Pro game would make sense. Selling 1000-day old pro workstations at the same prices as in 2013 makes <em>no</em> sense. Whatever the explanation is, this situation is an unmitigated disaster.</p>
  1633. ]]></summary>
  1634. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1635. <p><a href="">Chuq Von Rospach has a thoughtful look at the state of Apple</a>. The whole piece is worth reading, but his comments on two particular products stood out to me. First, the AirPort lineup:</p>
  1637. <blockquote>
  1638.  <p>Apple has products it has let languish without any significant
  1639. update for long periods of time. If you look at how Apple’s
  1640. treated their AirPort line, you’d think Wi-Fi was a mature
  1641. technology where nothing was really changing. In fact, a lot is
  1642. happening including a big shift to mesh networks, and Apple has
  1643. seemingly ignored all of that. It used to be you bought Airports
  1644. because they were some of the best Wi-FI devices out there. Today,
  1645. the only reason to buy them is you want easy, and because it has
  1646. the Apple brand. They’re woefully out of date (and in fact, I just
  1647. replaced mine with a set of Eero devices, which are Apple easy to
  1648. use, and blow Apple’s products away in terms of performance).
  1649. Rumors have come out that Apple has cancelled future development
  1650. of these, but they’re still for sale. Why?</p>
  1651. </blockquote>
  1653. <p>Something is clearly wrong with the AirPort line. Either it should have been updated long ago to remain state-of-the-art, or it should have been discontinued. Whether or not Apple should still be in the Wi-Fi router game is a reasonable argument. I think they should, but I can see the other side of the argument (that other companies do it well, and Apple should focus on areas where they stand alone). But there&#8217;s no reasonable argument for the current AirPort state of affairs.</p>
  1655. <p>And on the Mac Pro:</p>
  1657. <blockquote>
  1658.  <p>To put the Mac pro in context: This was the “Can’t Innovate my
  1659. Ass” product that Apple produced to counter criticism that it
  1660. wasn’t innovative any more and that it was letting the Mac product
  1661. line languish (hey, this isn’t a new complaint…). They came out
  1662. with something that was visually distinctive and they build a
  1663. really interesting set of guts inside the trash can.</p>
  1665. <p>But here’s the problem: in retrospect, what they built was a
  1666. device based around their own ego needs of proving their critics
  1667. wrong, not a device that served the purposes of their power users.
  1668. It’s not configurable, it’s not upgradeable, it’s not expandable:
  1669. It’s pretty, and full of (for 2013) innovative hardware design,
  1670. but is that really what Apple’s power users needed?</p>
  1671. </blockquote>
  1673. <p>&#8220;What the hell happened with the Mac Pro?&#8221; is the most interesting question about Apple today. Because something clearly went way wrong with this product. I&#8217;m not convinced the basic idea for the design is unsound &#8212; the idea is that expansion would come in the form of external peripherals, rather than things you install inside the box. I still think that&#8217;s probably the future of &#8220;expandable&#8221; computing.</p>
  1675. <p>If Apple had updated the Mac Pro on a roughly annual basis, we wouldn&#8217;t be calling this a disaster. I&#8217;m sure there would still be people who would wish that Apple had stuck with the traditional tower form factor, but we wouldn&#8217;t all be saying &#8220;What the fuck?&#8221;</p>
  1677. <p>If Apple were going to update this Mac Pro, we should have seen it two years ago. If Apple were going to scrap this design and replace it with something else (like they did with <a href="">the short-lived &#8220;sunflower&#8221; iMac G4 design in 2002</a>), we should have seen the replacement a <em>year</em> ago. And if they were planning to abolish the Mac Pro, that should have happened this past year &#8212; or at least we should have seen prices drop significantly on these three-year-old workstations.<sup id="fnr1-2017-01-03"><a href="#fn1-2017-01-03">1</a></sup></p>
  1679. <p>Updates to the same basic design would make sense. An all-new design would make sense. Getting out of the Mac Pro game would make sense. Selling 1000-day-old pro workstations at the same prices as in 2013 makes <em>no</em> sense. Whatever the explanation is, this situation is an unmitigated disaster.</p>
  1681. <div class="footnotes">
  1682. <hr />
  1683. <ol>
  1684. <li id="fn1-2017-01-03">
  1685. <p>Other computer makers raise and lower prices as component prices change. Apple comes out with a price and sticks with it. One reason for that is branding. Stable prices at &#8220;round&#8221; numbers &#8212; $1499 instead of $1427 or whatever &#8212; are a sign of a premium quality brand. And they don&#8217;t lower prices on older products unless they keep them in the product lineup <em>after</em> their replacements have been introduced. What they almost never do is lower the price of a product just because it&#8217;s old, without a replacement. Thus, if Apple were to announce price drops on the Mac Pro lineup, without releasing updated models, I would take that as a very strong sign that they&#8217;re getting out of the standalone pro desktop market. But they haven&#8217;t done that &#8212; they&#8217;re still selling these Mac Pros at the same prices as when they were announced over three years ago. I take that as a sign that they plan to replace them, or at least hope to replace them, but have failed for whatever reason(s).&nbsp;<a href="#fnr1-2017-01-03"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1686. </li>
  1687. </ol>
  1688. </div>
  1692.    ]]></content>
  1693.  <title>★ On Chuq Von Rospach’s ‘Apple’s 2016 in Review’, and the AirPort and Mac Pro Lineups in Particular</title></entry><entry>
  1695.    <link rel="alternate" type="text/html" href="" />
  1696. <link rel="shorturl" href="" />
  1697. <id>,2017://1.33252</id>
  1698. <published>2017-01-03T03:05:00Z</published>
  1699. <updated>2017-01-04T05:10:31Z</updated>
  1700. <author>
  1701. <name>John Gruber</name>
  1702. <uri></uri>
  1703. </author>
  1704. <summary type="html"><![CDATA[<p>In this book, Craig tells us not just <em>what</em> to do, but <em>why</em>.</p>
  1705. ]]></summary>
  1706. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1707. <p>When I was an incoming freshman at Drexel University in 1991, the school had a program, in collaboration with Apple, that allowed students to buy Macintosh computers at a significant discount. I had narrowed my choices to two: a Mac LC and a Mac SE/30. The SE/30 was significantly faster. But I wound up choosing the LC for one reason: the LC came with a color display, and the SE/30&#8217;s display was black and white. Even today, I love the original Mac&#8217;s 9-inch black and white display, but even then, just seven years after the Mac debuted, that love was nostalgic.</p>
  1709. <p>A color display was, for me, an irresistible draw.</p>
  1711. <p>The display on that Mac LC now sounds quaint. It measured only 12 inches diagonally (common for notebooks today, but the LC was a desktop), with 512 × 384 pixel resolution. A retina display it was not. And it could only display 256 colors at a time. Today that sounds ludicrous. In 1991 it sounded luxurious &#8212; most Macs were black-and-white and many PCs with color support could only show 16 colors at a time. Macs that could display &#8220;thousands&#8221; of colors cost thousands of dollars more.<sup id="fnr1-2017-01-02"><a href="#fn1-2017-01-02">1</a></sup></p>
  1713. <p>For a while, I was obsessed with <a href="">a Mac golfing game</a>. (Exciting, right?) As a computer nerd and budding designer, I noticed immediately that the game&#8217;s graphics seemed too good to be true &#8212; the scenery on the golf courses was clearly better looking than what was possible with the system&#8217;s 256 color palette. I delved into it and learned that while my LC indeed could not display more than 256 colors at a time, the OS provided APIs that allowed an app to specify <em>which</em> 256 colors to display.<sup id="fnr2-2017-01-02"><a href="#fn2-2017-01-02">2</a></sup> The golf game, for obvious reasons, used a custom palette with way more greens than the system&#8217;s standard palette. &#8220;That&#8217;s clever&#8221;, I remember thinking. I also remember thinking that 256 colors no longer seemed like &#8220;a lot&#8221;.</p>
  1715. <p>A few years later, after I&#8217;d immersed myself in the online indie Mac developer/power user community, I became aware of a design studio that specialized in a delightfully specific niche: software icons. Their name said it all: <a href="">The Iconfactory</a>. Soon, The Iconfactory started making their own apps, too, the user interfaces for which were just as exquisitely pixel-perfect as their icons. The Iconfactory&#8217;s developer was a very tall fellow named Craig Hockenberry.</p>
  1717. <hr />
  1719. <p>Craig&#8217;s long been a good friend. So, when he asked me last year if I&#8217;d consider writing the foreword to a book he was writing about color management, I was honored.</p>
  1721. <p><em><a href="">Making Sense of Color Management</a></em> came out last month. It is an excellent book &#8212; useful for both designers and developers who are trying to, well, make sense of the state of the art in color management. Here&#8217;s an example. You specify a certain exact RGB color in your CSS for a web page. Then you make a graphic for that web page, with the exact same RGB value for the background color. But when you put the graphic on the web page, the background colors don&#8217;t match up. But only in some browsers, on some platforms. What the hell is going on?</p>
  1723. <p>In this book, Craig tells us not just <em>what</em> to do, but <em>why</em>. It&#8217;s not merely a checklist of steps to follow blindly, but rather a foundation of knowledge. The famed physicist Richard Feynman believed that if he couldn&#8217;t explain a complex subject to an audience of first-year students, that meant he himself didn&#8217;t truly understand the subject. This book is proof that Craig now truly understands how modern color management works.</p>
  1725. <p>A few salient facts:</p>
  1727. <ul>
  1728. <li>It&#8217;s an e-book, and it costs only $8.</li>
  1729. <li>You can read it in iBooks, Kindle, and as a PDF. You only have to buy it once.</li>
  1730. <li>It&#8217;s only 91 pages long. It contains everything you need to know, and nothing you don&#8217;t.</li>
  1731. <li>It&#8217;s published by A Book Apart, so unsurprisingly it&#8217;s well-edited and exquisitely-designed.</li>
  1732. </ul>
  1734. <p>Color graphics have <em>never</em> been easy. As our technical capabilities have expanded (e.g. wide color gamut displays), so has the complexity involved in understanding how it all works. If you work in design or graphics, you should read this book.</p>
  1736. <p><strong>See also:</strong> Craig&#8217;s blog post <a href="">announcing the publication</a> of the book, and <a href="">the mini-site he created to accompany it</a>. Last but not least, Craig and I discussed the book <a href="">a few weeks ago on my podcast</a>.</p>
  1738. <div class="footnotes">
  1739. <hr />
  1740. <ol>
  1741. <li id="fn1-2017-01-02">
  1742. <p>Back in the System 7 era of the 1990s, you could change the number of colors used by your display in the Monitors control panel. There were options like &#8220;Black and White&#8221; and numbers like 4, 16, and 256. After that, though, <a href="">the system&#8217;s actual labels for how many colors to display were &#8220;Thousands&#8221; and &#8220;Millions&#8221;</a>. It&#8217;s one of those little details that made me love the Mac. 256 is a manageable number. 65,536 is not.</p>
  1744. <p>This preference for humane descriptions over technical descriptions lives on today in MacOS 10.12 Sierra&#8217;s Displays System Preferences panel. You can&#8217;t change the number of colors, but you can change the scale of the interface. If you have a retina display, rather than a list of pixel resolutions (e.g. 2560 × 1440), <a href="">you simply see five</a> side-by-side example icons, with &#8220;Larger Text&#8221; on the left, &#8220;More Space&#8221; on the right, and &#8220;Default&#8221; <a href="">somewhere in between</a>.&nbsp;<a href="#fnr1-2017-01-02"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  1745. </li>
  1747. <li id="fn2-2017-01-02">
  1748. <p>I even remember the 4-character code for the resource type that specified the custom color palettes: &#8220;clut&#8221;, for &#8220;color look up table&#8221;. I don&#8217;t think there&#8217;s any classic Mac app that I have stronger nostalgia for than ResEdit. I probably haven&#8217;t used ResEdit in 15 years, but I feel like I could sit down in front of it and be right at home.&nbsp;<a href="#fnr2-2017-01-02"  class="footnoteBackLink"  title="Jump back to footnote 2 in the text.">&#x21A9;&#xFE0E;</a></p>
  1749. </li>
  1750. </ol>
  1751. </div>
  1755.    ]]></content>
  1756.  <title>★ Craig Hockenberry’s ‘Making Sense of Color Management’</title></entry><entry>
  1758.    <link rel="alternate" type="text/html" href="" />
  1759. <link rel="shorturl" href="" />
  1760. <id>,2016://1.33209</id>
  1761. <published>2016-12-19T23:03:18Z</published>
  1762. <updated>2016-12-19T23:03:47Z</updated>
  1763. <author>
  1764. <name>John Gruber</name>
  1765. <uri></uri>
  1766. </author>
  1767. <summary type="html"><![CDATA[<p>I don&#8217;t trust Uber. But we can collectively verify that in this case, they&#8217;re doing exactly what they say they&#8217;re doing.</p>
  1768. ]]></summary>
  1769. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1770. <p>Uber&#8217;s iOS app <a href="">recently changed</a> its location-tracking from &#8220;When using the app&#8221; to &#8220;Always&#8221;. The company says they&#8217;re only doing it for five minutes after a ride ends, to see where passengers go. They&#8217;re trying to improve the accuracy of where passengers get dropped off.</p>
  1772. <p><a href="">Michael S. Fischer is alarmed by this</a>:</p>
  1774. <blockquote>
  1775.  <p>As you know, iOS allows users to control how apps can access the
  1776. user’s location. There are three choices: “Always,” “When using
  1777. the app,” or “Never.” These are reasonable options. Some users
  1778. might never want an app to have access to their location. Others
  1779. might have a strong trust relationship with the app and its
  1780. authors and allow the app always to track them.</p>
  1782. <p>Most of us, though, fall into the middle camp: We want to allow
  1783. apps to use our location for the purpose of providing a service,
  1784. but want to control our privacy when the app or its authors cease
  1785. doing business with us. So what we’re asking is simple:</p>
  1787. <p><em>Don’t allow app developers to disable the “when using the app”
  1788. Location privacy option.</em></p>
  1790. <p>It’s simply unnecessary for Uber or others to track us when the
  1791. app isn’t in use. How do we know this? <em>Because these apps worked
  1792. adequately before they disabled this option.</em> We were able to meet
  1793. our drivers by opening the app, finding our location, and hailing
  1794. a driver. We gave them enough information to get the job done, and
  1795. we were satisfied with the results.</p>
  1796. </blockquote>
  1798. <p>Few people are more skeptical about Uber than I am. Just last week <a href="">I linked to</a> a <a href="">scathing report on Uber&#8217;s internal privacy problems</a>.</p>
  1800. <p>iOS does not give users the fine-grained control over apps&#8217; location-tracking privileges that Fischer is asking for, but it does give us a way to verify that Uber is only using its &#8220;Always&#8221; privilege the way it claims to be &#8212; for five minutes after a ride ends.</p>
  1802. <p>Go to Settings → Privacy → Location Services and take a look at the list of apps. If Uber has checked your location recently, an indicator will appear in the list &#8212; purple if it checked &#8220;recently&#8221;, gray if in the last 24 hours. I&#8217;ve been checking this every few days ever since Uber changed its location-checking privilege, and it has never once shown any sign of misuse.</p>
  1804. <p>I don&#8217;t trust Uber. But we can collectively verify that in this case, they&#8217;re doing exactly what they say they&#8217;re doing.</p>
  1808.    ]]></content>
  1809.  <title>★ Regarding Uber’s New ‘Always’ Location Tracking</title></entry><entry>
  1811.    <link rel="alternate" type="text/html" href="" />
  1812. <link rel="shorturl" href="" />
  1813. <id>,2016://1.33117</id>
  1814. <published>2016-11-22T20:54:23Z</published>
  1815. <updated>2016-11-24T15:58:50Z</updated>
  1816. <author>
  1817. <name>John Gruber</name>
  1818. <uri></uri>
  1819. </author>
  1820. <summary type="html"><![CDATA[<p>I see why some people think <em>Designed by Apple in California</em> could be Ive&#8217;s goodbye to Apple. But it feels to me like Ive&#8217;s heartfelt goodbye to his best friend and colleague, five years gone. I don&#8217;t think Jony Ive is going anywhere.</p>
  1821. ]]></summary>
  1822. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1823. <p><a href="">Abdel Ibrahim, writing for AppAdvice</a>:</p>
  1825. <blockquote>
  1826.  <p>In the <a href="">latest episode of The Talk Show</a>, John Gruber
  1827. discusses with Six Colors founder, Jason Snell, about Jony Ive’s
  1828. role in the company and how it’s changed in the years since Steve
  1829. Jobs’ passing. He specifically makes mention that he’s heard that
  1830. Ive’s role has changed in a way where he’s not as much involved in
  1831. the design of physical hardware as he used to be.</p>
  1833. <blockquote>
  1834.  <p>I’ve heard that he has lately been checked out or not as directly
  1835. involved with product design and that he’s been largely focused on
  1836. architecture, meaning the spaceship campus and the new stores. And
  1837. that maybe the other top-level executive who’s been working the
  1838. most with Ive is Angela Arhendts.</p>
  1839. </blockquote>
  1841. <p>The comment comes on the back of Apple releasing a photo book
  1842. called “Designed by Apple in California” in which the company
  1843. looks back the last 20 years of products made under Ive and his
  1844. design team. Many Apple fans see the book as part of Ive’s slow
  1845. retirement from Apple, some who believe that Ive has been on his
  1846. way out for a while now.</p>
  1847. </blockquote>
  1849. <p>This is what I dislike most about podcasting. With everything I <em>write</em> here at DF, I aim for painstaking precision in my choice of words and phrasing. I try not only to make it easy for my meaning to be understood, but also difficult to be misconstrued. On a podcast, that&#8217;s not possible. I have no doubt Ibrahim transcribed my words accurately, but the above excerpt is <em>not</em> an accurate representation of what I tried to convey. I think if you listen to <a href="">that part of the show</a>, the surrounding context makes that clear.</p>
  1851. <p>There are definitely people who think Ive might be on his way out. There&#8217;s been speculation to that effect ever since <a href="">his promotion last year to chief design officer</a> and the coinciding promotions of Alan Dye and Richard Howarth to vice presidents of user interface design and industrial design, respectively. The company line is that this new arrangement allows Ive to spend less time on management, and more time directly on, well, design. The skeptic&#8217;s take is that this new arrangement allows Ive to be less involved, period, and that the chief design officer title is almost ceremonial.</p>
  1853. <p>Ive has also always been a bit of a mystery man at Apple. There aren&#8217;t many people who work with him directly, and those few who do, don&#8217;t talk about it. Almost everything I&#8217;ve heard about Ive&#8217;s current role is second or third-hand. Nobody has said to me &#8220;<em>Jony Ive has checked out of day-to-day product design.</em>&#8221; What I have heard is from people who&#8217;ve said &#8220;<em>I think Jony Ive has checked out of day-to-day product design.</em>&#8221; There is a big difference between those two sentences. The first implies direct knowledge. The second is speculation. That&#8217;s what I tried to convey on The Talk Show last week.</p>
  1855. <p>Importantly, I&#8217;ve also heard from well-placed sources within Apple that there is nothing to this &#8212; that while Ive is devoting much of his time and attention to architecture recently (both for the new campus and Apple retail), every aspect of every new product remains as much under his watchful eye as ever. That his chief design officer title isn&#8217;t the least bit ceremonial, and instead is an accurate representation of his <em>increased</em> authority.<sup id="fnr1-2016-11-22"><a href="#fn1-2016-11-22">1</a></sup> Some of this I&#8217;d heard a while back. Some of this I&#8217;ve heard just in the last few days, in the wake of last week&#8217;s episode of the show and the <a href="">ensuing misconstruing of my remarks</a>.<sup id="fnr2-2016-11-22"><a href="#fn2-2016-11-22">2</a></sup></p>
  1857. <p>The <em>Designed by Apple in California</em> book is fascinating in this regard. It lets you see what you want to see. <a href="">Steven Troughton-Smith expressed the &#8220;this is Ive&#8217;s swan song&#8221; side succinctly</a>:</p>
  1859. <blockquote>
  1860.  <p>That it&#8217;s only the last 20 years says a lot &#8212; this is Ive&#8217;s
  1861. portfolio, not Apple&#8217;s. My impression is that his career is
  1862. drawing to a close.</p>
  1863. </blockquote>
  1865. <p>I&#8217;ll argue the other side: the existence of this book &#8212; not just what the book is about, but the extraordinary effort that went into creating and printing it &#8212; is evidence that Jony Ive is wholly in charge of product at Apple. Perhaps every bit as much as Steve Jobs was. If Jony Ive wants to make a $300 book of super-high-end product photography, Apple makes that book. (See also: last year&#8217;s $20,000 gold Apple Watches.)</p>
  1867. <p>Maybe it&#8217;s just wishful thinking on my part, because I don&#8217;t want Ive to leave Apple. Confirmation bias can lead one to see what one wants to see. But if I had to bet, I&#8217;d bet he&#8217;s not going anywhere. Fundamentally I think Jony Ive loves Apple, feels a responsibility to the legacy of his collaboration with Steve Jobs, and that whatever aspirations he has for the remainder of his career, personally, they&#8217;re only possible at Apple. I think if you want to argue that Ive is one step out the door at Apple, you also have to argue that he&#8217;s one step out the door of being a designer. That doesn&#8217;t sound right to me.</p>
  1869. <p>I see why some people think <em>Designed by Apple in California</em> could be Ive&#8217;s goodbye to Apple. But it feels to me like Ive&#8217;s heartfelt goodbye to his best friend and colleague, five years gone. I don&#8217;t think Jony Ive is going anywhere.</p>
  1871. <div class="footnotes">
  1872. <hr />
  1873. <ol>
  1874. <li id="fn1-2016-11-22">
  1875. <p>I think if Jony Ive <em>were</em> to be slowly extricating himself from Apple, he could get a ceremonial title, but a C-level corporate officer doesn&#8217;t sound ceremonial at all. It would be irresponsible for a publicly-held corporation to claim to have a C-level executive who didn&#8217;t actually have C-level responsibilities &#8212; and Tim Cook is most certainly not an irresponsible man. It has never made sense to me that so many people took Ive&#8217;s promotion to chief design officer as a sign that he&#8217;s on the way out. Corporate governance is serious business, and the fact that Tim Cook would not play fast and loose with it is reason to take it at face value.&nbsp;<a href="#fnr1-2016-11-22"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1876. </li>
  1877. <li id="fn2-2016-11-22">
  1878. <p>When I first started seeing these &#8220;Gruber thinks Jony Ive is on his way out&#8221; stories, I was appalled. It felt like a punch to the gut, because it wasn&#8217;t what I meant to convey, and I realize how influential my word is in such regards. But perhaps it was worth it. It shook a few well-placed little birdies out of the tree, all of whom emphasized that Jony Ive is as connected to product design as ever.&nbsp;<a href="#fnr2-2016-11-22"  class="footnoteBackLink"  title="Jump back to footnote 2 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  1879. </li>
  1881. </ol>
  1882. </div>
  1886.    ]]></content>
  1887.  <title>★ On Jony Ive’s Role at Apple</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