Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

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

Source: http://mjtsai.com/blog/comments/feed/

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:dc="http://purl.org/dc/elements/1.1/"
  4. xmlns:atom="http://www.w3.org/2005/Atom"
  5. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  6. >
  7. <channel>
  8. <title>
  9. Comments for Michael Tsai </title>
  10. <atom:link href="https://mjtsai.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
  11. <link>https://mjtsai.com/blog</link>
  12. <description></description>
  13. <lastBuildDate>Thu, 28 Mar 2024 20:56:08 +0000</lastBuildDate>
  14. <sy:updatePeriod>
  15. hourly </sy:updatePeriod>
  16. <sy:updateFrequency>
  17. 1 </sy:updateFrequency>
  18. <generator>https://wordpress.org/?v=6.2.2</generator>
  19. <item>
  20. <title>
  21. Comment on Siri Regressions in iOS 17 by Tom Harrington </title>
  22. <link>https://mjtsai.com/blog/2024/03/28/siri-regressions-in-ios-17/#comment-4062485</link>
  23.  
  24. <dc:creator><![CDATA[Tom Harrington]]></dc:creator>
  25. <pubDate>Thu, 28 Mar 2024 20:56:08 +0000</pubDate>
  26. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42667#comment-4062485</guid>
  27.  
  28. <description><![CDATA[Apple&#039;s Siri page still says that &quot;Siri learns what you need&quot; and promises &quot;...learning your preferences and what you might want...&quot;.
  29.  
  30. Every morning at about the same time I make exactly the same request to my HomePod. But it&#039;s hit or miss whether Siri gets it right. I&#039;ve done this for years and Siri still seems to treat every interaction like it&#039;s only just been installed, without considering context or past history. Mostly I use AirPlay with my HomePod because at least then I know I&#039;ll get what I want instead of some random thing based on Siri&#039;s confused garbled understanding.
  31.  
  32. Siri is why I only own one HomePod and why I&#039;m glad it was a gift instead of something I spent money on. Great sound, absolutely awful user interface.]]></description>
  33. <content:encoded><![CDATA[<p>Apple's Siri page still says that "Siri learns what you need" and promises "...learning your preferences and what you might want...".</p>
  34. <p>Every morning at about the same time I make exactly the same request to my HomePod. But it's hit or miss whether Siri gets it right. I've done this for years and Siri still seems to treat every interaction like it's only just been installed, without considering context or past history. Mostly I use AirPlay with my HomePod because at least then I know I'll get what I want instead of some random thing based on Siri's confused garbled understanding.</p>
  35. <p>Siri is why I only own one HomePod and why I'm glad it was a gift instead of something I spent money on. Great sound, absolutely awful user interface.</p>
  36. ]]></content:encoded>
  37. </item>
  38. <item>
  39. <title>
  40. Comment on Giving Up on Siri and HomePod by DJ </title>
  41. <link>https://mjtsai.com/blog/2024/03/28/giving-up-on-siri-and-homepod/#comment-4062476</link>
  42.  
  43. <dc:creator><![CDATA[DJ]]></dc:creator>
  44. <pubDate>Thu, 28 Mar 2024 20:35:59 +0000</pubDate>
  45. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42669#comment-4062476</guid>
  46.  
  47. <description><![CDATA[I&#039;ve had some troubles with Siri understanding some things, especially with trying to navigate my music library.  Sometimes it fails even when I&#039;m very exact with what I want to play, but generalities work fine (&quot;Siri, play some Killers&quot;).  Outside of music, I really don&#039;t use Siri as much as I thought I would.
  48.  
  49. But as for giving up on it, I feel like now is the wrong time to be making that decision.  Rumors have it that Siri is going to get a major update at WWDC, so if I was considering abandoning it, I would at least wait to see what the summer brings.]]></description>
  50. <content:encoded><![CDATA[<p>I've had some troubles with Siri understanding some things, especially with trying to navigate my music library.  Sometimes it fails even when I'm very exact with what I want to play, but generalities work fine ("Siri, play some Killers").  Outside of music, I really don't use Siri as much as I thought I would.</p>
  51. <p>But as for giving up on it, I feel like now is the wrong time to be making that decision.  Rumors have it that Siri is going to get a major update at WWDC, so if I was considering abandoning it, I would at least wait to see what the summer brings.</p>
  52. ]]></content:encoded>
  53. </item>
  54. <item>
  55. <title>
  56. Comment on Siri Regressions in iOS 17 by Nigel </title>
  57. <link>https://mjtsai.com/blog/2024/03/28/siri-regressions-in-ios-17/#comment-4062463</link>
  58.  
  59. <dc:creator><![CDATA[Nigel]]></dc:creator>
  60. <pubDate>Thu, 28 Mar 2024 20:07:46 +0000</pubDate>
  61. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42667#comment-4062463</guid>
  62.  
  63. <description><![CDATA[New issue for me since 17.4:
  64.  
  65. Me: hey siri, add x to my groceries list
  66. Siri: sure, which list? “Groceries” or “Groceries”
  67.  
  68. I only have one Reminders list called Groceries ¯\_(ツ)_/¯
  69.  
  70. Also, I typically say “add x to my grocery list”. For years Siri was smart enough to resolve “grocery“ to “groceries”. But in the last couple years, with seemingly alternating minor releases of iOS, she loses this ability and simply says “I can’t find a ‘grocery’ list”.
  71.  
  72. I hope the current breakages are a sign that the whole siri team is no longer applying band aids and instead is working furiously on a massive update to debut with iOS 18.]]></description>
  73. <content:encoded><![CDATA[<p>New issue for me since 17.4:</p>
  74. <p>Me: hey siri, add x to my groceries list<br />
  75. Siri: sure, which list? “Groceries” or “Groceries”</p>
  76. <p>I only have one Reminders list called Groceries ¯\_(ツ)_/¯</p>
  77. <p>Also, I typically say “add x to my grocery list”. For years Siri was smart enough to resolve “grocery“ to “groceries”. But in the last couple years, with seemingly alternating minor releases of iOS, she loses this ability and simply says “I can’t find a ‘grocery’ list”.</p>
  78. <p>I hope the current breakages are a sign that the whole siri team is no longer applying band aids and instead is working furiously on a massive update to debut with iOS 18.</p>
  79. ]]></content:encoded>
  80. </item>
  81. <item>
  82. <title>
  83. Comment on Siri Regressions in iOS 17 by Mac Folklore Radio </title>
  84. <link>https://mjtsai.com/blog/2024/03/28/siri-regressions-in-ios-17/#comment-4062455</link>
  85.  
  86. <dc:creator><![CDATA[Mac Folklore Radio]]></dc:creator>
  87. <pubDate>Thu, 28 Mar 2024 19:48:15 +0000</pubDate>
  88. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42667#comment-4062455</guid>
  89.  
  90. <description><![CDATA[Oops, forgot to say I&#039;m still running iOS 15. I regret upgrading from 14; 15 is significantly less responsive on my iPhone 8.]]></description>
  91. <content:encoded><![CDATA[<p>Oops, forgot to say I'm still running iOS 15. I regret upgrading from 14; 15 is significantly less responsive on my iPhone 8.</p>
  92. ]]></content:encoded>
  93. </item>
  94. <item>
  95. <title>
  96. Comment on Siri Regressions in iOS 17 by NaOH </title>
  97. <link>https://mjtsai.com/blog/2024/03/28/siri-regressions-in-ios-17/#comment-4062453</link>
  98.  
  99. <dc:creator><![CDATA[NaOH]]></dc:creator>
  100. <pubDate>Thu, 28 Mar 2024 19:47:24 +0000</pubDate>
  101. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42667#comment-4062453</guid>
  102.  
  103. <description><![CDATA[I probably use Siri about 100 times per week, but only for two tasks: timers and calculations. For timers, I just say the time I want. So, I’ll say “Ten minutes” instead of “Set a timer for ten minutes.”
  104.  
  105. For calculations, there’s a random issue I get. I’ll say, “3-6-1-3 minus 2-8-7,” and Siri will periodically (twice a week?) respond, “Call 361-3287?” instead of replying, &quot;3,326.&quot; I have a grammatical mental block which keeps me from saying, “3-6-1-3 subtract 2-8-7,” and I haven’t been able to deduce if there&#039;s something causing the periodic, unwanted Siri response.]]></description>
  106. <content:encoded><![CDATA[<p>I probably use Siri about 100 times per week, but only for two tasks: timers and calculations. For timers, I just say the time I want. So, I’ll say “Ten minutes” instead of “Set a timer for ten minutes.” </p>
  107. <p>For calculations, there’s a random issue I get. I’ll say, “3-6-1-3 minus 2-8-7,” and Siri will periodically (twice a week?) respond, “Call 361-3287?” instead of replying, "3,326." I have a grammatical mental block which keeps me from saying, “3-6-1-3 subtract 2-8-7,” and I haven’t been able to deduce if there's something causing the periodic, unwanted Siri response.</p>
  108. ]]></content:encoded>
  109. </item>
  110. <item>
  111. <title>
  112. Comment on Siri Regressions in iOS 17 by ProfessorPlasma </title>
  113. <link>https://mjtsai.com/blog/2024/03/28/siri-regressions-in-ios-17/#comment-4062451</link>
  114.  
  115. <dc:creator><![CDATA[ProfessorPlasma]]></dc:creator>
  116. <pubDate>Thu, 28 Mar 2024 19:45:50 +0000</pubDate>
  117. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42667#comment-4062451</guid>
  118.  
  119. <description><![CDATA[I find siri to be triggered much less reliably now that &quot;Hey Siri&quot; is optional. I still say it most of the time but whereas before it triggered every time now it is much more hit and miss. I&#039;ve also experienced the issues mentioned about the alarm and timer. The purported benefit of Siri over Alexa was that it was supposed to handle less structured commands, but really it is more confusing since I never know what phrases Siri will understand and which ones are unknown.]]></description>
  120. <content:encoded><![CDATA[<p>I find siri to be triggered much less reliably now that "Hey Siri" is optional. I still say it most of the time but whereas before it triggered every time now it is much more hit and miss. I've also experienced the issues mentioned about the alarm and timer. The purported benefit of Siri over Alexa was that it was supposed to handle less structured commands, but really it is more confusing since I never know what phrases Siri will understand and which ones are unknown.</p>
  121. ]]></content:encoded>
  122. </item>
  123. <item>
  124. <title>
  125. Comment on Siri Regressions in iOS 17 by Ben G </title>
  126. <link>https://mjtsai.com/blog/2024/03/28/siri-regressions-in-ios-17/#comment-4062449</link>
  127.  
  128. <dc:creator><![CDATA[Ben G]]></dc:creator>
  129. <pubDate>Thu, 28 Mar 2024 19:44:59 +0000</pubDate>
  130. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42667#comment-4062449</guid>
  131.  
  132. <description><![CDATA[“Sometimes it will show on screen exactly what I said but not actually do anything.“
  133.  
  134. I emailed Siri lead engineer Alex Acero about this bug 8 years ago, and he replied and pawned if off to someone else to look into. It’s amazing that it’s still not fixed.
  135.  
  136. In my experience, Siri only works about 75% of the time at best. It misunderstands, or just can’t complete, even the most simple tasks like “Wake me up at 7:15am” sometimes. Forget using it with Apple Music, in that case it spits out garbage more than 90% of the time.
  137.  
  138. It really feels like Siri has made zero progress over the past decade in the ways that matter for everyday tasks.]]></description>
  139. <content:encoded><![CDATA[<p>“Sometimes it will show on screen exactly what I said but not actually do anything.“</p>
  140. <p>I emailed Siri lead engineer Alex Acero about this bug 8 years ago, and he replied and pawned if off to someone else to look into. It’s amazing that it’s still not fixed.</p>
  141. <p>In my experience, Siri only works about 75% of the time at best. It misunderstands, or just can’t complete, even the most simple tasks like “Wake me up at 7:15am” sometimes. Forget using it with Apple Music, in that case it spits out garbage more than 90% of the time.</p>
  142. <p>It really feels like Siri has made zero progress over the past decade in the ways that matter for everyday tasks.</p>
  143. ]]></content:encoded>
  144. </item>
  145. <item>
  146. <title>
  147. Comment on Siri Regressions in iOS 17 by Ben Kennedy </title>
  148. <link>https://mjtsai.com/blog/2024/03/28/siri-regressions-in-ios-17/#comment-4062448</link>
  149.  
  150. <dc:creator><![CDATA[Ben Kennedy]]></dc:creator>
  151. <pubDate>Thu, 28 Mar 2024 19:43:57 +0000</pubDate>
  152. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42667#comment-4062448</guid>
  153.  
  154. <description><![CDATA[I use the “remind me to X” command every so often and it almost always understands that I want to create a reminder. However, the follow-through is so unreliable that I always manually check the output on my phone so that I can be sure it actually worked, and then correct the inevitable transcription or timing mistakes it has made. The productivity gain from using Siri to create the reminder is typically a wash.
  155.  
  156. I have a habit of listening to the radio (well, streaming) in the shower each morning, which requires a high volume level to be audible. Since I immediately want to turn it down when I shut off the water, I created an automation that adjusts the volume, called “pipe down”. However, I can never get it to work properly on the first or second attempt: saying “hey Siri, pipe down” invokes the Siri animation, but nothing happens, and after a few seconds it goes dark again. In fact, more often than not, my HomePod Mini in the kitchen will begin playing music at a loud volume instead! (After several such intrusions all I could guess was that &quot;pipe down&quot; was being routinely interpreted as &quot;play music&quot;.) Instead, for my command to work, I have discovered that I need to say &quot;hey Siri” and pause for a few seconds, say “hey Siri” and pause for a few seconds again, say “hey Siri” and pause yet again, THEN say “pipe down”. This works most of the time. And it&#039;s ridiculous.
  157.  
  158. The spurious comma problem has been an issue for awhile. I filed FB11605023 in September 2022 (“iOS 16: voice-to-text dictation has a propensity for inserting spurious punctuation”); to no-one&#039;s surprise, it remains open and unacknowledged.]]></description>
  159. <content:encoded><![CDATA[<p>I use the “remind me to X” command every so often and it almost always understands that I want to create a reminder. However, the follow-through is so unreliable that I always manually check the output on my phone so that I can be sure it actually worked, and then correct the inevitable transcription or timing mistakes it has made. The productivity gain from using Siri to create the reminder is typically a wash.</p>
  160. <p>I have a habit of listening to the radio (well, streaming) in the shower each morning, which requires a high volume level to be audible. Since I immediately want to turn it down when I shut off the water, I created an automation that adjusts the volume, called “pipe down”. However, I can never get it to work properly on the first or second attempt: saying “hey Siri, pipe down” invokes the Siri animation, but nothing happens, and after a few seconds it goes dark again. In fact, more often than not, my HomePod Mini in the kitchen will begin playing music at a loud volume instead! (After several such intrusions all I could guess was that "pipe down" was being routinely interpreted as "play music".) Instead, for my command to work, I have discovered that I need to say "hey Siri” and pause for a few seconds, say “hey Siri” and pause for a few seconds again, say “hey Siri” and pause yet again, THEN say “pipe down”. This works most of the time. And it's ridiculous.</p>
  161. <p>The spurious comma problem has been an issue for awhile. I filed FB11605023 in September 2022 (“iOS 16: voice-to-text dictation has a propensity for inserting spurious punctuation”); to no-one's surprise, it remains open and unacknowledged.</p>
  162. ]]></content:encoded>
  163. </item>
  164. <item>
  165. <title>
  166. Comment on Siri Regressions in iOS 17 by Mac Folklore Radio </title>
  167. <link>https://mjtsai.com/blog/2024/03/28/siri-regressions-in-ios-17/#comment-4062444</link>
  168.  
  169. <dc:creator><![CDATA[Mac Folklore Radio]]></dc:creator>
  170. <pubDate>Thu, 28 Mar 2024 19:37:20 +0000</pubDate>
  171. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42667#comment-4062444</guid>
  172.  
  173. <description><![CDATA[I only used Siri for setting timers, and if I was really busy, for making short notes.
  174.  
  175. Over the past six months a new pattern has emerged. I&#039;ll say, &quot;Hey Siri, make a note: blargle the flab tomorrow&quot;. Now about 60% of the time this yields an on-screen error _showing that Siri head everything perfectly but refused to do anything_.
  176.  
  177. The error reads, &quot;Sorry, I didn&#039;t quote catch that: make a note blargle the flab tomorrow&quot;. Yes, with the full text of what I said on the screen. What.....?
  178.  
  179. So now I only use Siri to set timers. iOS: the &#062;=2010s Mac OS quality assurance disaster experience in your pocket.]]></description>
  180. <content:encoded><![CDATA[<p>I only used Siri for setting timers, and if I was really busy, for making short notes.</p>
  181. <p>Over the past six months a new pattern has emerged. I'll say, "Hey Siri, make a note: blargle the flab tomorrow". Now about 60% of the time this yields an on-screen error _showing that Siri head everything perfectly but refused to do anything_. </p>
  182. <p>The error reads, "Sorry, I didn't quote catch that: make a note blargle the flab tomorrow". Yes, with the full text of what I said on the screen. What.....?</p>
  183. <p>So now I only use Siri to set timers. iOS: the &gt;=2010s Mac OS quality assurance disaster experience in your pocket.</p>
  184. ]]></content:encoded>
  185. </item>
  186. <item>
  187. <title>
  188. Comment on Siri Regressions in iOS 17 by Anonymous </title>
  189. <link>https://mjtsai.com/blog/2024/03/28/siri-regressions-in-ios-17/#comment-4062441</link>
  190.  
  191. <dc:creator><![CDATA[Anonymous]]></dc:creator>
  192. <pubDate>Thu, 28 Mar 2024 19:34:33 +0000</pubDate>
  193. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42667#comment-4062441</guid>
  194.  
  195. <description><![CDATA[I think I&#039;ve reduced Siri usage to two tasks: timers and math calculations. For timers I simply say the amount of time I want, nothing else. So, &quot;Ten minutes&quot; instead of &quot;Set a timer for ten minutes.&quot; The issue I randomly face, and it pre-dates iOS 17, is calculations, whereby saying, &quot;3-6-7-7 minus 4-8-3&quot; leads to an offer to call 367-7483. I haven&#039;t been able to deduce a pattern behind when Siri interprets my request as a desire to make a call, and I do calculations like this a few dozen times per week. Meanwhile, I have a grammatical problem getting my head to say, &quot;3-6-7-7 subtract 4-8-3.&quot;]]></description>
  196. <content:encoded><![CDATA[<p>I think I've reduced Siri usage to two tasks: timers and math calculations. For timers I simply say the amount of time I want, nothing else. So, "Ten minutes" instead of "Set a timer for ten minutes." The issue I randomly face, and it pre-dates iOS 17, is calculations, whereby saying, "3-6-7-7 minus 4-8-3" leads to an offer to call 367-7483. I haven't been able to deduce a pattern behind when Siri interprets my request as a desire to make a call, and I do calculations like this a few dozen times per week. Meanwhile, I have a grammatical problem getting my head to say, "3-6-7-7 subtract 4-8-3."</p>
  197. ]]></content:encoded>
  198. </item>
  199. <item>
  200. <title>
  201. Comment on Siri Regressions in iOS 17 by John Gordon </title>
  202. <link>https://mjtsai.com/blog/2024/03/28/siri-regressions-in-ios-17/#comment-4062436</link>
  203.  
  204. <dc:creator><![CDATA[John Gordon]]></dc:creator>
  205. <pubDate>Thu, 28 Mar 2024 19:20:08 +0000</pubDate>
  206. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42667#comment-4062436</guid>
  207.  
  208. <description><![CDATA[When I told Siri to &quot;set an alarm in 10 minutes&quot; it used to do exactly that. Now it sets a 10 minute timer.]]></description>
  209. <content:encoded><![CDATA[<p>When I told Siri to "set an alarm in 10 minutes" it used to do exactly that. Now it sets a 10 minute timer.</p>
  210. ]]></content:encoded>
  211. </item>
  212. <item>
  213. <title>
  214. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by Nathan </title>
  215. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4062351</link>
  216.  
  217. <dc:creator><![CDATA[Nathan]]></dc:creator>
  218. <pubDate>Thu, 28 Mar 2024 15:59:20 +0000</pubDate>
  219. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4062351</guid>
  220.  
  221. <description><![CDATA[@DJ Yeah, that tracks in my experience. If a Linux is supported, it&#039;s almost always Ubuntu as one of the options (except apparently that one company).
  222.  
  223. Arch is great, but I don&#039;t know if I&#039;d run a company or large org on it. Bleeding edge and many software packages are not built directly for it, but AUR helps there (but is a bit more wild west). As a rolling distro, it&#039;s constantly updated and a bit more bleeding edge. I believe SteamOS uses Arch now, but Valve can custom build things and support their small set of devices pretty easily.
  224.  
  225. My mom&#039;s household is all Arch now, because I can support it pretty easily, and so is my household, excepting my daughter&#039;s laptop and Surface which both run Windows 10.]]></description>
  226. <content:encoded><![CDATA[<p>@DJ Yeah, that tracks in my experience. If a Linux is supported, it's almost always Ubuntu as one of the options (except apparently that one company).</p>
  227. <p>Arch is great, but I don't know if I'd run a company or large org on it. Bleeding edge and many software packages are not built directly for it, but AUR helps there (but is a bit more wild west). As a rolling distro, it's constantly updated and a bit more bleeding edge. I believe SteamOS uses Arch now, but Valve can custom build things and support their small set of devices pretty easily.</p>
  228. <p>My mom's household is all Arch now, because I can support it pretty easily, and so is my household, excepting my daughter's laptop and Surface which both run Windows 10.</p>
  229. ]]></content:encoded>
  230. </item>
  231. <item>
  232. <title>
  233. Comment on Movie Piracy App Tops App Store Charts by Nathan </title>
  234. <link>https://mjtsai.com/blog/2024/03/26/movie-piracy-app-tops-app-store-charts/#comment-4062344</link>
  235.  
  236. <dc:creator><![CDATA[Nathan]]></dc:creator>
  237. <pubDate>Thu, 28 Mar 2024 15:44:35 +0000</pubDate>
  238. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42646#comment-4062344</guid>
  239.  
  240. <description><![CDATA[@Bri Exactly. The protections are largely a myth and it&#039;s about Apple controlling their cut of the proceeds.]]></description>
  241. <content:encoded><![CDATA[<p>@Bri Exactly. The protections are largely a myth and it's about Apple controlling their cut of the proceeds.</p>
  242. ]]></content:encoded>
  243. </item>
  244. <item>
  245. <title>
  246. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by DJ </title>
  247. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4062260</link>
  248.  
  249. <dc:creator><![CDATA[DJ]]></dc:creator>
  250. <pubDate>Thu, 28 Mar 2024 12:50:30 +0000</pubDate>
  251. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4062260</guid>
  252.  
  253. <description><![CDATA[Ubuntu works well for most things.  For a lot of our users (higher ed), if they have any previous experience with Linux at all, it&#039;s with Ubuntu, so that makes the learning curve a little easier for them, and it&#039;s good for most server-level stuff .  It&#039;s mainstream enough to be well-supported, although we did just run into a company that supports at least a half dozen Linux variants and Ubuntu isn&#039;t one of them.
  254.  
  255. I haven&#039;t tried Arch yet, so I don&#039;t know how it compares.  I&#039;ll have to take a look.]]></description>
  256. <content:encoded><![CDATA[<p>Ubuntu works well for most things.  For a lot of our users (higher ed), if they have any previous experience with Linux at all, it's with Ubuntu, so that makes the learning curve a little easier for them, and it's good for most server-level stuff .  It's mainstream enough to be well-supported, although we did just run into a company that supports at least a half dozen Linux variants and Ubuntu isn't one of them.</p>
  257. <p>I haven't tried Arch yet, so I don't know how it compares.  I'll have to take a look.</p>
  258. ]]></content:encoded>
  259. </item>
  260. <item>
  261. <title>
  262. Comment on DMA Non-Compliance Investigations by Kristoffer </title>
  263. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4062137</link>
  264.  
  265. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  266. <pubDate>Thu, 28 Mar 2024 08:57:12 +0000</pubDate>
  267. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4062137</guid>
  268.  
  269. <description><![CDATA[I agree with DJ that trade laws are ridiculously over reaching. The US global sanctions against any company doing business with China being a good example.]]></description>
  270. <content:encoded><![CDATA[<p>I agree with DJ that trade laws are ridiculously over reaching. The US global sanctions against any company doing business with China being a good example.</p>
  271. ]]></content:encoded>
  272. </item>
  273. <item>
  274. <title>
  275. Comment on Noncopyable Generics Walkthrough by A </title>
  276. <link>https://mjtsai.com/blog/2024/03/27/noncopyable-generics-walkthrough/#comment-4062072</link>
  277.  
  278. <dc:creator><![CDATA[A]]></dc:creator>
  279. <pubDate>Thu, 28 Mar 2024 07:40:32 +0000</pubDate>
  280. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42653#comment-4062072</guid>
  281.  
  282. <description><![CDATA[And the complexity increases yet again , we’re almost surpassing C++.
  283.  
  284. Yet another feature I will never need when building iOS apps. I’m glad the language people are having fun building these things, while the most basic things are forever broken. All I need for making software is a working debugger, a non crashing and FAST compiler, less bugs in everything (regexes are broken, Decimal is broken, etc…) and simplicity.
  285.  
  286. The relative elegance of Objective-C is far away. Seem like the architecture astronauts have won and are more concerned about technical achievements than actually making usable software.]]></description>
  287. <content:encoded><![CDATA[<p>And the complexity increases yet again , we’re almost surpassing C++. </p>
  288. <p>Yet another feature I will never need when building iOS apps. I’m glad the language people are having fun building these things, while the most basic things are forever broken. All I need for making software is a working debugger, a non crashing and FAST compiler, less bugs in everything (regexes are broken, Decimal is broken, etc…) and simplicity. </p>
  289. <p>The relative elegance of Objective-C is far away. Seem like the architecture astronauts have won and are more concerned about technical achievements than actually making usable software.</p>
  290. ]]></content:encoded>
  291. </item>
  292. <item>
  293. <title>
  294. Comment on Glassdoor No Longer Anonymous by Ben </title>
  295. <link>https://mjtsai.com/blog/2024/03/21/glassdoor-no-longer-anonymous/#comment-4061932</link>
  296.  
  297. <dc:creator><![CDATA[Ben]]></dc:creator>
  298. <pubDate>Thu, 28 Mar 2024 02:06:28 +0000</pubDate>
  299. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42588#comment-4061932</guid>
  300.  
  301. <description><![CDATA[In my previous comment, the URL got stripped out: https://www.glassdoor.com/member/profile/settings.htm]]></description>
  302. <content:encoded><![CDATA[<p>In my previous comment, the URL got stripped out: <a href="https://www.glassdoor.com/member/profile/settings.htm" rel="nofollow ugc">https://www.glassdoor.com/member/profile/settings.htm</a></p>
  303. ]]></content:encoded>
  304. </item>
  305. <item>
  306. <title>
  307. Comment on Glassdoor No Longer Anonymous by Ben </title>
  308. <link>https://mjtsai.com/blog/2024/03/21/glassdoor-no-longer-anonymous/#comment-4061931</link>
  309.  
  310. <dc:creator><![CDATA[Ben]]></dc:creator>
  311. <pubDate>Thu, 28 Mar 2024 02:05:55 +0000</pubDate>
  312. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42588#comment-4061931</guid>
  313.  
  314. <description><![CDATA[&#062; I was forced to add at least one job history, write one job review, and enter my salary history…
  315.  
  316. It seems to be possible to bypass this by visiting the user settings page directly at . (I got through the modal prompt by using my browser&#039;s developer tools to remove it and its overlay from the DOM, at which point the settings link was accessible.)]]></description>
  317. <content:encoded><![CDATA[<p>&gt; I was forced to add at least one job history, write one job review, and enter my salary history…</p>
  318. <p>It seems to be possible to bypass this by visiting the user settings page directly at . (I got through the modal prompt by using my browser's developer tools to remove it and its overlay from the DOM, at which point the settings link was accessible.)</p>
  319. ]]></content:encoded>
  320. </item>
  321. <item>
  322. <title>
  323. Comment on 1Password.co Tracking Links by Ben Kennedy </title>
  324. <link>https://mjtsai.com/blog/2024/03/27/1password-co-tracking-links/#comment-4061898</link>
  325.  
  326. <dc:creator><![CDATA[Ben Kennedy]]></dc:creator>
  327. <pubDate>Thu, 28 Mar 2024 00:03:19 +0000</pubDate>
  328. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42655#comment-4061898</guid>
  329.  
  330. <description><![CDATA[I realize that I&#039;m old-school, but I still find it perplexing that reputable companies choose to use Colombian domains for anything at all.]]></description>
  331. <content:encoded><![CDATA[<p>I realize that I'm old-school, but I still find it perplexing that reputable companies choose to use Colombian domains for anything at all.</p>
  332. ]]></content:encoded>
  333. </item>
  334. <item>
  335. <title>
  336. Comment on &#8220;MFA Bombing&#8221; Attacks Targeting Apple Users by Riley </title>
  337. <link>https://mjtsai.com/blog/2024/03/27/mfa-bombing-attacks-targeting-apple-users/#comment-4061855</link>
  338.  
  339. <dc:creator><![CDATA[Riley]]></dc:creator>
  340. <pubDate>Wed, 27 Mar 2024 22:16:46 +0000</pubDate>
  341. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42657#comment-4061855</guid>
  342.  
  343. <description><![CDATA[Certainly the phone call scam would work, but this seems like it&#039;s something entirely different than &quot;accidentally thumbing the wrong button&quot;]]></description>
  344. <content:encoded><![CDATA[<p>Certainly the phone call scam would work, but this seems like it's something entirely different than "accidentally thumbing the wrong button"</p>
  345. ]]></content:encoded>
  346. </item>
  347. <item>
  348. <title>
  349. Comment on &#8220;MFA Bombing&#8221; Attacks Targeting Apple Users by Riley </title>
  350. <link>https://mjtsai.com/blog/2024/03/27/mfa-bombing-attacks-targeting-apple-users/#comment-4061854</link>
  351.  
  352. <dc:creator><![CDATA[Riley]]></dc:creator>
  353. <pubDate>Wed, 27 Mar 2024 22:14:59 +0000</pubDate>
  354. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42657#comment-4061854</guid>
  355.  
  356. <description><![CDATA[I find this odd, since the MFA makes you enter the 6 digit number given. How does MFA bombing work if hitting approve doesn&#039;t actually approve the 2FA? Presumably they would still need to access the physical device somehow.]]></description>
  357. <content:encoded><![CDATA[<p>I find this odd, since the MFA makes you enter the 6 digit number given. How does MFA bombing work if hitting approve doesn't actually approve the 2FA? Presumably they would still need to access the physical device somehow.</p>
  358. ]]></content:encoded>
  359. </item>
  360. <item>
  361. <title>
  362. Comment on DMA Non-Compliance Investigations by someone </title>
  363. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4061839</link>
  364.  
  365. <dc:creator><![CDATA[someone]]></dc:creator>
  366. <pubDate>Wed, 27 Mar 2024 21:32:06 +0000</pubDate>
  367. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4061839</guid>
  368.  
  369. <description><![CDATA[@DJ It may have included Russia before 2022… But I doubt that Apple is selling officially anything in Russia these days. Apart from UK where Apple is historically well implanted, you can remove the other additional countries on the European continent from the list.
  370.  
  371. Apple loves the European market because it has bigger margins than in the USA and Apple is  also fond of the European food, especially the double Irish Dutch sandwich.
  372.  
  373. Ref. https://www.cnbc.com/2024/02/21/two-years-after-apple-quit-russia-over-ukraine-vision-pros-are-for-sale-in-moscow.html]]></description>
  374. <content:encoded><![CDATA[<p>@DJ It may have included Russia before 2022… But I doubt that Apple is selling officially anything in Russia these days. Apart from UK where Apple is historically well implanted, you can remove the other additional countries on the European continent from the list. </p>
  375. <p>Apple loves the European market because it has bigger margins than in the USA and Apple is  also fond of the European food, especially the double Irish Dutch sandwich.</p>
  376. <p>Ref. <a href="https://www.cnbc.com/2024/02/21/two-years-after-apple-quit-russia-over-ukraine-vision-pros-are-for-sale-in-moscow.html" rel="nofollow ugc">https://www.cnbc.com/2024/02/21/two-years-after-apple-quit-russia-over-ukraine-vision-pros-are-for-sale-in-moscow.html</a></p>
  377. ]]></content:encoded>
  378. </item>
  379. <item>
  380. <title>
  381. Comment on DMA Non-Compliance Investigations by DJ </title>
  382. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4061681</link>
  383.  
  384. <dc:creator><![CDATA[DJ]]></dc:creator>
  385. <pubDate>Wed, 27 Mar 2024 16:15:45 +0000</pubDate>
  386. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4061681</guid>
  387.  
  388. <description><![CDATA[I had read somewhere that the &quot;Europe region&quot; includes the EU, UK, Russia, Turkey, Ukraine, etc.]]></description>
  389. <content:encoded><![CDATA[<p>I had read somewhere that the "Europe region" includes the EU, UK, Russia, Turkey, Ukraine, etc.</p>
  390. ]]></content:encoded>
  391. </item>
  392. <item>
  393. <title>
  394. Comment on DMA Non-Compliance Investigations by DanM </title>
  395. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4061660</link>
  396.  
  397. <dc:creator><![CDATA[DanM]]></dc:creator>
  398. <pubDate>Wed, 27 Mar 2024 15:35:20 +0000</pubDate>
  399. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4061660</guid>
  400.  
  401. <description><![CDATA[Apple&#039;s regional revenue split can be easily found on page 24 of the 10K SEC report.
  402.  
  403. Net sales for the Europe region (likely including Switzerland and the UK) were 94.3 billion USD, compared to 383.3 billion total. That&#039;s hardware sales and services combined. European net sales make up a little less than 25% of total net sales.
  404.  
  405. The 7 % figure is from the latest earnings conference call, and it&#039;s the share of services revenue only.]]></description>
  406. <content:encoded><![CDATA[<p>Apple's regional revenue split can be easily found on page 24 of the 10K SEC report.</p>
  407. <p>Net sales for the Europe region (likely including Switzerland and the UK) were 94.3 billion USD, compared to 383.3 billion total. That's hardware sales and services combined. European net sales make up a little less than 25% of total net sales.</p>
  408. <p>The 7 % figure is from the latest earnings conference call, and it's the share of services revenue only.</p>
  409. ]]></content:encoded>
  410. </item>
  411. <item>
  412. <title>
  413. Comment on DMA Non-Compliance Investigations by DJ </title>
  414. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4061647</link>
  415.  
  416. <dc:creator><![CDATA[DJ]]></dc:creator>
  417. <pubDate>Wed, 27 Mar 2024 15:03:54 +0000</pubDate>
  418. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4061647</guid>
  419.  
  420. <description><![CDATA[Yeah, you could be right.  The EU also has a higher population than the US, but a smaller economy.  So I wonder where the revenue numbers really fall?]]></description>
  421. <content:encoded><![CDATA[<p>Yeah, you could be right.  The EU also has a higher population than the US, but a smaller economy.  So I wonder where the revenue numbers really fall?</p>
  422. ]]></content:encoded>
  423. </item>
  424. <item>
  425. <title>
  426. Comment on DMA Non-Compliance Investigations by Old Unix Geek </title>
  427. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4061614</link>
  428.  
  429. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  430. <pubDate>Wed, 27 Mar 2024 14:19:55 +0000</pubDate>
  431. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4061614</guid>
  432.  
  433. <description><![CDATA[@DJ: The EU is the second largest economy in the world after the US and represents 1/6 of the world economy. The US represents 1/4. The EU doesn&#039;t have a national preference the way China does for local champions like Huawei. A higher percentage of Europeans can afford an iPhone than people in countries like India. So I&#039;d expect it to be at least twice, and possibly up to 3x larger.
  434.  
  435. As Kristoffer says, I&#039;d be quite amused if Apple were to leave the EU market particularly since they&#039;re slowly gaining share in Europe. The stockholders would probably be equally amused.]]></description>
  436. <content:encoded><![CDATA[<p>@DJ: The EU is the second largest economy in the world after the US and represents 1/6 of the world economy. The US represents 1/4. The EU doesn't have a national preference the way China does for local champions like Huawei. A higher percentage of Europeans can afford an iPhone than people in countries like India. So I'd expect it to be at least twice, and possibly up to 3x larger.</p>
  437. <p>As Kristoffer says, I'd be quite amused if Apple were to leave the EU market particularly since they're slowly gaining share in Europe. The stockholders would probably be equally amused.</p>
  438. ]]></content:encoded>
  439. </item>
  440. <item>
  441. <title>
  442. Comment on DMA Non-Compliance Investigations by DJ </title>
  443. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4061594</link>
  444.  
  445. <dc:creator><![CDATA[DJ]]></dc:creator>
  446. <pubDate>Wed, 27 Mar 2024 13:50:55 +0000</pubDate>
  447. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4061594</guid>
  448.  
  449. <description><![CDATA[How much bigger than 7% could the EU&#039;s percentage of Apple&#039;s revenue be?  Regardless of the number, you can bet that Apple (and Google, and Meta) have had more than one conversation about pulling out of the EU market.  And should the EU really be able to fine a company based on a percentage of their global revenue?  Seems like that should be limited to their revenue in the EU.  I guess once a fine like that has been levied against one of these companies, the resulting appeal(s) will determine that.]]></description>
  450. <content:encoded><![CDATA[<p>How much bigger than 7% could the EU's percentage of Apple's revenue be?  Regardless of the number, you can bet that Apple (and Google, and Meta) have had more than one conversation about pulling out of the EU market.  And should the EU really be able to fine a company based on a percentage of their global revenue?  Seems like that should be limited to their revenue in the EU.  I guess once a fine like that has been levied against one of these companies, the resulting appeal(s) will determine that.</p>
  451. ]]></content:encoded>
  452. </item>
  453. <item>
  454. <title>
  455. Comment on DMA Non-Compliance Investigations by Kristoffer </title>
  456. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4061574</link>
  457.  
  458. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  459. <pubDate>Wed, 27 Mar 2024 13:19:16 +0000</pubDate>
  460. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4061574</guid>
  461.  
  462. <description><![CDATA[&quot;(none of which are European companies of course)&quot;
  463.  
  464. There are many reasons for that, chief among which is the US lax stance on anti-trust for the last few decades and the creative tax dodging that Apple et al have perfected over the years.
  465.  
  466. It&#039;s one of the spins the anti DMA crowd rely on. &quot;This is targeted at the US&quot;. Read the document and what it says about gatekeepers. Now mentions of nations.]]></description>
  467. <content:encoded><![CDATA[<p>"(none of which are European companies of course)"</p>
  468. <p>There are many reasons for that, chief among which is the US lax stance on anti-trust for the last few decades and the creative tax dodging that Apple et al have perfected over the years.</p>
  469. <p>It's one of the spins the anti DMA crowd rely on. "This is targeted at the US". Read the document and what it says about gatekeepers. Now mentions of nations.</p>
  470. ]]></content:encoded>
  471. </item>
  472. <item>
  473. <title>
  474. Comment on Canva Acquires Affinity/Serif by Kristoffer </title>
  475. <link>https://mjtsai.com/blog/2024/03/26/canva-acquires-affinity-serif/#comment-4061572</link>
  476.  
  477. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  478. <pubDate>Wed, 27 Mar 2024 13:14:47 +0000</pubDate>
  479. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42650#comment-4061572</guid>
  480.  
  481. <description><![CDATA[I&#039;ve never heard of Affinity before, but Canva keeps popping up. So since I have full insight in all of this I can say this is a mistake.
  482.  
  483. Canva are thinking &quot;Aha, we have this simple and cheerful way to create &#039;content&#039; for &#039;social-media&#039; that marketing departments love. Obviously we should start targeting the professional creatives that use full fledged editing software!&quot;
  484.  
  485. They look into what it would cost to create a suite of installables and then they think: &quot;Oh, what&#039;s that? A company that have what we want. Let&#039;s buy them!&quot;
  486.  
  487. Completely disregarding the differences in business model, runtime, users, etc etc.
  488.  
  489. Three years of misery and then this will die.]]></description>
  490. <content:encoded><![CDATA[<p>I've never heard of Affinity before, but Canva keeps popping up. So since I have full insight in all of this I can say this is a mistake. </p>
  491. <p>Canva are thinking "Aha, we have this simple and cheerful way to create 'content' for 'social-media' that marketing departments love. Obviously we should start targeting the professional creatives that use full fledged editing software!"</p>
  492. <p>They look into what it would cost to create a suite of installables and then they think: "Oh, what's that? A company that have what we want. Let's buy them!"</p>
  493. <p>Completely disregarding the differences in business model, runtime, users, etc etc.</p>
  494. <p>Three years of misery and then this will die.</p>
  495. ]]></content:encoded>
  496. </item>
  497. <item>
  498. <title>
  499. Comment on DMA Non-Compliance Investigations by someone </title>
  500. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4061551</link>
  501.  
  502. <dc:creator><![CDATA[someone]]></dc:creator>
  503. <pubDate>Wed, 27 Mar 2024 12:35:10 +0000</pubDate>
  504. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4061551</guid>
  505.  
  506. <description><![CDATA[@Old Unix Geek
  507.  
  508. &#062; &quot;I&#039;d be surprised if the EU was only 7% of Apple&#039;s revenue.&quot;
  509.  
  510. Anyway, why should we believe any number given by a company whose CEO does not even &quot;remember&quot; how many billions Google is paying Apple to be the default search engine in Safari?
  511.  
  512. https://www.theregister.com/2021/05/22/apple_ceo_tim_cook_faces/]]></description>
  513. <content:encoded><![CDATA[<p>@Old Unix Geek</p>
  514. <p>&gt; "I'd be surprised if the EU was only 7% of Apple's revenue."</p>
  515. <p>Anyway, why should we believe any number given by a company whose CEO does not even "remember" how many billions Google is paying Apple to be the default search engine in Safari?</p>
  516. <p><a href="https://www.theregister.com/2021/05/22/apple_ceo_tim_cook_faces/" rel="nofollow ugc">https://www.theregister.com/2021/05/22/apple_ceo_tim_cook_faces/</a></p>
  517. ]]></content:encoded>
  518. </item>
  519. <item>
  520. <title>
  521. Comment on APFS Native Normalization by Happy birthday APFS, 7 years old today </title>
  522. <link>https://mjtsai.com/blog/2017/06/27/apfs-native-normalization/#comment-4061525</link>
  523.  
  524. <dc:creator><![CDATA[Happy birthday APFS, 7 years old today]]></dc:creator>
  525. <pubDate>Wed, 27 Mar 2024 11:30:05 +0000</pubDate>
  526. <guid isPermaLink="false">https://mjtsai.com/blog/?p=18242#comment-4061525</guid>
  527.  
  528. <description><![CDATA[[&#8230;] normalisation; this had to be resolved in later versions of macOS 10.13 and iOS 10, as explained here and [&#8230;]]]></description>
  529. <content:encoded><![CDATA[<p>[&#8230;] normalisation; this had to be resolved in later versions of macOS 10.13 and iOS 10, as explained here and [&#8230;]</p>
  530. ]]></content:encoded>
  531. </item>
  532. <item>
  533. <title>
  534. Comment on DMA Non-Compliance Investigations by Kristoffer </title>
  535. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4061457</link>
  536.  
  537. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  538. <pubDate>Wed, 27 Mar 2024 08:58:42 +0000</pubDate>
  539. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4061457</guid>
  540.  
  541. <description><![CDATA[I would love to see Apple pull out of the EU. It would be really interesting.]]></description>
  542. <content:encoded><![CDATA[<p>I would love to see Apple pull out of the EU. It would be really interesting.</p>
  543. ]]></content:encoded>
  544. </item>
  545. <item>
  546. <title>
  547. Comment on macOS 14.4.1 by foobat </title>
  548. <link>https://mjtsai.com/blog/2024/03/25/macos-14-4-1/#comment-4061367</link>
  549.  
  550. <dc:creator><![CDATA[foobat]]></dc:creator>
  551. <pubDate>Wed, 27 Mar 2024 05:44:27 +0000</pubDate>
  552. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42631#comment-4061367</guid>
  553.  
  554. <description><![CDATA[It&#039;s not you or your gear.
  555.  
  556. The other day, a USB C cable plugged into the front of my Mac Studio fell on the floor and I didn&#039;t notice until my chair was about to roll over it. I picked up the cable and inadvertently tugged on the Studio ever so slightly. The Studio moved like 2mm, which was enough to spontaneously eject all the hard drives on the one USB A cable that moved.
  557.  
  558. It gets worse. When I am going to be away from my Mac for more than an hour, I always lock it with control + command + q. This works great in the daytime—it works exactly how it has always worked since the day that keyboard shortcut was added. However, if my focus mode is on Sleep when I do this, Ventura ejects all external storage, but not by actually ejecting it or unmounting it (to, you know, prevent damage and shit), nope, Ventura cycles the power on all the USB ports (just guessing, it&#039;s not a bug, it&#039;s a feature!) which causes all the external storage to get disconnected suddenly (and I get a notification for every drive accusing me of improper removal, thanks Apple).]]></description>
  559. <content:encoded><![CDATA[<p>It's not you or your gear. </p>
  560. <p>The other day, a USB C cable plugged into the front of my Mac Studio fell on the floor and I didn't notice until my chair was about to roll over it. I picked up the cable and inadvertently tugged on the Studio ever so slightly. The Studio moved like 2mm, which was enough to spontaneously eject all the hard drives on the one USB A cable that moved. </p>
  561. <p>It gets worse. When I am going to be away from my Mac for more than an hour, I always lock it with control + command + q. This works great in the daytime—it works exactly how it has always worked since the day that keyboard shortcut was added. However, if my focus mode is on Sleep when I do this, Ventura ejects all external storage, but not by actually ejecting it or unmounting it (to, you know, prevent damage and shit), nope, Ventura cycles the power on all the USB ports (just guessing, it's not a bug, it's a feature!) which causes all the external storage to get disconnected suddenly (and I get a notification for every drive accusing me of improper removal, thanks Apple).</p>
  562. ]]></content:encoded>
  563. </item>
  564. <item>
  565. <title>
  566. Comment on Canva Acquires Affinity/Serif by Bri </title>
  567. <link>https://mjtsai.com/blog/2024/03/26/canva-acquires-affinity-serif/#comment-4061306</link>
  568.  
  569. <dc:creator><![CDATA[Bri]]></dc:creator>
  570. <pubDate>Wed, 27 Mar 2024 04:12:33 +0000</pubDate>
  571. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42650#comment-4061306</guid>
  572.  
  573. <description><![CDATA[Ah yes, Affinity&#039;s software reached the &quot;actually good, usable, and popular&quot; stage of the enshittification process, which means it was time for them to move on to the next stage: getting bought and/or investors, which means they&#039;re going to fuck everything up. We&#039;ve seen this countless times before.
  574.  
  575. I&#039;ll be shocked if Affinity&#039;s software suite is still any good five years from now.]]></description>
  576. <content:encoded><![CDATA[<p>Ah yes, Affinity's software reached the "actually good, usable, and popular" stage of the enshittification process, which means it was time for them to move on to the next stage: getting bought and/or investors, which means they're going to fuck everything up. We've seen this countless times before.</p>
  577. <p>I'll be shocked if Affinity's software suite is still any good five years from now.</p>
  578. ]]></content:encoded>
  579. </item>
  580. <item>
  581. <title>
  582. Comment on FastSpring Risk Screening by Dave </title>
  583. <link>https://mjtsai.com/blog/2023/12/07/fastspring-risk-screening/#comment-4061291</link>
  584.  
  585. <dc:creator><![CDATA[Dave]]></dc:creator>
  586. <pubDate>Wed, 27 Mar 2024 03:46:17 +0000</pubDate>
  587. <guid isPermaLink="false">https://mjtsai.com/blog/?p=41338#comment-4061291</guid>
  588.  
  589. <description><![CDATA[Wow! What a mess!
  590.  
  591. I haven&#039;t dealt with payment processors in years . . . the departed Kagi and eSellerate . . . but you know? All these reports in the comments sum up in a grim way that FastSpring is departing, too. Be careful.
  592.  
  593. Dave]]></description>
  594. <content:encoded><![CDATA[<p>Wow! What a mess!</p>
  595. <p>I haven't dealt with payment processors in years . . . the departed Kagi and eSellerate . . . but you know? All these reports in the comments sum up in a grim way that FastSpring is departing, too. Be careful.</p>
  596. <p>Dave</p>
  597. ]]></content:encoded>
  598. </item>
  599. <item>
  600. <title>
  601. Comment on Canva Acquires Affinity/Serif by Someone </title>
  602. <link>https://mjtsai.com/blog/2024/03/26/canva-acquires-affinity-serif/#comment-4061280</link>
  603.  
  604. <dc:creator><![CDATA[Someone]]></dc:creator>
  605. <pubDate>Wed, 27 Mar 2024 03:08:28 +0000</pubDate>
  606. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42650#comment-4061280</guid>
  607.  
  608. <description><![CDATA[Edits:
  609.  
  610. &quot;Then there was vector masks for bitmap layers *in Photo*&quot;
  611.  
  612. &quot;Version 2 they removed the ability *in Photo* on the Mac&quot;
  613.  
  614. &quot;you could only have documents in tabs, *with* only one visible at once.&quot;
  615.  
  616. &quot;*Publisher* couldn&#039;t do document-wide layers&quot;]]></description>
  617. <content:encoded><![CDATA[<p>Edits:</p>
  618. <p>"Then there was vector masks for bitmap layers *in Photo*"</p>
  619. <p>"Version 2 they removed the ability *in Photo* on the Mac"</p>
  620. <p>"you could only have documents in tabs, *with* only one visible at once."</p>
  621. <p>"*Publisher* couldn't do document-wide layers"</p>
  622. ]]></content:encoded>
  623. </item>
  624. <item>
  625. <title>
  626. Comment on Canva Acquires Affinity/Serif by Someone </title>
  627. <link>https://mjtsai.com/blog/2024/03/26/canva-acquires-affinity-serif/#comment-4061277</link>
  628.  
  629. <dc:creator><![CDATA[Someone]]></dc:creator>
  630. <pubDate>Wed, 27 Mar 2024 03:01:47 +0000</pubDate>
  631. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42650#comment-4061277</guid>
  632.  
  633. <description><![CDATA[I bought both v1 and v2 of the entire Affinity suite, and I wanted to love them. Truth is though, they were always awkward applications, that behaved as if they were made by people who didn&#039;t actually do the tasks you used them to do.
  634.  
  635. Publisher, lacking document-wide layers, feels like the sot of thing that would only be made by someone who didn&#039;t actually do desktop publishing, in which document-wide layers are the fundamental tool for how you build multipage documents (I think we got those in Pagemaker 6 / Quark 4 (possibly even 3) long before InDesign was a thing.
  636.  
  637. Then there was vector masks for bitmap layers, that couldn&#039;t show their bitmap art while the vector was being edited - why would you need to edit a mask, and see the content it&#039;s masking at the same time? Kinda important to the process.
  638.  
  639. Version 2 they removed the ability on the Mac to have more than one document window open on screen at once, so you couldn&#039;t work on two different documents at once, using one as reference, or developing / equalising work across both of them at once - you could only have documents in tabs without only one visible at once. The logic being &quot;this is how it works on windows&quot;.
  640.  
  641. It&#039;s sad, because their business model was great, and some of the individual features were good, but the apps overall suffered from the fact they existed to monetise a file format &quot;innovation&quot;, which dictated the abilities of the app, rather than starting with the workflow and tools, and building a file format to support that. Designer couldn&#039;t do document-wide layers, because the .affinity file format was in the way, and having a single file format was more important than the app being designed specifically as the best tool for the job.
  642.  
  643. If they go away into subscription-land, no doubt most of their users will switch back to Adobe if they can&#039;t find a purchasable alternative. That&#039;s my real concern, that they think their userbase are loyal to their product, not their economic model.]]></description>
  644. <content:encoded><![CDATA[<p>I bought both v1 and v2 of the entire Affinity suite, and I wanted to love them. Truth is though, they were always awkward applications, that behaved as if they were made by people who didn't actually do the tasks you used them to do.</p>
  645. <p>Publisher, lacking document-wide layers, feels like the sot of thing that would only be made by someone who didn't actually do desktop publishing, in which document-wide layers are the fundamental tool for how you build multipage documents (I think we got those in Pagemaker 6 / Quark 4 (possibly even 3) long before InDesign was a thing.</p>
  646. <p>Then there was vector masks for bitmap layers, that couldn't show their bitmap art while the vector was being edited - why would you need to edit a mask, and see the content it's masking at the same time? Kinda important to the process.</p>
  647. <p>Version 2 they removed the ability on the Mac to have more than one document window open on screen at once, so you couldn't work on two different documents at once, using one as reference, or developing / equalising work across both of them at once - you could only have documents in tabs without only one visible at once. The logic being "this is how it works on windows".</p>
  648. <p>It's sad, because their business model was great, and some of the individual features were good, but the apps overall suffered from the fact they existed to monetise a file format "innovation", which dictated the abilities of the app, rather than starting with the workflow and tools, and building a file format to support that. Designer couldn't do document-wide layers, because the .affinity file format was in the way, and having a single file format was more important than the app being designed specifically as the best tool for the job.</p>
  649. <p>If they go away into subscription-land, no doubt most of their users will switch back to Adobe if they can't find a purchasable alternative. That's my real concern, that they think their userbase are loyal to their product, not their economic model.</p>
  650. ]]></content:encoded>
  651. </item>
  652. <item>
  653. <title>
  654. Comment on Canva Acquires Affinity/Serif by Beatrix Willius </title>
  655. <link>https://mjtsai.com/blog/2024/03/26/canva-acquires-affinity-serif/#comment-4061271</link>
  656.  
  657. <dc:creator><![CDATA[Beatrix Willius]]></dc:creator>
  658. <pubDate>Wed, 27 Mar 2024 01:41:40 +0000</pubDate>
  659. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42650#comment-4061271</guid>
  660.  
  661. <description><![CDATA[I was really disappointed after the announcement. It was so much work to move all my icons to Affinity Designer. Affinity Photo should be easier to replace.]]></description>
  662. <content:encoded><![CDATA[<p>I was really disappointed after the announcement. It was so much work to move all my icons to Affinity Designer. Affinity Photo should be easier to replace.</p>
  663. ]]></content:encoded>
  664. </item>
  665. <item>
  666. <title>
  667. Comment on Movie Piracy App Tops App Store Charts by Bri </title>
  668. <link>https://mjtsai.com/blog/2024/03/26/movie-piracy-app-tops-app-store-charts/#comment-4061270</link>
  669.  
  670. <dc:creator><![CDATA[Bri]]></dc:creator>
  671. <pubDate>Wed, 27 Mar 2024 01:33:04 +0000</pubDate>
  672. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42646#comment-4061270</guid>
  673.  
  674. <description><![CDATA[@Nathan I totally feel you there. This is yet another slap to the face of everyone who&#039;s trying to sell a good app on the app store, and a slap to the face of users who don&#039;t want or need the &quot;protection&quot; of the app store.]]></description>
  675. <content:encoded><![CDATA[<p>@Nathan I totally feel you there. This is yet another slap to the face of everyone who's trying to sell a good app on the app store, and a slap to the face of users who don't want or need the "protection" of the app store.</p>
  676. ]]></content:encoded>
  677. </item>
  678. <item>
  679. <title>
  680. Comment on Movie Piracy App Tops App Store Charts by Nathan </title>
  681. <link>https://mjtsai.com/blog/2024/03/26/movie-piracy-app-tops-app-store-charts/#comment-4061262</link>
  682.  
  683. <dc:creator><![CDATA[Nathan]]></dc:creator>
  684. <pubDate>Wed, 27 Mar 2024 01:11:34 +0000</pubDate>
  685. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42646#comment-4061262</guid>
  686.  
  687. <description><![CDATA[So a piracy app that Apple could take a cut of the proceeds from was on the App Store for a good while, but normal developers are still being blocked capriciously? Alert Gruber so he can tell us why the new App Store rules will cause this thing to happen in the future… but we are totally protected now from such unsavory business.]]></description>
  688. <content:encoded><![CDATA[<p>So a piracy app that Apple could take a cut of the proceeds from was on the App Store for a good while, but normal developers are still being blocked capriciously? Alert Gruber so he can tell us why the new App Store rules will cause this thing to happen in the future… but we are totally protected now from such unsavory business.</p>
  689. ]]></content:encoded>
  690. </item>
  691. <item>
  692. <title>
  693. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by Nathan </title>
  694. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4061261</link>
  695.  
  696. <dc:creator><![CDATA[Nathan]]></dc:creator>
  697. <pubDate>Wed, 27 Mar 2024 01:05:13 +0000</pubDate>
  698. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4061261</guid>
  699.  
  700. <description><![CDATA[@DJ
  701. That&#039;s a fair point, maybe we are more technically sophisticated than the average user, but I&#039;m really not as learned as my fellows here. I&#039;m not a programmer and I&#039;m not really that wise to these things, I&#039;m more of an active hobbyist who sometimes gets to do it semi-professionally. :)
  702.  
  703. I don&#039;t have much to add given your explanation, but was curious how Ubuntu is serving your organization. I didn&#039;t really start using Linux until Ubuntu was out in 2004, but wow, 20 years already, eh? At some point for personal use I switched to Arch based systems and didn&#039;t look back but I used Ubuntu for years.]]></description>
  704. <content:encoded><![CDATA[<p>@DJ<br />
  705. That's a fair point, maybe we are more technically sophisticated than the average user, but I'm really not as learned as my fellows here. I'm not a programmer and I'm not really that wise to these things, I'm more of an active hobbyist who sometimes gets to do it semi-professionally. :)</p>
  706. <p>I don't have much to add given your explanation, but was curious how Ubuntu is serving your organization. I didn't really start using Linux until Ubuntu was out in 2004, but wow, 20 years already, eh? At some point for personal use I switched to Arch based systems and didn't look back but I used Ubuntu for years.</p>
  707. ]]></content:encoded>
  708. </item>
  709. <item>
  710. <title>
  711. Comment on Movie Piracy App Tops App Store Charts by Marcos </title>
  712. <link>https://mjtsai.com/blog/2024/03/26/movie-piracy-app-tops-app-store-charts/#comment-4061237</link>
  713.  
  714. <dc:creator><![CDATA[Marcos]]></dc:creator>
  715. <pubDate>Tue, 26 Mar 2024 23:17:30 +0000</pubDate>
  716. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42646#comment-4061237</guid>
  717.  
  718. <description><![CDATA[IANAL, but this is the crap the government should be focused on. These seemingly arbitrary and unevenly applied rules affect the livelihood of individual developers in a drastic way.
  719.  
  720. On top of that, I can only imagine the excellent and innovative apps that many have dreamed up but decided to never develop because of the uncertainty that it may get rejected AFTER the investment goes in developing or because they fall outside of the rules.
  721.  
  722. And how many business could thrive with a 5-15% Apple fee but can’t survive with 30%?
  723.  
  724. This whole mess has a terrible effect on the developer community and on Apple’s own platforms. One can only imagine how things could be…]]></description>
  725. <content:encoded><![CDATA[<p>IANAL, but this is the crap the government should be focused on. These seemingly arbitrary and unevenly applied rules affect the livelihood of individual developers in a drastic way.</p>
  726. <p>On top of that, I can only imagine the excellent and innovative apps that many have dreamed up but decided to never develop because of the uncertainty that it may get rejected AFTER the investment goes in developing or because they fall outside of the rules. </p>
  727. <p>And how many business could thrive with a 5-15% Apple fee but can’t survive with 30%?</p>
  728. <p>This whole mess has a terrible effect on the developer community and on Apple’s own platforms. One can only imagine how things could be…</p>
  729. ]]></content:encoded>
  730. </item>
  731. <item>
  732. <title>
  733. Comment on DMA Non-Compliance Investigations by Old Unix Geek </title>
  734. <link>https://mjtsai.com/blog/2024/03/26/dma-non-compliance-investigations/#comment-4061229</link>
  735.  
  736. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  737. <pubDate>Tue, 26 Mar 2024 22:41:51 +0000</pubDate>
  738. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42648#comment-4061229</guid>
  739.  
  740. <description><![CDATA[I&#039;d be surprised if the EU was only 7% of Apple&#039;s revenue. It might be only 7% of App Store revenue, but in that case they might need to explain the cause of this discrepancy. The EU might think that is due to App Store restrictions. It might also have to do with poor quality &quot;localization&quot; instead of apps actually designed for the relevant European culture... and Europeans not being satisfied by simply making do the way others might. Despite widespread belief in the US, not everyone on the planet is a temporarily embarrassed American just yearning to be freed of his/her cultural &quot;shackles&quot;.]]></description>
  741. <content:encoded><![CDATA[<p>I'd be surprised if the EU was only 7% of Apple's revenue. It might be only 7% of App Store revenue, but in that case they might need to explain the cause of this discrepancy. The EU might think that is due to App Store restrictions. It might also have to do with poor quality "localization" instead of apps actually designed for the relevant European culture... and Europeans not being satisfied by simply making do the way others might. Despite widespread belief in the US, not everyone on the planet is a temporarily embarrassed American just yearning to be freed of his/her cultural "shackles".</p>
  742. ]]></content:encoded>
  743. </item>
  744. <item>
  745. <title>
  746. Comment on Canva Acquires Affinity/Serif by Chris </title>
  747. <link>https://mjtsai.com/blog/2024/03/26/canva-acquires-affinity-serif/#comment-4061227</link>
  748.  
  749. <dc:creator><![CDATA[Chris]]></dc:creator>
  750. <pubDate>Tue, 26 Mar 2024 22:33:21 +0000</pubDate>
  751. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42650#comment-4061227</guid>
  752.  
  753. <description><![CDATA[Procreate will be next......]]></description>
  754. <content:encoded><![CDATA[<p>Procreate will be next......</p>
  755. ]]></content:encoded>
  756. </item>
  757. <item>
  758. <title>
  759. Comment on Canva Acquires Affinity/Serif by billyok </title>
  760. <link>https://mjtsai.com/blog/2024/03/26/canva-acquires-affinity-serif/#comment-4061205</link>
  761.  
  762. <dc:creator><![CDATA[billyok]]></dc:creator>
  763. <pubDate>Tue, 26 Mar 2024 20:59:25 +0000</pubDate>
  764. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42650#comment-4061205</guid>
  765.  
  766. <description><![CDATA[&quot;None of that changes today.&quot;
  767.  
  768. But check back in a year or two!
  769.  
  770. Just dreadful, dreadful news. Nothing lasts forever but these days it feels like nothing lasts at all before someone comes along to ruin it.]]></description>
  771. <content:encoded><![CDATA[<p>"None of that changes today."</p>
  772. <p>But check back in a year or two! </p>
  773. <p>Just dreadful, dreadful news. Nothing lasts forever but these days it feels like nothing lasts at all before someone comes along to ruin it.</p>
  774. ]]></content:encoded>
  775. </item>
  776. <item>
  777. <title>
  778. Comment on macOS 14.4.1 by Mac Folklore Radio </title>
  779. <link>https://mjtsai.com/blog/2024/03/25/macos-14-4-1/#comment-4061200</link>
  780.  
  781. <dc:creator><![CDATA[Mac Folklore Radio]]></dc:creator>
  782. <pubDate>Tue, 26 Mar 2024 20:51:02 +0000</pubDate>
  783. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42631#comment-4061200</guid>
  784.  
  785. <description><![CDATA[USB-C connectivity to my Dell U3818W would flake out once or twice a year on a 2018 Mac Mini and a 2020 MacBook Air. No big deal.
  786.  
  787. However, since moving to a 16-inch M3 MacBook Pro I have to unplug/replug the darned thing up to 10 times before it gets a signal. :\ So at least to me this isn&#039;t an entirely new problem.
  788.  
  789. I&#039;m not installing any more updates until I buy a new machine, though. Just kidding! ... sort of. At least my audio software works again.]]></description>
  790. <content:encoded><![CDATA[<p>USB-C connectivity to my Dell U3818W would flake out once or twice a year on a 2018 Mac Mini and a 2020 MacBook Air. No big deal.</p>
  791. <p>However, since moving to a 16-inch M3 MacBook Pro I have to unplug/replug the darned thing up to 10 times before it gets a signal. :\ So at least to me this isn't an entirely new problem.</p>
  792. <p>I'm not installing any more updates until I buy a new machine, though. Just kidding! ... sort of. At least my audio software works again.</p>
  793. ]]></content:encoded>
  794. </item>
  795. <item>
  796. <title>
  797. Comment on _eventFirstResponderChainDescription by Alexandre Dieulot </title>
  798. <link>https://mjtsai.com/blog/2024/03/22/_eventfirstresponderchaindescription/#comment-4061181</link>
  799.  
  800. <dc:creator><![CDATA[Alexandre Dieulot]]></dc:creator>
  801. <pubDate>Tue, 26 Mar 2024 20:08:38 +0000</pubDate>
  802. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42614#comment-4061181</guid>
  803.  
  804. <description><![CDATA[I wondered if that user default could be injected easily into every app with a “defaults” command, and indeed you can!
  805.  
  806. defaults write -g _NS_4445425547 -bool true]]></description>
  807. <content:encoded><![CDATA[<p>I wondered if that user default could be injected easily into every app with a “defaults” command, and indeed you can!</p>
  808. <p>defaults write -g _NS_4445425547 -bool true</p>
  809. ]]></content:encoded>
  810. </item>
  811. <item>
  812. <title>
  813. Comment on macOS 14.4.1 by Michael Tsai </title>
  814. <link>https://mjtsai.com/blog/2024/03/25/macos-14-4-1/#comment-4061155</link>
  815.  
  816. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  817. <pubDate>Tue, 26 Mar 2024 18:53:41 +0000</pubDate>
  818. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42631#comment-4061155</guid>
  819.  
  820. <description><![CDATA[@Daniël I found that, even when plugged directly into the MacBook Pro, the Studio Display hub is unreliable.]]></description>
  821. <content:encoded><![CDATA[<p>@Daniël I found that, even when plugged directly into the MacBook Pro, the Studio Display hub is unreliable.</p>
  822. ]]></content:encoded>
  823. </item>
  824. <item>
  825. <title>
  826. Comment on macOS 14.4.1 by Daniël de Kok </title>
  827. <link>https://mjtsai.com/blog/2024/03/25/macos-14-4-1/#comment-4061154</link>
  828.  
  829. <dc:creator><![CDATA[Daniël de Kok]]></dc:creator>
  830. <pubDate>Tue, 26 Mar 2024 18:50:15 +0000</pubDate>
  831. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42631#comment-4061154</guid>
  832.  
  833. <description><![CDATA[I have similar experiences. One StarTech dock that we have in the house worked great. Then after one macOS update (I think 13.0.0) it started having issues waking the external DisplayPort display after sleep. Since then it was never fixed. It&#039;s all the more surprising when you consider that many Thunderbolt docks are based on the same reference designs. So Apple would only have to test a handful of docks.
  834.  
  835. Of course, Apple&#039;s stuff (MacBook ports and Studio Display ports) works flawless.]]></description>
  836. <content:encoded><![CDATA[<p>I have similar experiences. One StarTech dock that we have in the house worked great. Then after one macOS update (I think 13.0.0) it started having issues waking the external DisplayPort display after sleep. Since then it was never fixed. It's all the more surprising when you consider that many Thunderbolt docks are based on the same reference designs. So Apple would only have to test a handful of docks.</p>
  837. <p>Of course, Apple's stuff (MacBook ports and Studio Display ports) works flawless.</p>
  838. ]]></content:encoded>
  839. </item>
  840. <item>
  841. <title>
  842. Comment on macOS 14.4.1 by Sören </title>
  843. <link>https://mjtsai.com/blog/2024/03/25/macos-14-4-1/#comment-4061137</link>
  844.  
  845. <dc:creator><![CDATA[Sören]]></dc:creator>
  846. <pubDate>Tue, 26 Mar 2024 17:55:22 +0000</pubDate>
  847. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42631#comment-4061137</guid>
  848.  
  849. <description><![CDATA[Yep.
  850.  
  851. Anecdotally:
  852.  
  853. * for a while, I was on a Belkin Tb 2 dock, through a 3 to 2 adapter. This worked fine, except 1) there’s no power delivery that way, and 2) the monitor connected through the dock took 20-30 seconds to wake up; the one connected directly to the building-in HDMI port &#060; 3 seconds. But other than that, it only flaked once or twice a year. USB, Ethernet, etc. all right there.
  854.  
  855. * mainly to simplify power, I got a Dell dock.  It even supports connecting both displays, and of course power delivery. But, 1) almost every single time, my Magic Trackpad (connected by a chain of laptop → dock → USB hub; no different than with the Belkin) refuses to wake up until I disconnect and reconnect Lightning, and 2) in about two and a half months, I’ve already had two kernel panics.
  856.  
  857. It invariably introduces complexity and points of failure. Still, being able to connect literally one cable and having everything right there is nice.]]></description>
  858. <content:encoded><![CDATA[<p>Yep.</p>
  859. <p>Anecdotally:</p>
  860. <p>* for a while, I was on a Belkin Tb 2 dock, through a 3 to 2 adapter. This worked fine, except 1) there’s no power delivery that way, and 2) the monitor connected through the dock took 20-30 seconds to wake up; the one connected directly to the building-in HDMI port &lt; 3 seconds. But other than that, it only flaked once or twice a year. USB, Ethernet, etc. all right there.</p>
  861. <p>* mainly to simplify power, I got a Dell dock.  It even supports connecting both displays, and of course power delivery. But, 1) almost every single time, my Magic Trackpad (connected by a chain of laptop → dock → USB hub; no different than with the Belkin) refuses to wake up until I disconnect and reconnect Lightning, and 2) in about two and a half months, I’ve already had two kernel panics.</p>
  862. <p>It invariably introduces complexity and points of failure. Still, being able to connect literally one cable and having everything right there is nice.</p>
  863. ]]></content:encoded>
  864. </item>
  865. <item>
  866. <title>
  867. Comment on macOS 14.4.1 by Michael Tsai </title>
  868. <link>https://mjtsai.com/blog/2024/03/25/macos-14-4-1/#comment-4061126</link>
  869.  
  870. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  871. <pubDate>Tue, 26 Mar 2024 17:30:08 +0000</pubDate>
  872. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42631#comment-4061126</guid>
  873.  
  874. <description><![CDATA[@Bri Yes, my experience is that internal ports are always better, even when using an expensive Thunderbolt dock/hub.]]></description>
  875. <content:encoded><![CDATA[<p>@Bri Yes, my experience is that internal ports are always better, even when using an expensive Thunderbolt dock/hub.</p>
  876. ]]></content:encoded>
  877. </item>
  878. <item>
  879. <title>
  880. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by Kristoffer </title>
  881. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4061073</link>
  882.  
  883. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  884. <pubDate>Tue, 26 Mar 2024 15:52:19 +0000</pubDate>
  885. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4061073</guid>
  886.  
  887. <description><![CDATA[&#062;developers know that they&#039;ll need to develop using Xcode and that there are a set of rules for developing and selling apps. Regardless of the size of the company or market, is it reasonable or fair to knowingly sign up for all of that and then complain about it?
  888.  
  889. But it&#039;s well documented that the rules they sign up for can change at any moment. Or that the rules won&#039;t change but their implementation will change. Or nothing changes and you just get ghosted. Or that one company has one set of rules and you another.
  890.  
  891. It&#039;s absolutely vital to complain when someone is abusing their power. Regardless of size, but I&#039;d say especially when they are huge.]]></description>
  892. <content:encoded><![CDATA[<p>&gt;developers know that they'll need to develop using Xcode and that there are a set of rules for developing and selling apps. Regardless of the size of the company or market, is it reasonable or fair to knowingly sign up for all of that and then complain about it?</p>
  893. <p>But it's well documented that the rules they sign up for can change at any moment. Or that the rules won't change but their implementation will change. Or nothing changes and you just get ghosted. Or that one company has one set of rules and you another.</p>
  894. <p>It's absolutely vital to complain when someone is abusing their power. Regardless of size, but I'd say especially when they are huge.</p>
  895. ]]></content:encoded>
  896. </item>
  897. <item>
  898. <title>
  899. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by DJ </title>
  900. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4061070</link>
  901.  
  902. <dc:creator><![CDATA[DJ]]></dc:creator>
  903. <pubDate>Tue, 26 Mar 2024 15:50:19 +0000</pubDate>
  904. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4061070</guid>
  905.  
  906. <description><![CDATA[@Soren: I get what you&#039;re saying.  But if you&#039;re a mobile app developer, these market conditions are already known to you.  It&#039;s unfortunate that the app market devolved into a &quot;race to the bottom&quot; on price.  With most businesses, you would just roll store commissions into your cost model and price your wares accordingly.]]></description>
  907. <content:encoded><![CDATA[<p>@Soren: I get what you're saying.  But if you're a mobile app developer, these market conditions are already known to you.  It's unfortunate that the app market devolved into a "race to the bottom" on price.  With most businesses, you would just roll store commissions into your cost model and price your wares accordingly.</p>
  908. ]]></content:encoded>
  909. </item>
  910. <item>
  911. <title>
  912. Comment on macOS 14.4.1 by Bri </title>
  913. <link>https://mjtsai.com/blog/2024/03/25/macos-14-4-1/#comment-4061054</link>
  914.  
  915. <dc:creator><![CDATA[Bri]]></dc:creator>
  916. <pubDate>Tue, 26 Mar 2024 15:28:05 +0000</pubDate>
  917. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42631#comment-4061054</guid>
  918.  
  919. <description><![CDATA[Part of the reason I&#039;m annoyed that Apple decided to start jettisoning ports from most of their mac models is because hubs just don&#039;t work as well. In my experience they&#039;re a bit janky and sometimes have very strange issues. This 14.4 update is one example of that.
  920.  
  921. Another example is that my OWC Thunderbolt 3 hub keeps losing it&#039;s connection if I bump its cable, and it happens no matter what cable I use. You don&#039;t have to worry about defects like that with internal ports!
  922.  
  923. And another good example is that I have a USB audio device that, if I plug it into one specific USB-A port on my CalDigit Thunderbolt hub, will cause the entire hub to start power cycling repeatedly over and over! The hub is otherwise not defective. And the only thing I&#039;ve found that does it is plugging in that one specific device into that one specific port. It works fine on all of the other ports.
  924.  
  925. I have other examples, but the purpose of me pointing them out is to illustrate that making a USB / Thunderbolt hub that works as consistently as using an internal port is obviously very difficult, if not outright impossible.
  926.  
  927. Of course your mileage may vary -- I&#039;m sure there are people out there that just *never* have these sorts of problems, especially given that I&#039;m a magnet for them for some reason. But they pretty much just don&#039;t happen when you use the built-in USB ports on your mac, at least in my experience. Those generally &quot;just work&quot; -- you know, that thing macs *used* to do.
  928.  
  929. I suppose nowadays if you want enough ports that you probably don&#039;t need a hub or dock, then you have to spring for the absurdly overpriced Mac Pro, or perhaps a Mac Studio. (Though honestly I would run out of ports on a Mac Studio.) There&#039;s no good option for portable macs.
  930.  
  931. My reasonably priced 2009 Mac Pro didn&#039;t need any hubs or docks. I could even add an expansion card to give it more and higher speed USB ports (though admittedly it didn&#039;t work 100% either). I wish Apple still sold a mac like that.]]></description>
  932. <content:encoded><![CDATA[<p>Part of the reason I'm annoyed that Apple decided to start jettisoning ports from most of their mac models is because hubs just don't work as well. In my experience they're a bit janky and sometimes have very strange issues. This 14.4 update is one example of that.</p>
  933. <p>Another example is that my OWC Thunderbolt 3 hub keeps losing it's connection if I bump its cable, and it happens no matter what cable I use. You don't have to worry about defects like that with internal ports!</p>
  934. <p>And another good example is that I have a USB audio device that, if I plug it into one specific USB-A port on my CalDigit Thunderbolt hub, will cause the entire hub to start power cycling repeatedly over and over! The hub is otherwise not defective. And the only thing I've found that does it is plugging in that one specific device into that one specific port. It works fine on all of the other ports.</p>
  935. <p>I have other examples, but the purpose of me pointing them out is to illustrate that making a USB / Thunderbolt hub that works as consistently as using an internal port is obviously very difficult, if not outright impossible.</p>
  936. <p>Of course your mileage may vary -- I'm sure there are people out there that just *never* have these sorts of problems, especially given that I'm a magnet for them for some reason. But they pretty much just don't happen when you use the built-in USB ports on your mac, at least in my experience. Those generally "just work" -- you know, that thing macs *used* to do.</p>
  937. <p>I suppose nowadays if you want enough ports that you probably don't need a hub or dock, then you have to spring for the absurdly overpriced Mac Pro, or perhaps a Mac Studio. (Though honestly I would run out of ports on a Mac Studio.) There's no good option for portable macs.</p>
  938. <p>My reasonably priced 2009 Mac Pro didn't need any hubs or docks. I could even add an expansion card to give it more and higher speed USB ports (though admittedly it didn't work 100% either). I wish Apple still sold a mac like that.</p>
  939. ]]></content:encoded>
  940. </item>
  941. <item>
  942. <title>
  943. Comment on Digital Wallets and the &#8220;Only Apple Pay Does This&#8221; Mythology by Kristoffer </title>
  944. <link>https://mjtsai.com/blog/2024/03/25/digital-wallets-and-the-only-apple-pay-does-this-mythology/#comment-4060896</link>
  945.  
  946. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  947. <pubDate>Tue, 26 Mar 2024 11:42:40 +0000</pubDate>
  948. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42637#comment-4060896</guid>
  949.  
  950. <description><![CDATA[A great reminder that the Dunning-Kruger effect is real and that I shouldn&#039;t criticise things I don&#039;t know, or have no way of verifying.
  951.  
  952. Like how some well known bloggers keep insisting that Google no longer links to Google flights, I&#039;m literally just now looking at a Google flights result that showed up when I Googled CPH to PEK, or that third party price comparisons sites should somehow be worse than the sponsored crap google keep shoving in my face.]]></description>
  953. <content:encoded><![CDATA[<p>A great reminder that the Dunning-Kruger effect is real and that I shouldn't criticise things I don't know, or have no way of verifying. </p>
  954. <p>Like how some well known bloggers keep insisting that Google no longer links to Google flights, I'm literally just now looking at a Google flights result that showed up when I Googled CPH to PEK, or that third party price comparisons sites should somehow be worse than the sponsored crap google keep shoving in my face.</p>
  955. ]]></content:encoded>
  956. </item>
  957. <item>
  958. <title>
  959. Comment on Digital Wallets and the &#8220;Only Apple Pay Does This&#8221; Mythology by Mark </title>
  960. <link>https://mjtsai.com/blog/2024/03/25/digital-wallets-and-the-only-apple-pay-does-this-mythology/#comment-4060763</link>
  961.  
  962. <dc:creator><![CDATA[Mark]]></dc:creator>
  963. <pubDate>Tue, 26 Mar 2024 09:49:29 +0000</pubDate>
  964. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42637#comment-4060763</guid>
  965.  
  966. <description><![CDATA[The post by Matt Birchler has been amended with the paragraph &quot;A previous version of this post suggested the DPAN changes between merchants, but that was a mistake. Serves me right for cranking this post out too quickly. Seriously, my bad.&quot;. However, the rest of the post still suggests that there is a unique DPAN per merchant, but I can&#039;t find any basis for that.
  967.  
  968. Even Apple&#039;s own documentation at https://support.apple.com/en-us/HT203027 says that the DPAN (called Device Account Number here) is only unique per device. When a card is added to Apple Pay a DPAN is created for that device, and it never gets changed afterwards unless the card is removed and re-added.
  969.  
  970. So whereas you can&#039;t be tracked by using the same card on two devices (e.g. iPhone and Apple Watch) because they will have two different DPANs, I&#039;m pretty sure data brokers can track you when using the same card on the same device across different merchants.]]></description>
  971. <content:encoded><![CDATA[<p>The post by Matt Birchler has been amended with the paragraph "A previous version of this post suggested the DPAN changes between merchants, but that was a mistake. Serves me right for cranking this post out too quickly. Seriously, my bad.". However, the rest of the post still suggests that there is a unique DPAN per merchant, but I can't find any basis for that.</p>
  972. <p>Even Apple's own documentation at <a href="https://support.apple.com/en-us/HT203027" rel="nofollow ugc">https://support.apple.com/en-us/HT203027</a> says that the DPAN (called Device Account Number here) is only unique per device. When a card is added to Apple Pay a DPAN is created for that device, and it never gets changed afterwards unless the card is removed and re-added.</p>
  973. <p>So whereas you can't be tracked by using the same card on two devices (e.g. iPhone and Apple Watch) because they will have two different DPANs, I'm pretty sure data brokers can track you when using the same card on the same device across different merchants.</p>
  974. ]]></content:encoded>
  975. </item>
  976. <item>
  977. <title>
  978. Comment on Digital Wallets and the &#8220;Only Apple Pay Does This&#8221; Mythology by Ralph </title>
  979. <link>https://mjtsai.com/blog/2024/03/25/digital-wallets-and-the-only-apple-pay-does-this-mythology/#comment-4060704</link>
  980.  
  981. <dc:creator><![CDATA[Ralph]]></dc:creator>
  982. <pubDate>Tue, 26 Mar 2024 08:53:13 +0000</pubDate>
  983. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42637#comment-4060704</guid>
  984.  
  985. <description><![CDATA[From my limited experience as a merchant, if you pay with card # on my hosted payment page I get less details about you compared to Apple Pay,
  986.  
  987. Apple Pay shares email/phone number/billing address you want it or not.]]></description>
  988. <content:encoded><![CDATA[<p>From my limited experience as a merchant, if you pay with card # on my hosted payment page I get less details about you compared to Apple Pay, </p>
  989. <p>Apple Pay shares email/phone number/billing address you want it or not.</p>
  990. ]]></content:encoded>
  991. </item>
  992. <item>
  993. <title>
  994. Comment on U.S. Sues Apple Over iPhone Monopoly by Kristoffer </title>
  995. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4060701</link>
  996.  
  997. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  998. <pubDate>Tue, 26 Mar 2024 08:49:04 +0000</pubDate>
  999. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4060701</guid>
  1000.  
  1001. <description><![CDATA[I meant that the reason why the DOJ opened the case, and why Eu has created the DMA/DSA is not complicated at all. The suit and the law are complicated, but why we need them isn&#039;t.
  1002.  
  1003. It&#039;s enough to list the number of abusive things apple are routinely doing, and like you say, point to the power apple have.
  1004.  
  1005. Funilly enough I haven&#039;t seen any mention of the draconian contracts they make network operators that want to sell iPhones sign.
  1006.  
  1007. Anyway, I find the reaching for ever weirder analogies to explain apples power and abusive use of said power completely unnecessary.]]></description>
  1008. <content:encoded><![CDATA[<p>I meant that the reason why the DOJ opened the case, and why Eu has created the DMA/DSA is not complicated at all. The suit and the law are complicated, but why we need them isn't.</p>
  1009. <p>It's enough to list the number of abusive things apple are routinely doing, and like you say, point to the power apple have.</p>
  1010. <p>Funilly enough I haven't seen any mention of the draconian contracts they make network operators that want to sell iPhones sign.</p>
  1011. <p>Anyway, I find the reaching for ever weirder analogies to explain apples power and abusive use of said power completely unnecessary.</p>
  1012. ]]></content:encoded>
  1013. </item>
  1014. <item>
  1015. <title>
  1016. Comment on macOS 13.6.6 by Eric Knibbe </title>
  1017. <link>https://mjtsai.com/blog/2024/03/25/macos-13-6-6/#comment-4060446</link>
  1018.  
  1019. <dc:creator><![CDATA[Eric Knibbe]]></dc:creator>
  1020. <pubDate>Mon, 25 Mar 2024 23:22:14 +0000</pubDate>
  1021. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42633#comment-4060446</guid>
  1022.  
  1023. <description><![CDATA[Likely because the associated CVE affects AV1 decoding, which isn’t present in Monterey.]]></description>
  1024. <content:encoded><![CDATA[<p>Likely because the associated CVE affects AV1 decoding, which isn’t present in Monterey.</p>
  1025. ]]></content:encoded>
  1026. </item>
  1027. <item>
  1028. <title>
  1029. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by Sören </title>
  1030. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4060359</link>
  1031.  
  1032. <dc:creator><![CDATA[Sören]]></dc:creator>
  1033. <pubDate>Mon, 25 Mar 2024 20:39:21 +0000</pubDate>
  1034. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4060359</guid>
  1035.  
  1036. <description><![CDATA[&#062; Regardless of the size of the company or market, is it reasonable or fair to knowingly sign up for all of that and then complain about it?
  1037.  
  1038. I think it is, and I don’t think you _should_ disregard the market when answering that.
  1039.  
  1040. Because it isn’t “oh, I could make this available for iOS, too!” so much as “I guess I _have_ to make it available for iOS, huh”.]]></description>
  1041. <content:encoded><![CDATA[<p>&gt; Regardless of the size of the company or market, is it reasonable or fair to knowingly sign up for all of that and then complain about it?</p>
  1042. <p>I think it is, and I don’t think you _should_ disregard the market when answering that.</p>
  1043. <p>Because it isn’t “oh, I could make this available for iOS, too!” so much as “I guess I _have_ to make it available for iOS, huh”.</p>
  1044. ]]></content:encoded>
  1045. </item>
  1046. <item>
  1047. <title>
  1048. Comment on U.S. Sues Apple Over iPhone Monopoly by Sören </title>
  1049. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4060304</link>
  1050.  
  1051. <dc:creator><![CDATA[Sören]]></dc:creator>
  1052. <pubDate>Mon, 25 Mar 2024 18:45:24 +0000</pubDate>
  1053. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4060304</guid>
  1054.  
  1055. <description><![CDATA[&#062;There is no need to use analogies at all.
  1056.  
  1057. I disagree, especially for the US. I&#039;m with Siracusa on that — they don&#039;t _quite_ have the right law to fit this behavior.
  1058.  
  1059. &#062;This is not complicated at all.
  1060.  
  1061. Oh, I think it&#039;s _very_ complicated, and as evidence, I&#039;ll bring
  1062.  
  1063. - that Michael&#039;s article has 2,500 (mostly quoted) words
  1064. - that the EU wrote a big piece of new legislation
  1065.  
  1066. &#062;Like how Apple won&#039;t approve Spotifys latest update, or tell them why.
  1067.  
  1068. Right, but there&#039;s no all-encompassing &quot;a corporation may not act capriciously&quot; law. It&#039;s only once you factor in the amount of power Apple wields that this even becomes legally relevant; take that away, and all you have is &quot;some Apple customers are unhappy with Apple&#039;s behavior&quot;.]]></description>
  1069. <content:encoded><![CDATA[<p>&gt;There is no need to use analogies at all.</p>
  1070. <p>I disagree, especially for the US. I'm with Siracusa on that — they don't _quite_ have the right law to fit this behavior.</p>
  1071. <p>&gt;This is not complicated at all.</p>
  1072. <p>Oh, I think it's _very_ complicated, and as evidence, I'll bring</p>
  1073. <p>- that Michael's article has 2,500 (mostly quoted) words<br />
  1074. - that the EU wrote a big piece of new legislation</p>
  1075. <p>&gt;Like how Apple won't approve Spotifys latest update, or tell them why.</p>
  1076. <p>Right, but there's no all-encompassing "a corporation may not act capriciously" law. It's only once you factor in the amount of power Apple wields that this even becomes legally relevant; take that away, and all you have is "some Apple customers are unhappy with Apple's behavior".</p>
  1077. ]]></content:encoded>
  1078. </item>
  1079. <item>
  1080. <title>
  1081. Comment on Nitro 2024.1 by jeff </title>
  1082. <link>https://mjtsai.com/blog/2024/03/14/nitro-2024-1/#comment-4060295</link>
  1083.  
  1084. <dc:creator><![CDATA[jeff]]></dc:creator>
  1085. <pubDate>Mon, 25 Mar 2024 18:34:02 +0000</pubDate>
  1086. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42509#comment-4060295</guid>
  1087.  
  1088. <description><![CDATA[First let me say thanks for continually working on these software editing tools.
  1089.  
  1090. Let me ask, one of the biggest requirements I have is being able to browse through a folder of images and tag or color label selects so when I&#039;m opening into another software that&#039;s using the finder I can quickly see the tagged (green) files.  
  1091.  
  1092. I know Raw Power could do it then the OS updated and it couldn&#039;t. Can Nitro, using Sonoma 14.4 on an old macbook pro 18 (Intel)?  Any insights are appreciated.
  1093.  
  1094. thanks,]]></description>
  1095. <content:encoded><![CDATA[<p>First let me say thanks for continually working on these software editing tools.</p>
  1096. <p>Let me ask, one of the biggest requirements I have is being able to browse through a folder of images and tag or color label selects so when I'm opening into another software that's using the finder I can quickly see the tagged (green) files.  </p>
  1097. <p>I know Raw Power could do it then the OS updated and it couldn't. Can Nitro, using Sonoma 14.4 on an old macbook pro 18 (Intel)?  Any insights are appreciated.</p>
  1098. <p>thanks,</p>
  1099. ]]></content:encoded>
  1100. </item>
  1101. <item>
  1102. <title>
  1103. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by DJ </title>
  1104. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4060240</link>
  1105.  
  1106. <dc:creator><![CDATA[DJ]]></dc:creator>
  1107. <pubDate>Mon, 25 Mar 2024 16:54:08 +0000</pubDate>
  1108. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4060240</guid>
  1109.  
  1110. <description><![CDATA[@Nathan, sorry if I seemed to imply that your opinions were not valid.  Insulting anyone is not my intention, although that doesn&#039;t seem to be a rule.  None of us here are &quot;normal&quot; consumers, given our technical/developer/IT levels of expertise.
  1111.  
  1112. I started out with Apple with a Mac SE and Mac II back when those were new, and I built a fairly large cluster using Xserves.  Before that I worked on VAX systems, so I&#039;ve been around a while. :-)  That might paint a picture of favoring underdogs -- VAXes when the world leaned IBM, Macs when the world leaned Windows -- but for me it has always been about what least got in the way of what I wanted to do.  Do I want to make a deck of punch cards and submit it to the IBM batch queue, or do I want to use a terminal on the PDP-11 and enter commands directly?
  1113.  
  1114. Anyway, the topic at hand is Apple, so I&#039;ve been speaking my opinions about Apple.  Apple created the iOS platform to compete in the smartphone market.  Everyone who signs on with Apple knows what they&#039;re getting into.  Consumers know that they will only be able to run iOS apps, developers know that they&#039;ll need to develop using Xcode and that there are a set of rules for developing and selling apps. Regardless of the size of the company or market, is it reasonable or fair to knowingly sign up for all of that and then complain about it?
  1115.  
  1116. I agree with you on what IBM has done with RedHat (and CentOS).  But I also think that IBM is free to do that with their products, just as I was free to switch all of my organization&#039;s Linux desktops and servers to Ubuntu.]]></description>
  1117. <content:encoded><![CDATA[<p>@Nathan, sorry if I seemed to imply that your opinions were not valid.  Insulting anyone is not my intention, although that doesn't seem to be a rule.  None of us here are "normal" consumers, given our technical/developer/IT levels of expertise.</p>
  1118. <p>I started out with Apple with a Mac SE and Mac II back when those were new, and I built a fairly large cluster using Xserves.  Before that I worked on VAX systems, so I've been around a while. :-)  That might paint a picture of favoring underdogs -- VAXes when the world leaned IBM, Macs when the world leaned Windows -- but for me it has always been about what least got in the way of what I wanted to do.  Do I want to make a deck of punch cards and submit it to the IBM batch queue, or do I want to use a terminal on the PDP-11 and enter commands directly?</p>
  1119. <p>Anyway, the topic at hand is Apple, so I've been speaking my opinions about Apple.  Apple created the iOS platform to compete in the smartphone market.  Everyone who signs on with Apple knows what they're getting into.  Consumers know that they will only be able to run iOS apps, developers know that they'll need to develop using Xcode and that there are a set of rules for developing and selling apps. Regardless of the size of the company or market, is it reasonable or fair to knowingly sign up for all of that and then complain about it?</p>
  1120. <p>I agree with you on what IBM has done with RedHat (and CentOS).  But I also think that IBM is free to do that with their products, just as I was free to switch all of my organization's Linux desktops and servers to Ubuntu.</p>
  1121. ]]></content:encoded>
  1122. </item>
  1123. <item>
  1124. <title>
  1125. Comment on PopClip Leaving the Mac App Store by Greg Scown </title>
  1126. <link>https://mjtsai.com/blog/2024/03/21/popclip-leaving-the-mac-app-store/#comment-4060174</link>
  1127.  
  1128. <dc:creator><![CDATA[Greg Scown]]></dc:creator>
  1129. <pubDate>Mon, 25 Mar 2024 14:38:31 +0000</pubDate>
  1130. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42592#comment-4060174</guid>
  1131.  
  1132. <description><![CDATA[TextExpander faced this same problem back in 2012:
  1133.  
  1134. https://mjtsai.com/blog/2012/06/22/textexpander-4-leaves-mac-app-store/
  1135.  
  1136. I filed a feature request for an entitlement for CGEventTaps back when Sandboxing was introduced. I lobbied Ivan Krstić after his session on Sandboxing at WWDC. If I recall correctly, the main objection was that Apple had no means to limit entitlement requests, just to review developer justifications for their use.
  1137.  
  1138. Perhaps it&#039;s time to try again, as now Apple has an &quot;upon request&quot; entitlement for FinanceKit, cf: https://forums.developer.apple.com/forums/thread/746770]]></description>
  1139. <content:encoded><![CDATA[<p>TextExpander faced this same problem back in 2012:</p>
  1140. <p><a href="https://mjtsai.com/blog/2012/06/22/textexpander-4-leaves-mac-app-store/" rel="ugc">https://mjtsai.com/blog/2012/06/22/textexpander-4-leaves-mac-app-store/</a></p>
  1141. <p>I filed a feature request for an entitlement for CGEventTaps back when Sandboxing was introduced. I lobbied Ivan Krstić after his session on Sandboxing at WWDC. If I recall correctly, the main objection was that Apple had no means to limit entitlement requests, just to review developer justifications for their use.</p>
  1142. <p>Perhaps it's time to try again, as now Apple has an "upon request" entitlement for FinanceKit, cf: <a href="https://forums.developer.apple.com/forums/thread/746770" rel="nofollow ugc">https://forums.developer.apple.com/forums/thread/746770</a></p>
  1143. ]]></content:encoded>
  1144. </item>
  1145. <item>
  1146. <title>
  1147. Comment on U.S. Sues Apple Over iPhone Monopoly by Kristoffer </title>
  1148. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4060173</link>
  1149.  
  1150. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  1151. <pubDate>Mon, 25 Mar 2024 14:37:25 +0000</pubDate>
  1152. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4060173</guid>
  1153.  
  1154. <description><![CDATA[There is no need to use analogies at all. We all know what Apple are, how an app marketplace works etc. This is not complicated at all.
  1155.  
  1156. Dump all the failed analogies and just write plainly about things we&#039;re all familiar with.
  1157.  
  1158. Like how Apple won&#039;t approve Spotifys latest update, or tell them why.
  1159. Like how Apple sometimes let things through, and sometimes don&#039;t.
  1160. Like where the expression Sherlocked came from and why.
  1161. Like how no one is talking about forcing happy Apple users to change to a third party app store.
  1162. Or how Aple can force you to update a perfectly fine app to follow some new graphical guidelines. Etc etc.
  1163. Or how they want to charge a fee, and get acces to your book keeping, for things you sell on your own marketplace with your own payment system.
  1164. And it&#039;s not about dragging Apple down to the same level as everyone else (the latest in a line of stupid arguments). It&#039;s about apple letting others build at the same level as they are. Which is perfectly possible
  1165.  
  1166. ANYONE can make headphones that integrate well with a system that they have access to. Same for tap to pay etc. Apples magic sauce is the fact that they&#039;ve put up an artificaila barrier that no-one is allowed to cross.]]></description>
  1167. <content:encoded><![CDATA[<p>There is no need to use analogies at all. We all know what Apple are, how an app marketplace works etc. This is not complicated at all. </p>
  1168. <p>Dump all the failed analogies and just write plainly about things we're all familiar with. </p>
  1169. <p>Like how Apple won't approve Spotifys latest update, or tell them why.<br />
  1170. Like how Apple sometimes let things through, and sometimes don't.<br />
  1171. Like where the expression Sherlocked came from and why.<br />
  1172. Like how no one is talking about forcing happy Apple users to change to a third party app store.<br />
  1173. Or how Aple can force you to update a perfectly fine app to follow some new graphical guidelines. Etc etc.<br />
  1174. Or how they want to charge a fee, and get acces to your book keeping, for things you sell on your own marketplace with your own payment system.<br />
  1175. And it's not about dragging Apple down to the same level as everyone else (the latest in a line of stupid arguments). It's about apple letting others build at the same level as they are. Which is perfectly possible </p>
  1176. <p>ANYONE can make headphones that integrate well with a system that they have access to. Same for tap to pay etc. Apples magic sauce is the fact that they've put up an artificaila barrier that no-one is allowed to cross.</p>
  1177. ]]></content:encoded>
  1178. </item>
  1179. <item>
  1180. <title>
  1181. Comment on U.S. Sues Apple Over iPhone Monopoly by Sören </title>
  1182. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4060156</link>
  1183.  
  1184. <dc:creator><![CDATA[Sören]]></dc:creator>
  1185. <pubDate>Mon, 25 Mar 2024 13:53:39 +0000</pubDate>
  1186. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4060156</guid>
  1187.  
  1188. <description><![CDATA[&#062;It is not clear to me whether DJ does not understand how smartphones are unlike cars or has deliberately chosen a bad analogy
  1189.  
  1190. The problem is that there _aren&#039;t_ a lot of good analogies out there.
  1191.  
  1192. If we&#039;re gonna stick to cars (which I&#039;m not sure we should), then this is more like Ford only approves certain roads and gas stations, and GM approves _other_ roads and gas stations, and if the roads and gas stations want to operate at a profit, they have to pay Ford a cut. Maybe. Something like that. Meaning: it&#039;s not really about car _accessories_, which are largely optional, so much as it is about _near-essential_ portions of owning a car. You _could_ buy an iPhone and never install an app, but almost nobody does that.]]></description>
  1193. <content:encoded><![CDATA[<p>&gt;It is not clear to me whether DJ does not understand how smartphones are unlike cars or has deliberately chosen a bad analogy</p>
  1194. <p>The problem is that there _aren't_ a lot of good analogies out there.</p>
  1195. <p>If we're gonna stick to cars (which I'm not sure we should), then this is more like Ford only approves certain roads and gas stations, and GM approves _other_ roads and gas stations, and if the roads and gas stations want to operate at a profit, they have to pay Ford a cut. Maybe. Something like that. Meaning: it's not really about car _accessories_, which are largely optional, so much as it is about _near-essential_ portions of owning a car. You _could_ buy an iPhone and never install an app, but almost nobody does that.</p>
  1196. ]]></content:encoded>
  1197. </item>
  1198. <item>
  1199. <title>
  1200. Comment on U.S. Sues Apple Over iPhone Monopoly by Sören </title>
  1201. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4060154</link>
  1202.  
  1203. <dc:creator><![CDATA[Sören]]></dc:creator>
  1204. <pubDate>Mon, 25 Mar 2024 13:47:56 +0000</pubDate>
  1205. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4060154</guid>
  1206.  
  1207. <description><![CDATA[&#062;IMO if you have a platform with a store that sells software that can only run on your platform you have a software market and a monopoly on that market. Having a monopoly is only problematic *if* you control every aspect of distribution and use it to disadvantage competitors and harm customers (I think size of the platform matters so I don’t think whatever is happening on FreeBSD or some obscure Linux distro with a few dozen developers really matters).
  1208.  
  1209. And the reason &quot;size of the platform&quot; matters is because _platforms_ are the real market there. It&#039;s when few vendors control the platform landscape that this becomes a problem. That&#039;s why, even though some people argued even back to the 1990s that the Mac is a monopoly, it doesn&#039;t really matter if you feel that way or not, because the Mac was never the dominant choice. Windows was. Whereas, with Android and iOS, iOS has enough clout that you pretty much _have_ to serve those customers if you&#039;re doing a smartphone app.
  1210.  
  1211. So I don&#039;t disagree with that part; I just think &quot;a software platform is a market&quot; is too facile an argument. The problem is that Apple and Google together control basically the entire smartphone ecosystem. If they didn&#039;t, Apple could be as restrictive as they wanted to be.]]></description>
  1212. <content:encoded><![CDATA[<p>&gt;IMO if you have a platform with a store that sells software that can only run on your platform you have a software market and a monopoly on that market. Having a monopoly is only problematic *if* you control every aspect of distribution and use it to disadvantage competitors and harm customers (I think size of the platform matters so I don’t think whatever is happening on FreeBSD or some obscure Linux distro with a few dozen developers really matters).</p>
  1213. <p>And the reason "size of the platform" matters is because _platforms_ are the real market there. It's when few vendors control the platform landscape that this becomes a problem. That's why, even though some people argued even back to the 1990s that the Mac is a monopoly, it doesn't really matter if you feel that way or not, because the Mac was never the dominant choice. Windows was. Whereas, with Android and iOS, iOS has enough clout that you pretty much _have_ to serve those customers if you're doing a smartphone app.</p>
  1214. <p>So I don't disagree with that part; I just think "a software platform is a market" is too facile an argument. The problem is that Apple and Google together control basically the entire smartphone ecosystem. If they didn't, Apple could be as restrictive as they wanted to be.</p>
  1215. ]]></content:encoded>
  1216. </item>
  1217. <item>
  1218. <title>
  1219. Comment on U.S. Sues Apple Over iPhone Monopoly by eg </title>
  1220. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4060147</link>
  1221.  
  1222. <dc:creator><![CDATA[eg]]></dc:creator>
  1223. <pubDate>Mon, 25 Mar 2024 13:11:56 +0000</pubDate>
  1224. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4060147</guid>
  1225.  
  1226. <description><![CDATA[It is not clear to me whether DJ does not understand how smartphones are unlike cars or has deliberately chosen a bad analogy in order to provide a folksy justification for a defense of Apple in the same way that orthodox neoclassical economists use the fallacious “household budget analogy” to gull the groundlings into believing that fiat currency issuers face a solvency constraint with respect to debts denominated in their own currency of issue.]]></description>
  1227. <content:encoded><![CDATA[<p>It is not clear to me whether DJ does not understand how smartphones are unlike cars or has deliberately chosen a bad analogy in order to provide a folksy justification for a defense of Apple in the same way that orthodox neoclassical economists use the fallacious “household budget analogy” to gull the groundlings into believing that fiat currency issuers face a solvency constraint with respect to debts denominated in their own currency of issue.</p>
  1228. ]]></content:encoded>
  1229. </item>
  1230. <item>
  1231. <title>
  1232. Comment on Digital Services Act Compliance: App Store by Amar </title>
  1233. <link>https://mjtsai.com/blog/2024/03/14/digital-services-act-compliance-app-store/#comment-4060112</link>
  1234.  
  1235. <dc:creator><![CDATA[Amar]]></dc:creator>
  1236. <pubDate>Mon, 25 Mar 2024 09:17:51 +0000</pubDate>
  1237. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42504#comment-4060112</guid>
  1238.  
  1239. <description><![CDATA[@Ralph: Article 29 sounds like the exclusion would apply to the whole platform (in this case the App Store), not to the traders. So I think that once Apple is subject to the rules, that article doesn’t help us.
  1240.  
  1241. As an aside, the wording also makes it ambiguous whether it’s the traders or the platform that have to be micro/small, but that should be moot anyway because neither apply in Apple’s case.]]></description>
  1242. <content:encoded><![CDATA[<p>@Ralph: Article 29 sounds like the exclusion would apply to the whole platform (in this case the App Store), not to the traders. So I think that once Apple is subject to the rules, that article doesn’t help us.</p>
  1243. <p>As an aside, the wording also makes it ambiguous whether it’s the traders or the platform that have to be micro/small, but that should be moot anyway because neither apply in Apple’s case.</p>
  1244. ]]></content:encoded>
  1245. </item>
  1246. <item>
  1247. <title>
  1248. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by Nathan </title>
  1249. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4060072</link>
  1250.  
  1251. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1252. <pubDate>Mon, 25 Mar 2024 05:19:25 +0000</pubDate>
  1253. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4060072</guid>
  1254.  
  1255. <description><![CDATA[@DJ
  1256. Why am I not a normal person in your estimation? I literally listed things I, the consumer, want, so why don&#039;t I matter again?
  1257.  
  1258. Were you around the Apple ecosystem when Apple moaned their was to the DoJ to do something about Microsoft&#039;s dominance in the PC marketplace? If so, why is that okay and not this? And how was that about consumers then, but not about consumers now? Also, where was the hand wringing when the government went after Google for their dominance in search? Why is one company&#039;s market your only concern? Or am I misreading and you think no companies should be regulated? I&#039;m confused here.
  1259.  
  1260. Furthermore, why did Apple get to ride Microsoft&#039;s PC dominance coattails to their own success with the iPod without paying Microsoft 30% of every sale of iTunes content via the install on Windows? Why wasn&#039;t Microsoft owed compensation for owning their platform? Weird right? Guess Apple should have paid a platform fee per install, right? No free rides, right? Airport Utility, QuickTime, Safari, etc should have all owed Microsoft a core platform fee, right?
  1261.  
  1262. Or you know, that was simply normal for how things worked forever on computing platforms, but my first rodeo for computer, portable music player, smartphone, smart watch, router, etc was simply not an Apple device, so maybe I have a different viewpoint of how a healthy market should work. I used to really like Apple devices, but it&#039;s been a long while since I felt good about buying them. Thank goodness for Linux to give me a platform that isn&#039;t beholden to Microsoft or Apple right now. Having said that, don&#039;t get me started about how bad Red Hat (ever since IBM acquired them mind you) had been acting. Good thing I don&#039;t have to deal with Red Hat in my work/home life. I&#039;m a professional kvetcher when it comes to malfeasance from technology companies, I never single out Apple for my complaints.]]></description>
  1263. <content:encoded><![CDATA[<p>@DJ<br />
  1264. Why am I not a normal person in your estimation? I literally listed things I, the consumer, want, so why don't I matter again?</p>
  1265. <p>Were you around the Apple ecosystem when Apple moaned their was to the DoJ to do something about Microsoft's dominance in the PC marketplace? If so, why is that okay and not this? And how was that about consumers then, but not about consumers now? Also, where was the hand wringing when the government went after Google for their dominance in search? Why is one company's market your only concern? Or am I misreading and you think no companies should be regulated? I'm confused here.</p>
  1266. <p>Furthermore, why did Apple get to ride Microsoft's PC dominance coattails to their own success with the iPod without paying Microsoft 30% of every sale of iTunes content via the install on Windows? Why wasn't Microsoft owed compensation for owning their platform? Weird right? Guess Apple should have paid a platform fee per install, right? No free rides, right? Airport Utility, QuickTime, Safari, etc should have all owed Microsoft a core platform fee, right?</p>
  1267. <p>Or you know, that was simply normal for how things worked forever on computing platforms, but my first rodeo for computer, portable music player, smartphone, smart watch, router, etc was simply not an Apple device, so maybe I have a different viewpoint of how a healthy market should work. I used to really like Apple devices, but it's been a long while since I felt good about buying them. Thank goodness for Linux to give me a platform that isn't beholden to Microsoft or Apple right now. Having said that, don't get me started about how bad Red Hat (ever since IBM acquired them mind you) had been acting. Good thing I don't have to deal with Red Hat in my work/home life. I'm a professional kvetcher when it comes to malfeasance from technology companies, I never single out Apple for my complaints.</p>
  1268. ]]></content:encoded>
  1269. </item>
  1270. <item>
  1271. <title>
  1272. Comment on Digital Services Act Compliance: App Store by Ralph </title>
  1273. <link>https://mjtsai.com/blog/2024/03/14/digital-services-act-compliance-app-store/#comment-4060031</link>
  1274.  
  1275. <dc:creator><![CDATA[Ralph]]></dc:creator>
  1276. <pubDate>Mon, 25 Mar 2024 00:13:10 +0000</pubDate>
  1277. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42504#comment-4060031</guid>
  1278.  
  1279. <description><![CDATA[I think a lot of small developers should not have to provide this information.  Looking at Recommendation 2003/361/EC, Article 2 says:
  1280.  
  1281. 3. Within the SME category, a microenterprise is defined as an enterprise which employs fewer than 10 persons and whose annual turnover and/or annual balance sheet total does not exceed EUR 2 million.
  1282.  
  1283. Now going to Regulation 2022/2065 (the DSA), Article 29 says:
  1284.  
  1285. Exclusion for micro and small enterprises
  1286. 1.   This Section shall not apply to providers of online platforms allowing consumers to conclude distance contracts with traders that qualify as micro or small enterprises as defined in Recommendation 2003/361/EC.
  1287.  
  1288. So, I am a solo developer with a lot less than EUR 2M in revenue and assets, so I think I am immune.
  1289.  
  1290. Any thoughts anyone?]]></description>
  1291. <content:encoded><![CDATA[<p>I think a lot of small developers should not have to provide this information.  Looking at Recommendation 2003/361/EC, Article 2 says:</p>
  1292. <p>3. Within the SME category, a microenterprise is defined as an enterprise which employs fewer than 10 persons and whose annual turnover and/or annual balance sheet total does not exceed EUR 2 million.</p>
  1293. <p>Now going to Regulation 2022/2065 (the DSA), Article 29 says:</p>
  1294. <p>Exclusion for micro and small enterprises<br />
  1295. 1.   This Section shall not apply to providers of online platforms allowing consumers to conclude distance contracts with traders that qualify as micro or small enterprises as defined in Recommendation 2003/361/EC.</p>
  1296. <p>So, I am a solo developer with a lot less than EUR 2M in revenue and assets, so I think I am immune.</p>
  1297. <p>Any thoughts anyone?</p>
  1298. ]]></content:encoded>
  1299. </item>
  1300. <item>
  1301. <title>
  1302. Comment on U.S. Sues Apple Over iPhone Monopoly by ObjC4Life </title>
  1303. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4060030</link>
  1304.  
  1305. <dc:creator><![CDATA[ObjC4Life]]></dc:creator>
  1306. <pubDate>Mon, 25 Mar 2024 00:12:09 +0000</pubDate>
  1307. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4060030</guid>
  1308.  
  1309. <description><![CDATA[@Mark +1
  1310.  
  1311. IMO if you have a platform with a store that sells software that can only run on your platform you have a software market and a monopoly on that market. Having a monopoly is only problematic *if* you control every aspect of distribution and use it to disadvantage competitors and harm customers (I think size of the platform matters so I don’t think whatever is happening on FreeBSD or some obscure Linux distro with a few dozen developers really matters). Software platforms really aren’t comparable to cupboards. There are plenty of woodworkers out there that can build a cupboard of any size. Not really the same thing as spending years writing a complex iOS app that you just can’t take with you if you don’t like how Apple is treating you as a partner.]]></description>
  1312. <content:encoded><![CDATA[<p>@Mark +1</p>
  1313. <p>IMO if you have a platform with a store that sells software that can only run on your platform you have a software market and a monopoly on that market. Having a monopoly is only problematic *if* you control every aspect of distribution and use it to disadvantage competitors and harm customers (I think size of the platform matters so I don’t think whatever is happening on FreeBSD or some obscure Linux distro with a few dozen developers really matters). Software platforms really aren’t comparable to cupboards. There are plenty of woodworkers out there that can build a cupboard of any size. Not really the same thing as spending years writing a complex iOS app that you just can’t take with you if you don’t like how Apple is treating you as a partner.</p>
  1314. ]]></content:encoded>
  1315. </item>
  1316. <item>
  1317. <title>
  1318. Comment on How to Choose and Customize a Mechanical Keyboard by Tamim Likhon </title>
  1319. <link>https://mjtsai.com/blog/2024/02/01/how-to-choose-and-customize-a-mechanical-keyboard/#comment-4059977</link>
  1320.  
  1321. <dc:creator><![CDATA[Tamim Likhon]]></dc:creator>
  1322. <pubDate>Sun, 24 Mar 2024 18:42:17 +0000</pubDate>
  1323. <guid isPermaLink="false">https://mjtsai.com/blog/?p=41972#comment-4059977</guid>
  1324.  
  1325. <description><![CDATA[I also have an article where I talk about Linear switches.]]></description>
  1326. <content:encoded><![CDATA[<p>I also have an article where I talk about Linear switches.</p>
  1327. ]]></content:encoded>
  1328. </item>
  1329. <item>
  1330. <title>
  1331. Comment on U.S. Sues Apple Over iPhone Monopoly by Marc </title>
  1332. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059944</link>
  1333.  
  1334. <dc:creator><![CDATA[Marc]]></dc:creator>
  1335. <pubDate>Sun, 24 Mar 2024 15:01:44 +0000</pubDate>
  1336. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059944</guid>
  1337.  
  1338. <description><![CDATA[As cupboard manufacturer, it&#039;s easy to create smaller and larger cupboards - same material, same tools, same knowledge. But you wouldn&#039;t start building car seats - different materials (APIs), different tools (IDEs), different knowledge.
  1339. Of course, almost all market segmentations are artificial, but when you have hundreds of millions of customers clearly divided into two camps then it&#039;s inevitable these are different markets, not only segments.
  1340. Now Apple itself argues, that iPadOS is a different market than iOS, and requested the EU not to treat them as gatekeeper for iPadOS. IMHO that would make a perfect case for a segment, since here developers use the same APIs, the same tools, the same knowledge to build apps for pretty similar devices where the most significant difference is just the screen size. We&#039;ll see how this plays out...]]></description>
  1341. <content:encoded><![CDATA[<p>As cupboard manufacturer, it's easy to create smaller and larger cupboards - same material, same tools, same knowledge. But you wouldn't start building car seats - different materials (APIs), different tools (IDEs), different knowledge.<br />
  1342. Of course, almost all market segmentations are artificial, but when you have hundreds of millions of customers clearly divided into two camps then it's inevitable these are different markets, not only segments.<br />
  1343. Now Apple itself argues, that iPadOS is a different market than iOS, and requested the EU not to treat them as gatekeeper for iPadOS. IMHO that would make a perfect case for a segment, since here developers use the same APIs, the same tools, the same knowledge to build apps for pretty similar devices where the most significant difference is just the screen size. We'll see how this plays out...</p>
  1344. ]]></content:encoded>
  1345. </item>
  1346. <item>
  1347. <title>
  1348. Comment on Apple Manuals, Specs, and Downloads by Sebby </title>
  1349. <link>https://mjtsai.com/blog/2024/03/22/apple-manuals-specs-and-downloads/#comment-4059943</link>
  1350.  
  1351. <dc:creator><![CDATA[Sebby]]></dc:creator>
  1352. <pubDate>Sun, 24 Mar 2024 14:36:27 +0000</pubDate>
  1353. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42612#comment-4059943</guid>
  1354.  
  1355. <description><![CDATA[It&#039;s nice.]]></description>
  1356. <content:encoded><![CDATA[<p>It's nice.</p>
  1357. ]]></content:encoded>
  1358. </item>
  1359. <item>
  1360. <title>
  1361. Comment on U.S. Sues Apple Over iPhone Monopoly by Sören </title>
  1362. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059939</link>
  1363.  
  1364. <dc:creator><![CDATA[Sören]]></dc:creator>
  1365. <pubDate>Sun, 24 Mar 2024 14:19:51 +0000</pubDate>
  1366. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059939</guid>
  1367.  
  1368. <description><![CDATA[&#062;If you are a hardware manufacturer that creates pocket computers, yes. You can sell a compelling phone to all people world-wide.
  1369. If you are a software developer, no. The markets for iOS apps and Android apps do not overlap
  1370.  
  1371. This suggests to me &quot;operating systems are bad, actually&quot;. Who knew the developers of FreeBSD are monopolists?
  1372.  
  1373. Apple&#039;s behavior isn&#039;t problematic because iPhones don&#039;t run Android apps. It&#039;s problematic because people rely on effectively one of just two choices. Not owning a phone is impractical.
  1374.  
  1375. This would all be less of a problem if more smartphone platforms existed. Firefox OS, Maemo, whatever. But they don&#039;t, because software developers would rather that consumers have even _fewer_ choices to run software on. Regulators _could_ flip that entire logic around and mandate that commercial software exist on at least three platforms. Then, companies like Apple and Google would&#039;ve had less market power.
  1376.  
  1377. Instead, they&#039;ve learnt bupkis from 2000.
  1378.  
  1379. &#062;The markets for iOS apps and Android apps do not overlap - you cannot sell 1 product to the same customers. iPhone owners will not buy Android apps, and Android owners will not buy iOS apps.
  1380.  
  1381. Does compatibility a market make? Is &quot;cupboards that happen to fit in the space in the corner of your living room&quot; a market? Because by your argument, they should be, since you aren&#039;t going to buy a cupboard that&#039;s too large to fit.
  1382.  
  1383. Segments aren&#039;t the same thing as markets.]]></description>
  1384. <content:encoded><![CDATA[<p>&gt;If you are a hardware manufacturer that creates pocket computers, yes. You can sell a compelling phone to all people world-wide.<br />
  1385. If you are a software developer, no. The markets for iOS apps and Android apps do not overlap </p>
  1386. <p>This suggests to me "operating systems are bad, actually". Who knew the developers of FreeBSD are monopolists?</p>
  1387. <p>Apple's behavior isn't problematic because iPhones don't run Android apps. It's problematic because people rely on effectively one of just two choices. Not owning a phone is impractical.</p>
  1388. <p>This would all be less of a problem if more smartphone platforms existed. Firefox OS, Maemo, whatever. But they don't, because software developers would rather that consumers have even _fewer_ choices to run software on. Regulators _could_ flip that entire logic around and mandate that commercial software exist on at least three platforms. Then, companies like Apple and Google would've had less market power.</p>
  1389. <p>Instead, they've learnt bupkis from 2000.</p>
  1390. <p>&gt;The markets for iOS apps and Android apps do not overlap - you cannot sell 1 product to the same customers. iPhone owners will not buy Android apps, and Android owners will not buy iOS apps.</p>
  1391. <p>Does compatibility a market make? Is "cupboards that happen to fit in the space in the corner of your living room" a market? Because by your argument, they should be, since you aren't going to buy a cupboard that's too large to fit.</p>
  1392. <p>Segments aren't the same thing as markets.</p>
  1393. ]]></content:encoded>
  1394. </item>
  1395. <item>
  1396. <title>
  1397. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by Kristoffer </title>
  1398. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4059895</link>
  1399.  
  1400. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  1401. <pubDate>Sun, 24 Mar 2024 10:03:45 +0000</pubDate>
  1402. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4059895</guid>
  1403.  
  1404. <description><![CDATA[What he wants us to be able to build whatever pool device he wants, and sell them in his own store.
  1405.  
  1406. Wether you but it or not is your decision.
  1407.  
  1408. Spotify wants to be able to publish an update and get a swift and clear handling of that update. Apple are an abusiven that claim to curate but don&#039;t.]]></description>
  1409. <content:encoded><![CDATA[<p>What he wants us to be able to build whatever pool device he wants, and sell them in his own store.</p>
  1410. <p>Wether you but it or not is your decision.</p>
  1411. <p>Spotify wants to be able to publish an update and get a swift and clear handling of that update. Apple are an abusiven that claim to curate but don't.</p>
  1412. ]]></content:encoded>
  1413. </item>
  1414. <item>
  1415. <title>
  1416. Comment on _eventFirstResponderChainDescription by Rob Mayoff </title>
  1417. <link>https://mjtsai.com/blog/2024/03/22/_eventfirstresponderchaindescription/#comment-4059830</link>
  1418.  
  1419. <dc:creator><![CDATA[Rob Mayoff]]></dc:creator>
  1420. <pubDate>Sun, 24 Mar 2024 04:20:22 +0000</pubDate>
  1421. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42614#comment-4059830</guid>
  1422.  
  1423. <description><![CDATA[Nice find. This is a little simpler way to print the value:
  1424.  
  1425. print(NSApp.value(forKey: &quot;_eventFirstResponderChainDescription&quot;))
  1426.  
  1427. And that _NS_4445425547 thing is really neat!]]></description>
  1428. <content:encoded><![CDATA[<p>Nice find. This is a little simpler way to print the value:</p>
  1429. <p>print(NSApp.value(forKey: "_eventFirstResponderChainDescription"))</p>
  1430. <p>And that _NS_4445425547 thing is really neat!</p>
  1431. ]]></content:encoded>
  1432. </item>
  1433. <item>
  1434. <title>
  1435. Comment on U.S. Sues Apple Over iPhone Monopoly by Marc </title>
  1436. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059820</link>
  1437.  
  1438. <dc:creator><![CDATA[Marc]]></dc:creator>
  1439. <pubDate>Sun, 24 Mar 2024 03:08:27 +0000</pubDate>
  1440. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059820</guid>
  1441.  
  1442. <description><![CDATA[@Sören &#062; I’m with Gruber here. The market is “pocket computers that can also make phone calls”, not “computers that run iOS apps”.
  1443. If you are a hardware manufacturer that creates pocket computers, yes. You can sell a compelling phone to all people world-wide.
  1444. If you are a software developer, no. The markets for iOS apps and Android apps do not overlap - you cannot sell 1 product to the same customers. iPhone owners will not buy Android apps, and Android owners will not buy iOS apps. And while neither Google nor Samsung or any other company has a monopoly for Android app sales (you can offer your app e.g. in the F-Droid or Amazon store), Apple clearly has a monopoly in the iOS app market, since you can only offer your software to iPhone users in the AppStore. Apple is the gatekeeper everyone must pay who wants to sell software and digital goods to people that bought an iPhone.]]></description>
  1445. <content:encoded><![CDATA[<p>@Sören &gt; I’m with Gruber here. The market is “pocket computers that can also make phone calls”, not “computers that run iOS apps”.<br />
  1446. If you are a hardware manufacturer that creates pocket computers, yes. You can sell a compelling phone to all people world-wide.<br />
  1447. If you are a software developer, no. The markets for iOS apps and Android apps do not overlap - you cannot sell 1 product to the same customers. iPhone owners will not buy Android apps, and Android owners will not buy iOS apps. And while neither Google nor Samsung or any other company has a monopoly for Android app sales (you can offer your app e.g. in the F-Droid or Amazon store), Apple clearly has a monopoly in the iOS app market, since you can only offer your software to iPhone users in the AppStore. Apple is the gatekeeper everyone must pay who wants to sell software and digital goods to people that bought an iPhone.</p>
  1448. ]]></content:encoded>
  1449. </item>
  1450. <item>
  1451. <title>
  1452. Comment on U.S. Sues Apple Over iPhone Monopoly by Marc </title>
  1453. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059817</link>
  1454.  
  1455. <dc:creator><![CDATA[Marc]]></dc:creator>
  1456. <pubDate>Sun, 24 Mar 2024 02:46:50 +0000</pubDate>
  1457. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059817</guid>
  1458.  
  1459. <description><![CDATA[@DJ &quot;iPhones and Android phones are &#039;smart phones&#039;. They are both &#039;brands&#039;, and they compete in the &#039;smart phone market&#039;. I don&#039;t know how much simpler it can be.&quot;
  1460. Right, but I don&#039;t sell &quot;smart phones&quot;, I sell &quot;smart phone apps&quot;. I don&#039;t compete with Apple, Samsung, ... which sell similar hand-held mini-computers.
  1461. To customers using an iPhone I can only sell iOS apps. And I would need to learn a new programming language and write code for different APIs to be able to develop an app that I could sell to customers using an Android phone. Even you should see that those are not the same customers - thus these are different markets which do not overlap.]]></description>
  1462. <content:encoded><![CDATA[<p>@DJ "iPhones and Android phones are 'smart phones'. They are both 'brands', and they compete in the 'smart phone market'. I don't know how much simpler it can be."<br />
  1463. Right, but I don't sell "smart phones", I sell "smart phone apps". I don't compete with Apple, Samsung, ... which sell similar hand-held mini-computers.<br />
  1464. To customers using an iPhone I can only sell iOS apps. And I would need to learn a new programming language and write code for different APIs to be able to develop an app that I could sell to customers using an Android phone. Even you should see that those are not the same customers - thus these are different markets which do not overlap.</p>
  1465. ]]></content:encoded>
  1466. </item>
  1467. <item>
  1468. <title>
  1469. Comment on DMA Compliance: Default App Controls and NFC by Marc </title>
  1470. <link>https://mjtsai.com/blog/2024/01/26/dma-compliance-default-app-controls/#comment-4059811</link>
  1471.  
  1472. <dc:creator><![CDATA[Marc]]></dc:creator>
  1473. <pubDate>Sun, 24 Mar 2024 02:01:12 +0000</pubDate>
  1474. <guid isPermaLink="false">https://mjtsai.com/blog/?p=41882#comment-4059811</guid>
  1475.  
  1476. <description><![CDATA[The DMA demands gatekeepers to &quot;provide choice screens for key services&quot;
  1477. https://ec.europa.eu/commission/presscorner/api/files/document/print/en/qanda_20_2349/QANDA_20_2349_EN.pdf
  1478. Jeff is absolutely right, there must be more than just for the browser.
  1479.  
  1480. And second, &quot;electronic payments&quot; is more than just card payments. GNU Taler, for instance, is a payment system where digital tokens/&quot;coins&quot; are sent from the payer&#039;s wallet to the payee&#039;s wallet - no cards involved at all. Apple will have to enable NFC tap-to-pay for this also...]]></description>
  1481. <content:encoded><![CDATA[<p>The DMA demands gatekeepers to "provide choice screens for key services"<br />
  1482. <a href="https://ec.europa.eu/commission/presscorner/api/files/document/print/en/qanda_20_2349/QANDA_20_2349_EN.pdf" rel="nofollow ugc">https://ec.europa.eu/commission/presscorner/api/files/document/print/en/qanda_20_2349/QANDA_20_2349_EN.pdf</a><br />
  1483. Jeff is absolutely right, there must be more than just for the browser.</p>
  1484. <p>And second, "electronic payments" is more than just card payments. GNU Taler, for instance, is a payment system where digital tokens/"coins" are sent from the payer's wallet to the payee's wallet - no cards involved at all. Apple will have to enable NFC tap-to-pay for this also...</p>
  1485. ]]></content:encoded>
  1486. </item>
  1487. <item>
  1488. <title>
  1489. Comment on _eventFirstResponderChainDescription by bob </title>
  1490. <link>https://mjtsai.com/blog/2024/03/22/_eventfirstresponderchaindescription/#comment-4059739</link>
  1491.  
  1492. <dc:creator><![CDATA[bob]]></dc:creator>
  1493. <pubDate>Sat, 23 Mar 2024 19:37:56 +0000</pubDate>
  1494. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42614#comment-4059739</guid>
  1495.  
  1496. <description><![CDATA[Florian, wow, that&#039;s great! How did I never know about that?!
  1497.  
  1498. It&#039;s such a shame tn2124 was killed.
  1499.  
  1500. http://web.archive.org/web/20101206131250/http://developer.apple.com/library/mac/#technotes/tn2004/tn2124.html]]></description>
  1501. <content:encoded><![CDATA[<p>Florian, wow, that's great! How did I never know about that?!</p>
  1502. <p>It's such a shame tn2124 was killed.</p>
  1503. <p><a href="http://web.archive.org/web/20101206131250/http://developer.apple.com/library/mac/#technotes/tn2004/tn2124.html" rel="nofollow ugc">http://web.archive.org/web/20101206131250/http://developer.apple.com/library/mac/#technotes/tn2004/tn2124.html</a></p>
  1504. ]]></content:encoded>
  1505. </item>
  1506. <item>
  1507. <title>
  1508. Comment on _eventFirstResponderChainDescription by Florian </title>
  1509. <link>https://mjtsai.com/blog/2024/03/22/_eventfirstresponderchaindescription/#comment-4059578</link>
  1510.  
  1511. <dc:creator><![CDATA[Florian]]></dc:creator>
  1512. <pubDate>Sat, 23 Mar 2024 12:57:36 +0000</pubDate>
  1513. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42614#comment-4059578</guid>
  1514.  
  1515. <description><![CDATA[I always pass `-_NS_4445425547 YES` when debugging from Xcode, which gives a nice extra menu item <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f41e.png" alt="🐞" class="wp-smiley" style="height: 1em; max-height: 1em;" /> with — among other goodies — a window that lists the current responder chain.]]></description>
  1516. <content:encoded><![CDATA[<p>I always pass `-_NS_4445425547 YES` when debugging from Xcode, which gives a nice extra menu item 🐞 with — among other goodies — a window that lists the current responder chain.</p>
  1517. ]]></content:encoded>
  1518. </item>
  1519. <item>
  1520. <title>
  1521. Comment on U.S. Sues Apple Over iPhone Monopoly by Sören </title>
  1522. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059522</link>
  1523.  
  1524. <dc:creator><![CDATA[Sören]]></dc:creator>
  1525. <pubDate>Sat, 23 Mar 2024 11:08:20 +0000</pubDate>
  1526. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059522</guid>
  1527.  
  1528. <description><![CDATA[&#062;I wish Congress had passed better laws
  1529.  
  1530. Yep. (Well, from a EU perspective, more like: I wish we’d learnt more lessons from the ca-2000 Microsoft legislation on how to regulate platform companies.)
  1531.  
  1532. &#062;and that Apple hadn’t acted so badly.
  1533.  
  1534. Indeed.
  1535.  
  1536. But also:
  1537.  
  1538. &#062;Defining the iPhone as a monopoly when it has somewhere around 55 percent market share in the U.S. is obviously the first thing the DOJ needs to prove.
  1539.  
  1540. I’m with Gruber here. The market is “pocket computers that can also make phone calls”, not “computers that run iOS apps”.
  1541.  
  1542. But I also, not being a lawyer and certainly not a US lawyer, I find this focus on “monopoly” silly. It’s about _market dominance_, and Apple and Google form a _duopoly_ that essentially controls the market and dictates the terms, much like Windows formed a quasi-monopoly and did twenty-five years ago.
  1543.  
  1544. And _that_, coupled with _this_:
  1545.  
  1546. &#062;The smartphone revolution was so successful that the product has become table stakes for modern life.
  1547.  
  1548. Is where the problem lies. Squibbling over “is it a monopoly” is besides the point; “does Apple wield a significant amount of control over our lives” and “should the state, therefore, exert some regulation” are the questions, and I think it’s fair to answer them with “yes”. (Leaving aside for a second that the US Congress seems institutionally incapable of passing laws.)
  1549.  
  1550. I’ve started listening to ATP’s take, and it’s funny how I go from nodding in agreement to rolling my eyes in disagreement, back and forth.
  1551.  
  1552. For example!
  1553.  
  1554. They argue about the Watch thing. If I were the DoJ, personally, I’d have picked AirPods as the better example, but Watch works as well. I own an Apple Watch and AirPods Pro 2, and am reasonably satisfied with them.
  1555.  
  1556. Now, some of that satisfaction comes from tight system integration, which on the _one_ hand is a sign of Apple’s software+hardware engineering success, something they get to be proud of, and something that’s classic Apple “it just works” (except when it doesn’t). Yet on the _other_ hand, they don’t _just_ integrate the pieces of hardware. They don’t _just_ make private APIs to make that possible for themselves. They then _also_ lock down the system so that third parties _cannot_ make equivalent APIs for themselves, except for on the Mac, and even there, decreasingly so.
  1557.  
  1558. A company like Samsung or whatever _can’t_ decide “let’s make the Gear Watch Whatever and Gear Beats Boomboom and make them integrate just as well or even better on iOS as the Apple Watch and AirPods do”. Apple argues this — Samsung being unable to make a GearBackgroundService that does things like detecting when your device comes near, offering to pair, switching music to it, all those things — is in part for privacy and security, and that’s not entirely wrong, but it _also_, insidiously, reinforces Apple’s market position by creating platform lock-in, and providing a free flow of additional mutual revenue. AirPods go old? Time for new headphones. Oops, can’t shop elsewhere because you have an iPhone. iPhone goes old? Time for a new phone. Oops, no alternative unless you also want to give up on the same level of headphone experience, or replace them as well.
  1559.  
  1560. I’m a bit frustrated that the ATP folks can’t see this problem. Is it a huge problem in the grand scheme of things? Perhaps not. Is it one where requiring Apple to provide APIs that are at the same level as their own integration, and/or requiring them to offer an opt-in entitlement where a third party could make such a service would help? I think so!
  1561.  
  1562. And I’d probably _still_ buy AirPods, because I think they’re quite good. But I’d do so more happily, as I’d feel less compelled to.]]></description>
  1563. <content:encoded><![CDATA[<p>&gt;I wish Congress had passed better laws</p>
  1564. <p>Yep. (Well, from a EU perspective, more like: I wish we’d learnt more lessons from the ca-2000 Microsoft legislation on how to regulate platform companies.)</p>
  1565. <p>&gt;and that Apple hadn’t acted so badly.</p>
  1566. <p>Indeed.</p>
  1567. <p>But also:</p>
  1568. <p>&gt;Defining the iPhone as a monopoly when it has somewhere around 55 percent market share in the U.S. is obviously the first thing the DOJ needs to prove.</p>
  1569. <p>I’m with Gruber here. The market is “pocket computers that can also make phone calls”, not “computers that run iOS apps”.</p>
  1570. <p>But I also, not being a lawyer and certainly not a US lawyer, I find this focus on “monopoly” silly. It’s about _market dominance_, and Apple and Google form a _duopoly_ that essentially controls the market and dictates the terms, much like Windows formed a quasi-monopoly and did twenty-five years ago.</p>
  1571. <p>And _that_, coupled with _this_:</p>
  1572. <p>&gt;The smartphone revolution was so successful that the product has become table stakes for modern life.</p>
  1573. <p>Is where the problem lies. Squibbling over “is it a monopoly” is besides the point; “does Apple wield a significant amount of control over our lives” and “should the state, therefore, exert some regulation” are the questions, and I think it’s fair to answer them with “yes”. (Leaving aside for a second that the US Congress seems institutionally incapable of passing laws.)</p>
  1574. <p>I’ve started listening to ATP’s take, and it’s funny how I go from nodding in agreement to rolling my eyes in disagreement, back and forth.</p>
  1575. <p>For example!</p>
  1576. <p>They argue about the Watch thing. If I were the DoJ, personally, I’d have picked AirPods as the better example, but Watch works as well. I own an Apple Watch and AirPods Pro 2, and am reasonably satisfied with them.</p>
  1577. <p>Now, some of that satisfaction comes from tight system integration, which on the _one_ hand is a sign of Apple’s software+hardware engineering success, something they get to be proud of, and something that’s classic Apple “it just works” (except when it doesn’t). Yet on the _other_ hand, they don’t _just_ integrate the pieces of hardware. They don’t _just_ make private APIs to make that possible for themselves. They then _also_ lock down the system so that third parties _cannot_ make equivalent APIs for themselves, except for on the Mac, and even there, decreasingly so.</p>
  1578. <p>A company like Samsung or whatever _can’t_ decide “let’s make the Gear Watch Whatever and Gear Beats Boomboom and make them integrate just as well or even better on iOS as the Apple Watch and AirPods do”. Apple argues this — Samsung being unable to make a GearBackgroundService that does things like detecting when your device comes near, offering to pair, switching music to it, all those things — is in part for privacy and security, and that’s not entirely wrong, but it _also_, insidiously, reinforces Apple’s market position by creating platform lock-in, and providing a free flow of additional mutual revenue. AirPods go old? Time for new headphones. Oops, can’t shop elsewhere because you have an iPhone. iPhone goes old? Time for a new phone. Oops, no alternative unless you also want to give up on the same level of headphone experience, or replace them as well.</p>
  1579. <p>I’m a bit frustrated that the ATP folks can’t see this problem. Is it a huge problem in the grand scheme of things? Perhaps not. Is it one where requiring Apple to provide APIs that are at the same level as their own integration, and/or requiring them to offer an opt-in entitlement where a third party could make such a service would help? I think so!</p>
  1580. <p>And I’d probably _still_ buy AirPods, because I think they’re quite good. But I’d do so more happily, as I’d feel less compelled to.</p>
  1581. ]]></content:encoded>
  1582. </item>
  1583. <item>
  1584. <title>
  1585. Comment on U.S. Sues Apple Over iPhone Monopoly by Kristoffer </title>
  1586. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059416</link>
  1587.  
  1588. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  1589. <pubDate>Sat, 23 Mar 2024 07:38:48 +0000</pubDate>
  1590. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059416</guid>
  1591.  
  1592. <description><![CDATA[@DJ what do you men by Android ad based echo system?
  1593.  
  1594. I see more ads on my MacBook, the constant Hey, get iCooud, nagging mostly, but also Get, turn on time machine!
  1595.  
  1596. There are some ads in the Google news feed I guess. It&#039;s that what you meant?
  1597.  
  1598. Either way, of Apple shared your confidence in their superiority they wouldn&#039;t be so he&#039;ll bent on increasing switching costs and lick in.
  1599.  
  1600. It has taken a lot of pressure(outside of China naturally, in China Apple complied in the blink of an eye) to get Apple to consider RCS
  1601.  
  1602. A feature that will improve the experience for their own users. But, as Gruber put it &quot;Apple puts themselves first, and their users second&quot;]]></description>
  1603. <content:encoded><![CDATA[<p>@DJ what do you men by Android ad based echo system?</p>
  1604. <p>I see more ads on my MacBook, the constant Hey, get iCooud, nagging mostly, but also Get, turn on time machine!</p>
  1605. <p>There are some ads in the Google news feed I guess. It's that what you meant?</p>
  1606. <p>Either way, of Apple shared your confidence in their superiority they wouldn't be so he'll bent on increasing switching costs and lick in.</p>
  1607. <p>It has taken a lot of pressure(outside of China naturally, in China Apple complied in the blink of an eye) to get Apple to consider RCS</p>
  1608. <p>A feature that will improve the experience for their own users. But, as Gruber put it "Apple puts themselves first, and their users second"</p>
  1609. ]]></content:encoded>
  1610. </item>
  1611. <item>
  1612. <title>
  1613. Comment on Epic Challenges External Link Rules and Commission by Kristoffer </title>
  1614. <link>https://mjtsai.com/blog/2024/03/22/epic-challenges-external-link-rules-and-commission/#comment-4059407</link>
  1615.  
  1616. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  1617. <pubDate>Sat, 23 Mar 2024 07:26:19 +0000</pubDate>
  1618. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42610#comment-4059407</guid>
  1619.  
  1620. <description><![CDATA[There&#039;s blood in the water]]></description>
  1621. <content:encoded><![CDATA[<p>There's blood in the water</p>
  1622. ]]></content:encoded>
  1623. </item>
  1624. <item>
  1625. <title>
  1626. Comment on U.S. Sues Apple Over iPhone Monopoly by ObjC4Life </title>
  1627. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059260</link>
  1628.  
  1629. <dc:creator><![CDATA[ObjC4Life]]></dc:creator>
  1630. <pubDate>Sat, 23 Mar 2024 02:43:22 +0000</pubDate>
  1631. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059260</guid>
  1632.  
  1633. <description><![CDATA[&#062; The whole idea that iOS (platform, product, whatever) is its own market is just wrong. The market for iPhones is &#039;smart phones&#039;, just as the market for Macs is &#039;desktop computers&#039; and not &#039;macOS computers&#039;, and the market for Porsches is &#039;cars&#039;, not &#039;Porsche cars&#039;. If I buy a Porsche, I don&#039;t expect to be able to swap in the front quarters from a Buick.
  1634.  
  1635. A market is a place where goods and services are sold (like the App Store where software is sold for real money). A porsche is a car and as far as I know there isn’t an App Store built into the dashboard so I don’t really understand your analogy at all? Software created by third party devs are not car parts so I don’t get your point about swapping parts from a Buick in a Porsche. If you create a marketplace you have a market. As far as I know Porsche doesn’t have a developer program or App Store but you can get new tires from anywhere you want.
  1636.  
  1637. No other general purpose computing platform is as locked down as iOS. Apple has 100% control of app distribution on iOS and demands revenue sharing for every install. Whether the existence of Android is enough for this to not be considered a monopoly is something for courts to determine. IMO if it is not considered a monopoly i think our laws need to be updated for the digital age.]]></description>
  1638. <content:encoded><![CDATA[<p>&gt; The whole idea that iOS (platform, product, whatever) is its own market is just wrong. The market for iPhones is 'smart phones', just as the market for Macs is 'desktop computers' and not 'macOS computers', and the market for Porsches is 'cars', not 'Porsche cars'. If I buy a Porsche, I don't expect to be able to swap in the front quarters from a Buick.</p>
  1639. <p>A market is a place where goods and services are sold (like the App Store where software is sold for real money). A porsche is a car and as far as I know there isn’t an App Store built into the dashboard so I don’t really understand your analogy at all? Software created by third party devs are not car parts so I don’t get your point about swapping parts from a Buick in a Porsche. If you create a marketplace you have a market. As far as I know Porsche doesn’t have a developer program or App Store but you can get new tires from anywhere you want.</p>
  1640. <p> No other general purpose computing platform is as locked down as iOS. Apple has 100% control of app distribution on iOS and demands revenue sharing for every install. Whether the existence of Android is enough for this to not be considered a monopoly is something for courts to determine. IMO if it is not considered a monopoly i think our laws need to be updated for the digital age.</p>
  1641. ]]></content:encoded>
  1642. </item>
  1643. <item>
  1644. <title>
  1645. Comment on FastSpring Risk Screening by Miller </title>
  1646. <link>https://mjtsai.com/blog/2023/12/07/fastspring-risk-screening/#comment-4059259</link>
  1647.  
  1648. <dc:creator><![CDATA[Miller]]></dc:creator>
  1649. <pubDate>Sat, 23 Mar 2024 02:35:29 +0000</pubDate>
  1650. <guid isPermaLink="false">https://mjtsai.com/blog/?p=41338#comment-4059259</guid>
  1651.  
  1652. <description><![CDATA[After two weeks of giving them a negative review on Trustpilot, I finally received my money today.]]></description>
  1653. <content:encoded><![CDATA[<p>After two weeks of giving them a negative review on Trustpilot, I finally received my money today.</p>
  1654. ]]></content:encoded>
  1655. </item>
  1656. <item>
  1657. <title>
  1658. Comment on U.S. Sues Apple Over iPhone Monopoly by Someone </title>
  1659. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059240</link>
  1660.  
  1661. <dc:creator><![CDATA[Someone]]></dc:creator>
  1662. <pubDate>Sat, 23 Mar 2024 01:38:27 +0000</pubDate>
  1663. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059240</guid>
  1664.  
  1665. <description><![CDATA[@DJ It doesn&#039;t really matter what your logic is for why iOS should, or should not be a market unto itself, or should be part of a larger meta-market of &quot;smartphones&quot;, the fact is multiple competition regulatory jurisdictions world wide have ruled that iOS *is* a market unto itself, and that Apple&#039;s behaviour is going to be judged in that context.]]></description>
  1666. <content:encoded><![CDATA[<p>@DJ It doesn't really matter what your logic is for why iOS should, or should not be a market unto itself, or should be part of a larger meta-market of "smartphones", the fact is multiple competition regulatory jurisdictions world wide have ruled that iOS *is* a market unto itself, and that Apple's behaviour is going to be judged in that context.</p>
  1667. ]]></content:encoded>
  1668. </item>
  1669. <item>
  1670. <title>
  1671. Comment on U.S. Sues Apple Over iPhone Monopoly by Sam Rowlands </title>
  1672. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059235</link>
  1673.  
  1674. <dc:creator><![CDATA[Sam Rowlands]]></dc:creator>
  1675. <pubDate>Sat, 23 Mar 2024 01:14:09 +0000</pubDate>
  1676. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059235</guid>
  1677.  
  1678. <description><![CDATA[I put off switching to Android because of all the stories. Android is slow, Android has terrible battery life, Android is full of malware and Ads.
  1679.  
  1680. I got so frustrated waiting for Apple to fix bugs that affected me on a daily basis, upgrading every year, only to find more things that no longer work. So I did it, and I&#039;m glad I did.
  1681.  
  1682. At first I wasn&#039;t sure about it at all, I mean it does everything the same, it even kinda looks similar in places, but it wasn&#039;t iOS.
  1683.  
  1684. Performance. If you watch enough comparative reviews, you&#039;ll see Snapdragon chips trade blows with Apple&#039;s A series, A series better here, while SD better there.
  1685.  
  1686. Battery life... I have a two year Zenfone 9 and I charge it every 3 days. I had to use it extensively yesterday, and got home with 50% battery (it stated at 90%).
  1687.  
  1688. Malware. I&#039;ve not encountered any in the 3 years I&#039;ve been using Android. I&#039;m not saying there isn&#039;t any as Google regularly reports how much crap they remove from their Play Store.
  1689.  
  1690. Ads. I&#039;m pretty certain that if you buy a $100 Android phone, you&#039;re going to get Ads to subsidize the cost, but I&#039;ve never seen an Ad in the last 3 years (both of my phones have been Asus).
  1691.  
  1692. I would recommend anyone who&#039;s slightly interested in switching, to try it themselves. Manufacturers sell refurbished devices, so you can score a 2 or 3 year old model for cheaper and still get a warranty.]]></description>
  1693. <content:encoded><![CDATA[<p>I put off switching to Android because of all the stories. Android is slow, Android has terrible battery life, Android is full of malware and Ads.</p>
  1694. <p>I got so frustrated waiting for Apple to fix bugs that affected me on a daily basis, upgrading every year, only to find more things that no longer work. So I did it, and I'm glad I did.</p>
  1695. <p>At first I wasn't sure about it at all, I mean it does everything the same, it even kinda looks similar in places, but it wasn't iOS.</p>
  1696. <p>Performance. If you watch enough comparative reviews, you'll see Snapdragon chips trade blows with Apple's A series, A series better here, while SD better there.</p>
  1697. <p>Battery life... I have a two year Zenfone 9 and I charge it every 3 days. I had to use it extensively yesterday, and got home with 50% battery (it stated at 90%).</p>
  1698. <p>Malware. I've not encountered any in the 3 years I've been using Android. I'm not saying there isn't any as Google regularly reports how much crap they remove from their Play Store.</p>
  1699. <p>Ads. I'm pretty certain that if you buy a $100 Android phone, you're going to get Ads to subsidize the cost, but I've never seen an Ad in the last 3 years (both of my phones have been Asus).</p>
  1700. <p>I would recommend anyone who's slightly interested in switching, to try it themselves. Manufacturers sell refurbished devices, so you can score a 2 or 3 year old model for cheaper and still get a warranty.</p>
  1701. ]]></content:encoded>
  1702. </item>
  1703. <item>
  1704. <title>
  1705. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by Old Unix Geek </title>
  1706. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4059224</link>
  1707.  
  1708. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  1709. <pubDate>Sat, 23 Mar 2024 00:38:19 +0000</pubDate>
  1710. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4059224</guid>
  1711.  
  1712. <description><![CDATA[Perhaps if I built a tall enough one, you&#039;d knock some sense into yourself :-).]]></description>
  1713. <content:encoded><![CDATA[<p>Perhaps if I built a tall enough one, you'd knock some sense into yourself :-).</p>
  1714. ]]></content:encoded>
  1715. </item>
  1716. <item>
  1717. <title>
  1718. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by DJ </title>
  1719. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4059175</link>
  1720.  
  1721. <dc:creator><![CDATA[DJ]]></dc:creator>
  1722. <pubDate>Fri, 22 Mar 2024 21:49:00 +0000</pubDate>
  1723. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4059175</guid>
  1724.  
  1725. <description><![CDATA[Meanwhile, back at the pool:  What you&#039;re saying is that you want to be free to build a high-diving platform for my pool, and I have to be OK with that.]]></description>
  1726. <content:encoded><![CDATA[<p>Meanwhile, back at the pool:  What you're saying is that you want to be free to build a high-diving platform for my pool, and I have to be OK with that.</p>
  1727. ]]></content:encoded>
  1728. </item>
  1729. <item>
  1730. <title>
  1731. Comment on U.S. Sues Apple Over iPhone Monopoly by DJ </title>
  1732. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059170</link>
  1733.  
  1734. <dc:creator><![CDATA[DJ]]></dc:creator>
  1735. <pubDate>Fri, 22 Mar 2024 21:25:55 +0000</pubDate>
  1736. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059170</guid>
  1737.  
  1738. <description><![CDATA[Nope, iPhones and Android phones are &#039;smart phones&#039;.  They are both &#039;brands&#039;, and they compete in the &#039;smart phone market&#039;.  Porsche and Buick are automobiles.  They are both &#039;brands&#039;, and they compete in the &#039;automobile market&#039;.  I don&#039;t know how much simpler it can be.]]></description>
  1739. <content:encoded><![CDATA[<p>Nope, iPhones and Android phones are 'smart phones'.  They are both 'brands', and they compete in the 'smart phone market'.  Porsche and Buick are automobiles.  They are both 'brands', and they compete in the 'automobile market'.  I don't know how much simpler it can be.</p>
  1740. ]]></content:encoded>
  1741. </item>
  1742. <item>
  1743. <title>
  1744. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by Old Unix Geek </title>
  1745. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4059162</link>
  1746.  
  1747. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  1748. <pubDate>Fri, 22 Mar 2024 21:02:42 +0000</pubDate>
  1749. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4059162</guid>
  1750.  
  1751. <description><![CDATA[No. Many of us want more freedom. The ability to make an app and not worry that Apple will simply ban it with its shape-shifting regulations. Others want to use apps you don&#039;t care about like emulators, other web browsers, interpreters, not have to fuck around logging in to take a picture with a 3rd party photo app, and other apps people would have developed had they had the same freedom.
  1752.  
  1753. Even with Spotify, you are misconstruing things. Spotify wants to be able to compete fairly against Apple Music. Apple charging 30% while competing with them is like fighting with one arm behind their backs, particularly since Apple Music is already installed on the device whereas Spotify needs to make potential customers aware of its existence (which costs money). You also don&#039;t know whether they wouldn&#039;t improve Spotify if they had more money and could hire more developers. So your absolute statement about them is simply wrong.
  1754.  
  1755. And if you&#039;re so worried about app developers getting their hands on filthy lucre why aren&#039;t you worried about Apple&#039;s lucre? They accumulate a lot more of it than anyone else. And they&#039;re certainly not using it to hire developers to fix all the bugs in MacOS or iOS. And no, they don&#039;t make it, if they&#039;re just obtaining it by taxing transactions in the unique market for iOS apps which they just happen to control.]]></description>
  1756. <content:encoded><![CDATA[<p>No. Many of us want more freedom. The ability to make an app and not worry that Apple will simply ban it with its shape-shifting regulations. Others want to use apps you don't care about like emulators, other web browsers, interpreters, not have to fuck around logging in to take a picture with a 3rd party photo app, and other apps people would have developed had they had the same freedom.</p>
  1757. <p>Even with Spotify, you are misconstruing things. Spotify wants to be able to compete fairly against Apple Music. Apple charging 30% while competing with them is like fighting with one arm behind their backs, particularly since Apple Music is already installed on the device whereas Spotify needs to make potential customers aware of its existence (which costs money). You also don't know whether they wouldn't improve Spotify if they had more money and could hire more developers. So your absolute statement about them is simply wrong.</p>
  1758. <p>And if you're so worried about app developers getting their hands on filthy lucre why aren't you worried about Apple's lucre? They accumulate a lot more of it than anyone else. And they're certainly not using it to hire developers to fix all the bugs in MacOS or iOS. And no, they don't make it, if they're just obtaining it by taxing transactions in the unique market for iOS apps which they just happen to control.</p>
  1759. ]]></content:encoded>
  1760. </item>
  1761. <item>
  1762. <title>
  1763. Comment on U.S. Sues Apple Over iPhone Monopoly by Old Unix Geek </title>
  1764. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059160</link>
  1765.  
  1766. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  1767. <pubDate>Fri, 22 Mar 2024 20:48:48 +0000</pubDate>
  1768. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059160</guid>
  1769.  
  1770. <description><![CDATA[@DJ: Platforms are their own market, whether you like it or not.
  1771.  
  1772. That&#039;s what literally what the App Store is: a market, a place where the exchange of services and goods occurs.
  1773.  
  1774. If I build an App on iOS, my competitors are not applications running on Windows or Blackberries. Those are different incompatible platforms which have different customers, and I cannot offer them anything of value because the app I wrote only works on iOS. Since I am not providing them with anything of value, no exchange of services and goods will occur. Since no market transactions will occur, they are not part of the same market.
  1775.  
  1776. A platform is an environment in which software executes. Software only runs within a compatible platform because software is only a very long number. The platform knows how to decode that very long number into the behaviors that were intended by the software&#039;s author. The same very long number would result in very different behaviors on a different platform. (It would crash).
  1777.  
  1778. In the case of Porsche, you are in the same market as Buick: customers who might buy a Porsche might also buy a Buick. If, on the other hand, you wanted to sell a train locomotive, you&#039;d not be in the same market. People who want to drive on roads don&#039;t buy train locomotives because those need rails. Just as roads and rails are different, and result in different markets, so it is with iOS and Android, as far as apps are concerned. Just as trains and cars constitute different markets, so do iOS and Android. And it doesn&#039;t matter how much you scream &quot;but they are just different means of transportation&quot;.]]></description>
  1779. <content:encoded><![CDATA[<p>@DJ: Platforms are their own market, whether you like it or not.</p>
  1780. <p>That's what literally what the App Store is: a market, a place where the exchange of services and goods occurs.</p>
  1781. <p>If I build an App on iOS, my competitors are not applications running on Windows or Blackberries. Those are different incompatible platforms which have different customers, and I cannot offer them anything of value because the app I wrote only works on iOS. Since I am not providing them with anything of value, no exchange of services and goods will occur. Since no market transactions will occur, they are not part of the same market.</p>
  1782. <p>A platform is an environment in which software executes. Software only runs within a compatible platform because software is only a very long number. The platform knows how to decode that very long number into the behaviors that were intended by the software's author. The same very long number would result in very different behaviors on a different platform. (It would crash).</p>
  1783. <p>In the case of Porsche, you are in the same market as Buick: customers who might buy a Porsche might also buy a Buick. If, on the other hand, you wanted to sell a train locomotive, you'd not be in the same market. People who want to drive on roads don't buy train locomotives because those need rails. Just as roads and rails are different, and result in different markets, so it is with iOS and Android, as far as apps are concerned. Just as trains and cars constitute different markets, so do iOS and Android. And it doesn't matter how much you scream "but they are just different means of transportation".</p>
  1784. ]]></content:encoded>
  1785. </item>
  1786. <item>
  1787. <title>
  1788. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by DJ </title>
  1789. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4059154</link>
  1790.  
  1791. <dc:creator><![CDATA[DJ]]></dc:creator>
  1792. <pubDate>Fri, 22 Mar 2024 20:36:28 +0000</pubDate>
  1793. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4059154</guid>
  1794.  
  1795. <description><![CDATA[Again, the people that want to do this are not doing it &quot;for the people&quot;.  They&#039;re doing it &quot;for the money&quot;.  Spotify is not going to improve in any way by having their own app store, they&#039;re just going to keep more of the money for themselves.  This is not an Industrial Revolution analog, it&#039;s a redirection of money.]]></description>
  1796. <content:encoded><![CDATA[<p>Again, the people that want to do this are not doing it "for the people".  They're doing it "for the money".  Spotify is not going to improve in any way by having their own app store, they're just going to keep more of the money for themselves.  This is not an Industrial Revolution analog, it's a redirection of money.</p>
  1797. ]]></content:encoded>
  1798. </item>
  1799. <item>
  1800. <title>
  1801. Comment on U.S. Sues Apple Over iPhone Monopoly by DJ </title>
  1802. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059147</link>
  1803.  
  1804. <dc:creator><![CDATA[DJ]]></dc:creator>
  1805. <pubDate>Fri, 22 Mar 2024 20:15:36 +0000</pubDate>
  1806. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059147</guid>
  1807.  
  1808. <description><![CDATA[The whole idea that iOS (platform, product, whatever) is its own market is just wrong.  The market for iPhones is &#039;smart phones&#039;, just as the market for Macs is &#039;desktop computers&#039; and not &#039;macOS computers&#039;, and the market for Porsches is &#039;cars&#039;, not &#039;Porsche cars&#039;.  If I buy a Porsche, I don&#039;t expect to be able to swap in the front quarters from a Buick.]]></description>
  1809. <content:encoded><![CDATA[<p>The whole idea that iOS (platform, product, whatever) is its own market is just wrong.  The market for iPhones is 'smart phones', just as the market for Macs is 'desktop computers' and not 'macOS computers', and the market for Porsches is 'cars', not 'Porsche cars'.  If I buy a Porsche, I don't expect to be able to swap in the front quarters from a Buick.</p>
  1810. ]]></content:encoded>
  1811. </item>
  1812. <item>
  1813. <title>
  1814. Comment on DMA Compliance Workshop: Notarization and Core Technology Fee by Old Unix Geek </title>
  1815. <link>https://mjtsai.com/blog/2024/03/20/dma-compliance-workshop-notarization-and-core-technology-fee/#comment-4059130</link>
  1816.  
  1817. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  1818. <pubDate>Fri, 22 Mar 2024 19:46:50 +0000</pubDate>
  1819. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42573#comment-4059130</guid>
  1820.  
  1821. <description><![CDATA[Again, most people would have wanted a faster horse.
  1822.  
  1823. Most people before, and even during the industrial revolution, did not care what scientists and engineers were up to. But it made your life possible, since half of the people on the planet would not exist without the green revolution -- aka the Haber Bosch process.
  1824.  
  1825. What &quot;most people want&quot; is incredibly short-sighted, not some holy grail of truth.]]></description>
  1826. <content:encoded><![CDATA[<p>Again, most people would have wanted a faster horse.</p>
  1827. <p>Most people before, and even during the industrial revolution, did not care what scientists and engineers were up to. But it made your life possible, since half of the people on the planet would not exist without the green revolution -- aka the Haber Bosch process.</p>
  1828. <p>What "most people want" is incredibly short-sighted, not some holy grail of truth.</p>
  1829. ]]></content:encoded>
  1830. </item>
  1831. <item>
  1832. <title>
  1833. Comment on U.S. Sues Apple Over iPhone Monopoly by ObjC4Life </title>
  1834. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059099</link>
  1835.  
  1836. <dc:creator><![CDATA[ObjC4Life]]></dc:creator>
  1837. <pubDate>Fri, 22 Mar 2024 18:40:28 +0000</pubDate>
  1838. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059099</guid>
  1839.  
  1840. <description><![CDATA[&#062;I&#039;ve never felt &quot;locked in&quot; with Apple. If Android&#039;s ad-based ecosystem offered a superior experience, I would switch. It doesn&#039;t, so I don&#039;t. No doubt there needs to be better control over what can go into a children&#039;s app. I don&#039;t think separate app stores should be required for that, though admittedly I haven&#039;t put much thought how that could be solved.
  1841.  
  1842. Right but you&#039;re only one person. Does Apple have a monopoly on the iOS software market and does that hinder competition and hurt customers? Of course it does.
  1843.  
  1844. Can Amazon compete with Apple fairly when it comes to ebooks on iOS? The answer is no. I don&#039;t think the answer to that question is no on virtually any other computing platform.]]></description>
  1845. <content:encoded><![CDATA[<p>&gt;I've never felt "locked in" with Apple. If Android's ad-based ecosystem offered a superior experience, I would switch. It doesn't, so I don't. No doubt there needs to be better control over what can go into a children's app. I don't think separate app stores should be required for that, though admittedly I haven't put much thought how that could be solved.</p>
  1846. <p>Right but you're only one person. Does Apple have a monopoly on the iOS software market and does that hinder competition and hurt customers? Of course it does. </p>
  1847. <p>Can Amazon compete with Apple fairly when it comes to ebooks on iOS? The answer is no. I don't think the answer to that question is no on virtually any other computing platform.</p>
  1848. ]]></content:encoded>
  1849. </item>
  1850. <item>
  1851. <title>
  1852. Comment on U.S. Sues Apple Over iPhone Monopoly by DJ </title>
  1853. <link>https://mjtsai.com/blog/2024/03/21/u-s-sues-apple-over-iphone-monopoly/#comment-4059092</link>
  1854.  
  1855. <dc:creator><![CDATA[DJ]]></dc:creator>
  1856. <pubDate>Fri, 22 Mar 2024 18:26:53 +0000</pubDate>
  1857. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42594#comment-4059092</guid>
  1858.  
  1859. <description><![CDATA[I think RCS will solve a lot of those interoperability problems with messaging.  Right now, it&#039;s limited by SMS.
  1860.  
  1861. I&#039;ve never felt &quot;locked in&quot; with Apple.  If Android&#039;s ad-based ecosystem offered a superior experience, I would switch.  It doesn&#039;t, so I don&#039;t.
  1862.  
  1863. No doubt there needs to be better control over what can go into a children&#039;s app.  I don&#039;t think separate app stores should be required for that, though admittedly I haven&#039;t put much thought how that could be solved.]]></description>
  1864. <content:encoded><![CDATA[<p>I think RCS will solve a lot of those interoperability problems with messaging.  Right now, it's limited by SMS.</p>
  1865. <p>I've never felt "locked in" with Apple.  If Android's ad-based ecosystem offered a superior experience, I would switch.  It doesn't, so I don't.</p>
  1866. <p>No doubt there needs to be better control over what can go into a children's app.  I don't think separate app stores should be required for that, though admittedly I haven't put much thought how that could be solved.</p>
  1867. ]]></content:encoded>
  1868. </item>
  1869. </channel>
  1870. </rss>
  1871.  

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 RSS" banner.

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

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

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

http://www.feedvalidator.org/check.cgi?url=http%3A//mjtsai.com/blog/comments/feed/

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