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>Wed, 16 Apr 2025 14:56:47 +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 Git at 20 by Scott </title>
  22. <link>https://mjtsai.com/blog/2025/04/15/git-at-20/#comment-4250097</link>
  23.  
  24. <dc:creator><![CDATA[Scott]]></dc:creator>
  25. <pubDate>Wed, 16 Apr 2025 14:56:47 +0000</pubDate>
  26. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47408#comment-4250097</guid>
  27.  
  28. <description><![CDATA[And here I had naively hoped, 20 years ago now, that Apple would adopt principles of CMS/VCS into the Finder, and expand it out system-wide and eventually to a network and cloud service. Oh well. FTFF!
  29. (Oh those were the halcyon days, when Apple adopted UNIX fundamental concepts, pulled talent from FreeBSD, and the future looked so very bright! Annnnnnnnd… here we are.)]]></description>
  30. <content:encoded><![CDATA[<p>And here I had naively hoped, 20 years ago now, that Apple would adopt principles of CMS/VCS into the Finder, and expand it out system-wide and eventually to a network and cloud service. Oh well. FTFF!<br />
  31. (Oh those were the halcyon days, when Apple adopted UNIX fundamental concepts, pulled talent from FreeBSD, and the future looked so very bright! Annnnnnnnd… here we are.)</p>
  32. ]]></content:encoded>
  33. </item>
  34. <item>
  35. <title>
  36. Comment on Git at 20 by Wu Ming </title>
  37. <link>https://mjtsai.com/blog/2025/04/15/git-at-20/#comment-4250085</link>
  38.  
  39. <dc:creator><![CDATA[Wu Ming]]></dc:creator>
  40. <pubDate>Wed, 16 Apr 2025 14:18:04 +0000</pubDate>
  41. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47408#comment-4250085</guid>
  42.  
  43. <description><![CDATA[As much as standardization looks and feels convenient, I believe splitting teams and users on multiple tools offers not only variety, that is fun and useful, but also the opportunity for evolution.
  44.  
  45. One large corporation acting as conduit for most SCM processes is a menace. Especially when many other permutations with equivalent results are possible.
  46.  
  47. Personally I believe Fossil checks all the marks. As other SCM tools do. They were pushed to the margins for no good practical reasons.]]></description>
  48. <content:encoded><![CDATA[<p>As much as standardization looks and feels convenient, I believe splitting teams and users on multiple tools offers not only variety, that is fun and useful, but also the opportunity for evolution.</p>
  49. <p>One large corporation acting as conduit for most SCM processes is a menace. Especially when many other permutations with equivalent results are possible.</p>
  50. <p>Personally I believe Fossil checks all the marks. As other SCM tools do. They were pushed to the margins for no good practical reasons.</p>
  51. ]]></content:encoded>
  52. </item>
  53. <item>
  54. <title>
  55. Comment on Apple Mail&#8217;s Broken &#8220;Block All Remote Content&#8221; by frijole </title>
  56. <link>https://mjtsai.com/blog/2024/06/07/apple-mails-broken-block-all-remote-content/#comment-4250058</link>
  57.  
  58. <dc:creator><![CDATA[frijole]]></dc:creator>
  59. <pubDate>Wed, 16 Apr 2025 12:47:50 +0000</pubDate>
  60. <guid isPermaLink="false">https://mjtsai.com/blog/?p=43598#comment-4250058</guid>
  61.  
  62. <description><![CDATA[Earlier this year they responded to the bug report and gave me a bug bounty. They also created a CVE, and the fix went out in 15.4.
  63.  
  64. https://nvd.nist.gov/vuln/detail/CVE-2025-24172
  65. https://support.apple.com/en-us/122373]]></description>
  66. <content:encoded><![CDATA[<p>Earlier this year they responded to the bug report and gave me a bug bounty. They also created a CVE, and the fix went out in 15.4.</p>
  67. <p><a href="https://nvd.nist.gov/vuln/detail/CVE-2025-24172" rel="nofollow ugc">https://nvd.nist.gov/vuln/detail/CVE-2025-24172</a><br />
  68. <a href="https://support.apple.com/en-us/122373" rel="nofollow ugc">https://support.apple.com/en-us/122373</a></p>
  69. ]]></content:encoded>
  70. </item>
  71. <item>
  72. <title>
  73. Comment on Git at 20 by Plume </title>
  74. <link>https://mjtsai.com/blog/2025/04/15/git-at-20/#comment-4249988</link>
  75.  
  76. <dc:creator><![CDATA[Plume]]></dc:creator>
  77. <pubDate>Wed, 16 Apr 2025 08:15:54 +0000</pubDate>
  78. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47408#comment-4249988</guid>
  79.  
  80. <description><![CDATA[Git is in a sweet spot where it is technically very reliable, and the easy tasks are easy. You only encounter the weirder aspects when it&#039;s too late, and you&#039;re already deeply invested.]]></description>
  81. <content:encoded><![CDATA[<p>Git is in a sweet spot where it is technically very reliable, and the easy tasks are easy. You only encounter the weirder aspects when it's too late, and you're already deeply invested.</p>
  82. ]]></content:encoded>
  83. </item>
  84. <item>
  85. <title>
  86. Comment on Google Is Winning on Every AI Front by Philip </title>
  87. <link>https://mjtsai.com/blog/2025/04/14/google-is-winning-on-every-ai-front/#comment-4249713</link>
  88.  
  89. <dc:creator><![CDATA[Philip]]></dc:creator>
  90. <pubDate>Tue, 15 Apr 2025 16:19:25 +0000</pubDate>
  91. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47404#comment-4249713</guid>
  92.  
  93. <description><![CDATA[Same. I tried it after reading this post and it never outperformed ChatGPT. Neither in speed nor in answer quality.]]></description>
  94. <content:encoded><![CDATA[<p>Same. I tried it after reading this post and it never outperformed ChatGPT. Neither in speed nor in answer quality.</p>
  95. ]]></content:encoded>
  96. </item>
  97. <item>
  98. <title>
  99. Comment on Claude for Mac by Plume </title>
  100. <link>https://mjtsai.com/blog/2025/04/14/claude-for-mac/#comment-4249656</link>
  101.  
  102. <dc:creator><![CDATA[Plume]]></dc:creator>
  103. <pubDate>Tue, 15 Apr 2025 11:06:08 +0000</pubDate>
  104. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47402#comment-4249656</guid>
  105.  
  106. <description><![CDATA[&quot;All these apps are just glorified thin clients after all.&quot;
  107.  
  108. ChatGPT has pretty good integration into Mac OS. It can use the accessibility API to see what you are doing and read context from applications. It can also trigger some actions, like typing code into IntelliJ.
  109.  
  110. But even if they were just wrappers around the chat API, having a nice UI that you can trigger with a shortcut is still a nice win.
  111.  
  112. Incidentally, this is why LLM apps on iOS suck, they can&#039;t do any of this stuff.]]></description>
  113. <content:encoded><![CDATA[<p>"All these apps are just glorified thin clients after all."</p>
  114. <p>ChatGPT has pretty good integration into Mac OS. It can use the accessibility API to see what you are doing and read context from applications. It can also trigger some actions, like typing code into IntelliJ.</p>
  115. <p>But even if they were just wrappers around the chat API, having a nice UI that you can trigger with a shortcut is still a nice win.</p>
  116. <p>Incidentally, this is why LLM apps on iOS suck, they can't do any of this stuff.</p>
  117. ]]></content:encoded>
  118. </item>
  119. <item>
  120. <title>
  121. Comment on LLaMA Gaming AI Benchmarks by Kristoffer </title>
  122. <link>https://mjtsai.com/blog/2025/04/14/llama-gaming-ai-benchmarks/#comment-4249611</link>
  123.  
  124. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  125. <pubDate>Tue, 15 Apr 2025 08:29:56 +0000</pubDate>
  126. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47400#comment-4249611</guid>
  127.  
  128. <description><![CDATA[I found this bloggpost about how recent ai gains feel like bullshit rather spot on. I get this weird feeling like I&#039;m being gaslit all the time when people wax lyrically about how fantastic AI is. It&#039;s nice and useful I think the 20 dolalrs a month my company pays for my ChatGPT plus sub are money well spent.
  129.  
  130. But at the same time I honestly don&#039;t see that much of a difference over the last two years. It&#039;s more fine grained and tighter locked into the large hump of the bell curve. Results look more like the thing they&#039;re copying. Anyways... worth a read:
  131.  
  132.  
  133. https://www.lesswrong.com/posts/4mvphwx5pdsZLMmpY/recent-ai-model-progress-feels-mostly-like-bullshit]]></description>
  134. <content:encoded><![CDATA[<p>I found this bloggpost about how recent ai gains feel like bullshit rather spot on. I get this weird feeling like I'm being gaslit all the time when people wax lyrically about how fantastic AI is. It's nice and useful I think the 20 dolalrs a month my company pays for my ChatGPT plus sub are money well spent. </p>
  135. <p>But at the same time I honestly don't see that much of a difference over the last two years. It's more fine grained and tighter locked into the large hump of the bell curve. Results look more like the thing they're copying. Anyways... worth a read:</p>
  136. <p><a href="https://www.lesswrong.com/posts/4mvphwx5pdsZLMmpY/recent-ai-model-progress-feels-mostly-like-bullshit" rel="nofollow ugc">https://www.lesswrong.com/posts/4mvphwx5pdsZLMmpY/recent-ai-model-progress-feels-mostly-like-bullshit</a></p>
  137. ]]></content:encoded>
  138. </item>
  139. <item>
  140. <title>
  141. Comment on Bauhaus Clock Screensaver by freediverx </title>
  142. <link>https://mjtsai.com/blog/2025/04/11/bauhaus-clock-screensaver/#comment-4249483</link>
  143.  
  144. <dc:creator><![CDATA[freediverx]]></dc:creator>
  145. <pubDate>Mon, 14 Apr 2025 23:33:03 +0000</pubDate>
  146. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47388#comment-4249483</guid>
  147.  
  148. <description><![CDATA[ShutUpAndTakeMyMoney.gif]]></description>
  149. <content:encoded><![CDATA[<p>ShutUpAndTakeMyMoney.gif</p>
  150. ]]></content:encoded>
  151. </item>
  152. <item>
  153. <title>
  154. Comment on Google Is Winning on Every AI Front by Ben G </title>
  155. <link>https://mjtsai.com/blog/2025/04/14/google-is-winning-on-every-ai-front/#comment-4249481</link>
  156.  
  157. <dc:creator><![CDATA[Ben G]]></dc:creator>
  158. <pubDate>Mon, 14 Apr 2025 23:13:18 +0000</pubDate>
  159. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47404#comment-4249481</guid>
  160.  
  161. <description><![CDATA[Huh. I tried Gemini Pro from December until about 3 weeks ago and it consistently gave me incorrect answers (to engineering class problems) and/or it presented the answers in a very confusing manner. ChatGPT and Grok were almost always correct. Grok wins for outputting the answers in the most understandable format.
  162.  
  163. Often, I knew the answer that Gemini gave was incorrect right away, so I&#039;d say something like &quot;Are you sure this is correct?&quot; and it&#039;d be like &quot;You&#039;re right! My apologies for the oversight. Let me do it again.&quot; and it would either output the same wrong answer, or go off on a different wrong tangent.
  164.  
  165. Or sometimes it would have the equation correct, with the correct numbers, and then it would output the wrong answer. Like 2 + 3 = 5.3 type of stuff.
  166.  
  167. Guess I&#039;ll have to try the new model.]]></description>
  168. <content:encoded><![CDATA[<p>Huh. I tried Gemini Pro from December until about 3 weeks ago and it consistently gave me incorrect answers (to engineering class problems) and/or it presented the answers in a very confusing manner. ChatGPT and Grok were almost always correct. Grok wins for outputting the answers in the most understandable format.</p>
  169. <p>Often, I knew the answer that Gemini gave was incorrect right away, so I'd say something like "Are you sure this is correct?" and it'd be like "You're right! My apologies for the oversight. Let me do it again." and it would either output the same wrong answer, or go off on a different wrong tangent.</p>
  170. <p>Or sometimes it would have the equation correct, with the correct numbers, and then it would output the wrong answer. Like 2 + 3 = 5.3 type of stuff.</p>
  171. <p>Guess I'll have to try the new model.</p>
  172. ]]></content:encoded>
  173. </item>
  174. <item>
  175. <title>
  176. Comment on Claude for Mac by cglong </title>
  177. <link>https://mjtsai.com/blog/2025/04/14/claude-for-mac/#comment-4249450</link>
  178.  
  179. <dc:creator><![CDATA[cglong]]></dc:creator>
  180. <pubDate>Mon, 14 Apr 2025 21:18:38 +0000</pubDate>
  181. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47402#comment-4249450</guid>
  182.  
  183. <description><![CDATA[Is ChatGPT really the &quot;best&quot; app when it only works on macOS 14+ with Apple Silicon? All these apps are just glorified thin clients after all.]]></description>
  184. <content:encoded><![CDATA[<p>Is ChatGPT really the "best" app when it only works on macOS 14+ with Apple Silicon? All these apps are just glorified thin clients after all.</p>
  185. ]]></content:encoded>
  186. </item>
  187. <item>
  188. <title>
  189. Comment on Obituary for Cyc by John Muir </title>
  190. <link>https://mjtsai.com/blog/2025/04/14/obituary-for-cyc/#comment-4249441</link>
  191.  
  192. <dc:creator><![CDATA[John Muir]]></dc:creator>
  193. <pubDate>Mon, 14 Apr 2025 20:40:33 +0000</pubDate>
  194. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47406#comment-4249441</guid>
  195.  
  196. <description><![CDATA[Yes, I remembered that strange conclusion from the same documentary, many years after watching, it thanks to Andy Baio.
  197.  
  198. When I saw this here, what did I do to confirm it is the glimmering phantom that I thought it was? Asked an AI, of course.]]></description>
  199. <content:encoded><![CDATA[<p>Yes, I remembered that strange conclusion from the same documentary, many years after watching, it thanks to Andy Baio.</p>
  200. <p>When I saw this here, what did I do to confirm it is the glimmering phantom that I thought it was? Asked an AI, of course.</p>
  201. ]]></content:encoded>
  202. </item>
  203. <item>
  204. <title>
  205. Comment on Obituary for Cyc by Mac Folklore Radio </title>
  206. <link>https://mjtsai.com/blog/2025/04/14/obituary-for-cyc/#comment-4249434</link>
  207.  
  208. <dc:creator><![CDATA[Mac Folklore Radio]]></dc:creator>
  209. <pubDate>Mon, 14 Apr 2025 20:17:27 +0000</pubDate>
  210. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47406#comment-4249434</guid>
  211.  
  212. <description><![CDATA[[trying again with a disguised URL to get past WordPress]
  213.  
  214. I first heard about Cyc from the 1993 documentary &quot;The Machine That Changed The World&quot;.
  215.  
  216. Here&#039;s Doug talking about &quot;the brittleness problem&quot;:
  217.  
  218. https://www.youtube.com/watch?v=enWWlx7-t0k&#038;list=PL3GEqwP6dqmjVeHZTmymATHwu3s_YWLQC
  219.  
  220. Cyc knows people shave and Cyc &quot;thinks&quot; an electric shaver held in the hand is, in some sense, part of a person. But it also knows people don&#039;t have electrical parts. &quot;So in a sense, [Cyc] is asking,&#039;Is Fred still a person while he&#039;s shaving?&#039;&quot;
  221.  
  222. Unfortunately Doug passed away in 2023 (says Wikipedia).]]></description>
  223. <content:encoded><![CDATA[<p>[trying again with a disguised URL to get past WordPress]</p>
  224. <p>I first heard about Cyc from the 1993 documentary "The Machine That Changed The World". </p>
  225. <p>Here's Doug talking about "the brittleness problem":</p>
  226. <p><a href="https://www.youtube.com/watch?v=enWWlx7-t0k&#038;list=PL3GEqwP6dqmjVeHZTmymATHwu3s_YWLQC" rel="nofollow ugc">https://www.youtube.com/watch?v=enWWlx7-t0k&#038;list=PL3GEqwP6dqmjVeHZTmymATHwu3s_YWLQC</a></p>
  227. <p>Cyc knows people shave and Cyc "thinks" an electric shaver held in the hand is, in some sense, part of a person. But it also knows people don't have electrical parts. "So in a sense, [Cyc] is asking,'Is Fred still a person while he's shaving?'"</p>
  228. <p>Unfortunately Doug passed away in 2023 (says Wikipedia).</p>
  229. ]]></content:encoded>
  230. </item>
  231. <item>
  232. <title>
  233. Comment on Claude for Mac by Plume </title>
  234. <link>https://mjtsai.com/blog/2025/04/14/claude-for-mac/#comment-4249425</link>
  235.  
  236. <dc:creator><![CDATA[Plume]]></dc:creator>
  237. <pubDate>Mon, 14 Apr 2025 19:53:08 +0000</pubDate>
  238. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47402#comment-4249425</guid>
  239.  
  240. <description><![CDATA[OpenAI&#039;s app is currently the best vendor-specific Mac app. Claude is a barely working clown show, while ChatGPT feels part of the OS.
  241.  
  242. But IntelliBar is the best LLM chat app for Macs. Apart from the extremely convenient shortcut UI, it supports almost all LLM vendors and allows you to easily ask the same question to different models. You can prompt a local model, and if the answer isn&#039;t suitable, ask the same question to a commercial model with a single click.]]></description>
  243. <content:encoded><![CDATA[<p>OpenAI's app is currently the best vendor-specific Mac app. Claude is a barely working clown show, while ChatGPT feels part of the OS.</p>
  244. <p>But IntelliBar is the best LLM chat app for Macs. Apart from the extremely convenient shortcut UI, it supports almost all LLM vendors and allows you to easily ask the same question to different models. You can prompt a local model, and if the answer isn't suitable, ask the same question to a commercial model with a single click.</p>
  245. ]]></content:encoded>
  246. </item>
  247. <item>
  248. <title>
  249. Comment on LLaMA Gaming AI Benchmarks by Plume </title>
  250. <link>https://mjtsai.com/blog/2025/04/14/llama-gaming-ai-benchmarks/#comment-4249421</link>
  251.  
  252. <dc:creator><![CDATA[Plume]]></dc:creator>
  253. <pubDate>Mon, 14 Apr 2025 19:43:20 +0000</pubDate>
  254. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47400#comment-4249421</guid>
  255.  
  256. <description><![CDATA[The unmodified release version of Maverick (Llama-4-Maverick-17B-128E-Instruct) ranks 32nd on LMArena.
  257.  
  258. This is interesting because Meta tried to make the model less &quot;biased&quot; toward the left and refuse fewer questions. If the hypothesis that LLMs are biased toward the left is correct, removing that bias should improve the model, particularly in this type of benchmark. The results don&#039;t seem to bear that out.]]></description>
  259. <content:encoded><![CDATA[<p>The unmodified release version of Maverick (Llama-4-Maverick-17B-128E-Instruct) ranks 32nd on LMArena.</p>
  260. <p>This is interesting because Meta tried to make the model less "biased" toward the left and refuse fewer questions. If the hypothesis that LLMs are biased toward the left is correct, removing that bias should improve the model, particularly in this type of benchmark. The results don't seem to bear that out.</p>
  261. ]]></content:encoded>
  262. </item>
  263. <item>
  264. <title>
  265. Comment on Google Is Winning on Every AI Front by Bart </title>
  266. <link>https://mjtsai.com/blog/2025/04/14/google-is-winning-on-every-ai-front/#comment-4249410</link>
  267.  
  268. <dc:creator><![CDATA[Bart]]></dc:creator>
  269. <pubDate>Mon, 14 Apr 2025 18:58:23 +0000</pubDate>
  270. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47404#comment-4249410</guid>
  271.  
  272. <description><![CDATA[Aside from the cringe phrasing of &quot;vibes checks and high-taste testers,&quot; I have to agree. My own &quot;vibe check&quot; says they have accelerated very quickly. And they do have the advantage that they basically already have everyone&#039;s data, and everyone has an account. An advantage that Apple also potentially had and will continue to squander for the foreseeable future.
  273.  
  274. People gave them a hard time for a while about &quot;glue on pizza&quot; (sounds kind of old already) but in that span of time they went from that to something that has a substantial lead and is inarguably useful.]]></description>
  275. <content:encoded><![CDATA[<p>Aside from the cringe phrasing of "vibes checks and high-taste testers," I have to agree. My own "vibe check" says they have accelerated very quickly. And they do have the advantage that they basically already have everyone's data, and everyone has an account. An advantage that Apple also potentially had and will continue to squander for the foreseeable future.</p>
  276. <p>People gave them a hard time for a while about "glue on pizza" (sounds kind of old already) but in that span of time they went from that to something that has a substantial lead and is inarguably useful.</p>
  277. ]]></content:encoded>
  278. </item>
  279. <item>
  280. <title>
  281. Comment on LLaMA Gaming AI Benchmarks by Laurent Giroud </title>
  282. <link>https://mjtsai.com/blog/2025/04/14/llama-gaming-ai-benchmarks/#comment-4249407</link>
  283.  
  284. <dc:creator><![CDATA[Laurent Giroud]]></dc:creator>
  285. <pubDate>Mon, 14 Apr 2025 18:46:45 +0000</pubDate>
  286. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47400#comment-4249407</guid>
  287.  
  288. <description><![CDATA[This is interesting on two counts: first this highlights how those firms are essentially clueless as to how generally improve their models so they can be controlled in more programmatic manners (which, by construction, they cannot be), and second, they are willing to take the risk to be caught pants down, lying in public about it.
  289.  
  290. So we have essentially two levels of incompetence: one semi-technical and one purely executive/communication. The latter of which raises even more moral questions but keep in mind that companies are amoral (alas).
  291.  
  292. I think they are essentially symptoms of the same underlying issue though: executives are so far from having a technical understanding of the issues at hand here that they seem to be essentially wishing their teams to make the LLM inherent-to-their-construction problems disappear and are willing to fabricate evidence in the meantime.
  293. This would already be an important problem but there could be a second one at play here : one may wonder if those executives are getting clear feedback from engineers that LLMs’s lack of controllability are inherent to their very structure. Absent this feedback they would not see any other choice but to march forward (into the wall, alas).
  294. Given how much AI hype there is, even in engineering groups, it is not even clear many even dare expressing the thought that other approaches are needed for the expected feature set (natural language, symbolic reasoning, safety, absence of hallucinations).
  295.  
  296. I am with John Siracusa here: a step back is needed but it’s not clear there is any awareness of that necessity at any decision level in those companies. And the fact they are willing to be caught lying about it makes one think they don’t really have a way out at the moment.]]></description>
  297. <content:encoded><![CDATA[<p>This is interesting on two counts: first this highlights how those firms are essentially clueless as to how generally improve their models so they can be controlled in more programmatic manners (which, by construction, they cannot be), and second, they are willing to take the risk to be caught pants down, lying in public about it.</p>
  298. <p>So we have essentially two levels of incompetence: one semi-technical and one purely executive/communication. The latter of which raises even more moral questions but keep in mind that companies are amoral (alas).</p>
  299. <p>I think they are essentially symptoms of the same underlying issue though: executives are so far from having a technical understanding of the issues at hand here that they seem to be essentially wishing their teams to make the LLM inherent-to-their-construction problems disappear and are willing to fabricate evidence in the meantime.<br />
  300. This would already be an important problem but there could be a second one at play here : one may wonder if those executives are getting clear feedback from engineers that LLMs’s lack of controllability are inherent to their very structure. Absent this feedback they would not see any other choice but to march forward (into the wall, alas).<br />
  301. Given how much AI hype there is, even in engineering groups, it is not even clear many even dare expressing the thought that other approaches are needed for the expected feature set (natural language, symbolic reasoning, safety, absence of hallucinations).</p>
  302. <p>I am with John Siracusa here: a step back is needed but it’s not clear there is any awareness of that necessity at any decision level in those companies. And the fact they are willing to be caught lying about it makes one think they don’t really have a way out at the moment.</p>
  303. ]]></content:encoded>
  304. </item>
  305. <item>
  306. <title>
  307. Comment on Bauhaus Clock Screensaver by Alexandre Dieulot </title>
  308. <link>https://mjtsai.com/blog/2025/04/11/bauhaus-clock-screensaver/#comment-4249310</link>
  309.  
  310. <dc:creator><![CDATA[Alexandre Dieulot]]></dc:creator>
  311. <pubDate>Mon, 14 Apr 2025 13:18:14 +0000</pubDate>
  312. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47388#comment-4249310</guid>
  313.  
  314. <description><![CDATA[https://x.com/_atilla1/status/1911443302127227249
  315.  
  316. &#062; Since it&#039;s based on the Max Bill watch dial, I&#039;ve taken it offline to clarify design rights and avoid any IP issues. I&#039;m already in touch with @junghansgermany to properly address the situation. I&#039;ll keep you updated on our progress. Thank you!]]></description>
  317. <content:encoded><![CDATA[<p><a href="https://x.com/_atilla1/status/1911443302127227249" rel="nofollow ugc">https://x.com/_atilla1/status/1911443302127227249</a></p>
  318. <p>&gt; Since it's based on the Max Bill watch dial, I've taken it offline to clarify design rights and avoid any IP issues. I'm already in touch with @junghansgermany to properly address the situation. I'll keep you updated on our progress. Thank you!</p>
  319. ]]></content:encoded>
  320. </item>
  321. <item>
  322. <title>
  323. Comment on Unable to Send Messages With Apple Mail on macOS 15.4 by sergio molino </title>
  324. <link>https://mjtsai.com/blog/2025/04/09/unable-to-send-messages-with-apple-mail-on-macos-15-4/#comment-4249273</link>
  325.  
  326. <dc:creator><![CDATA[sergio molino]]></dc:creator>
  327. <pubDate>Mon, 14 Apr 2025 10:39:03 +0000</pubDate>
  328. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47365#comment-4249273</guid>
  329.  
  330. <description><![CDATA[I have the same problem, I do not understand why the Send icon is greyed out after the first pressing!!]]></description>
  331. <content:encoded><![CDATA[<p>I have the same problem, I do not understand why the Send icon is greyed out after the first pressing!!</p>
  332. ]]></content:encoded>
  333. </item>
  334. <item>
  335. <title>
  336. Comment on How Apple Fumbled Siri&#8217;s AI Makeover by Kristoffer </title>
  337. <link>https://mjtsai.com/blog/2025/04/10/how-apple-fumbled-siris-ai-makeover/#comment-4249250</link>
  338.  
  339. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  340. <pubDate>Mon, 14 Apr 2025 09:25:32 +0000</pubDate>
  341. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47373#comment-4249250</guid>
  342.  
  343. <description><![CDATA[I&#039;m with this lot: https://edition.cnn.com/2025/03/27/tech/apple-ai-artificial-intelligence/index.html
  344.  
  345. AI is the failure, not the poor sods trying to use it for something]]></description>
  346. <content:encoded><![CDATA[<p>I'm with this lot: <a href="https://edition.cnn.com/2025/03/27/tech/apple-ai-artificial-intelligence/index.html" rel="nofollow ugc">https://edition.cnn.com/2025/03/27/tech/apple-ai-artificial-intelligence/index.html</a></p>
  347. <p>AI is the failure, not the poor sods trying to use it for something</p>
  348. ]]></content:encoded>
  349. </item>
  350. <item>
  351. <title>
  352. Comment on Bauhaus Clock Screensaver by Kristoffer </title>
  353. <link>https://mjtsai.com/blog/2025/04/11/bauhaus-clock-screensaver/#comment-4249222</link>
  354.  
  355. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  356. <pubDate>Mon, 14 Apr 2025 07:48:04 +0000</pubDate>
  357. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47388#comment-4249222</guid>
  358.  
  359. <description><![CDATA[Like with the iOS clock that Apple copied? https://www.chinadaily.com.cn/m/cip/2013-01/08/content_16095837.htm]]></description>
  360. <content:encoded><![CDATA[<p>Like with the iOS clock that Apple copied? <a href="https://www.chinadaily.com.cn/m/cip/2013-01/08/content_16095837.htm" rel="nofollow ugc">https://www.chinadaily.com.cn/m/cip/2013-01/08/content_16095837.htm</a></p>
  361. ]]></content:encoded>
  362. </item>
  363. <item>
  364. <title>
  365. Comment on Bauhaus Clock Screensaver by Nate </title>
  366. <link>https://mjtsai.com/blog/2025/04/11/bauhaus-clock-screensaver/#comment-4249092</link>
  367.  
  368. <dc:creator><![CDATA[Nate]]></dc:creator>
  369. <pubDate>Sun, 13 Apr 2025 23:15:45 +0000</pubDate>
  370. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47388#comment-4249092</guid>
  371.  
  372. <description><![CDATA[It looks beautiful but it’s currently unavailable. Intellectual property claim from Junghans?]]></description>
  373. <content:encoded><![CDATA[<p>It looks beautiful but it’s currently unavailable. Intellectual property claim from Junghans?</p>
  374. ]]></content:encoded>
  375. </item>
  376. <item>
  377. <title>
  378. Comment on Abysmal Services by Tony Collins </title>
  379. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4248880</link>
  380.  
  381. <dc:creator><![CDATA[Tony Collins]]></dc:creator>
  382. <pubDate>Sun, 13 Apr 2025 10:04:12 +0000</pubDate>
  383. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4248880</guid>
  384.  
  385. <description><![CDATA[Hi Sebby. I use iCloud with a custom domain, which might be the worst of all worlds
  386.  
  387. Can I ask why you use a VM to host your mail?
  388.  
  389. I&#039;ve got a new Mac mini and I&#039;m considering self-hosting but to be honest I wouldn&#039;t know where to start these days - the last time I self-hosted was around 2003&#039;]]></description>
  390. <content:encoded><![CDATA[<p>Hi Sebby. I use iCloud with a custom domain, which might be the worst of all worlds</p>
  391. <p>Can I ask why you use a VM to host your mail? </p>
  392. <p>I've got a new Mac mini and I'm considering self-hosting but to be honest I wouldn't know where to start these days - the last time I self-hosted was around 2003'</p>
  393. ]]></content:encoded>
  394. </item>
  395. <item>
  396. <title>
  397. Comment on Failed Software Update on the External Drive of an Apple Silicon Mac by Riccardo Mori </title>
  398. <link>https://mjtsai.com/blog/2025/04/11/failed-software-update-on-the-external-drive-of-an-apple-silicon-mac/#comment-4248730</link>
  399.  
  400. <dc:creator><![CDATA[Riccardo Mori]]></dc:creator>
  401. <pubDate>Sat, 12 Apr 2025 22:08:50 +0000</pubDate>
  402. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47392#comment-4248730</guid>
  403.  
  404. <description><![CDATA[What MeX said, 100%.]]></description>
  405. <content:encoded><![CDATA[<p>What MeX said, 100%.</p>
  406. ]]></content:encoded>
  407. </item>
  408. <item>
  409. <title>
  410. Comment on Failed Software Update on the External Drive of an Apple Silicon Mac by charles </title>
  411. <link>https://mjtsai.com/blog/2025/04/11/failed-software-update-on-the-external-drive-of-an-apple-silicon-mac/#comment-4248674</link>
  412.  
  413. <dc:creator><![CDATA[charles]]></dc:creator>
  414. <pubDate>Sat, 12 Apr 2025 18:31:51 +0000</pubDate>
  415. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47392#comment-4248674</guid>
  416.  
  417. <description><![CDATA[I don&#039;t understand the problem. Just copy the &quot;System&quot; folder to the external disk. Oh wait... that&#039;s OS 9.
  418.  
  419. Okay, no problem. Well, it&#039;s a bit of a nuisance, but not that bad: just copy everything from the root of a working volume to the external volume, and &quot;bless&quot; the disk... right, that&#039;s OS X.
  420.  
  421. Oh, right. It&#039;s a Silicon Mac. What&#039;s that you say, follow an Apple Support article? No, that won&#039;t work. What you had better do is just send an email to this guy Howard Oakley...]]></description>
  422. <content:encoded><![CDATA[<p>I don't understand the problem. Just copy the "System" folder to the external disk. Oh wait... that's OS 9.</p>
  423. <p>Okay, no problem. Well, it's a bit of a nuisance, but not that bad: just copy everything from the root of a working volume to the external volume, and "bless" the disk... right, that's OS X.</p>
  424. <p>Oh, right. It's a Silicon Mac. What's that you say, follow an Apple Support article? No, that won't work. What you had better do is just send an email to this guy Howard Oakley...</p>
  425. ]]></content:encoded>
  426. </item>
  427. <item>
  428. <title>
  429. Comment on Failed Software Update on the External Drive of an Apple Silicon Mac by MeX </title>
  430. <link>https://mjtsai.com/blog/2025/04/11/failed-software-update-on-the-external-drive-of-an-apple-silicon-mac/#comment-4248672</link>
  431.  
  432. <dc:creator><![CDATA[MeX]]></dc:creator>
  433. <pubDate>Sat, 12 Apr 2025 18:29:14 +0000</pubDate>
  434. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47392#comment-4248672</guid>
  435.  
  436. <description><![CDATA[Apple says that all this mess is for privacy reasons. OK, then give us the option to select what privacy level do we want. I want to be able to do with my Macs whatever I want, including 100% booting from external SSD, booting different Macs from the very same external SSD, not installing anything in the internal SSD (booting 100% from the external SSD) leaving it empty or for Time Machine backups only, install any application from outside the Apple Store, etc.
  437.  
  438. Apple, they are my Macs, not yours, since I paid for them. Stop patronizing us. Give us options. Options are good.]]></description>
  439. <content:encoded><![CDATA[<p>Apple says that all this mess is for privacy reasons. OK, then give us the option to select what privacy level do we want. I want to be able to do with my Macs whatever I want, including 100% booting from external SSD, booting different Macs from the very same external SSD, not installing anything in the internal SSD (booting 100% from the external SSD) leaving it empty or for Time Machine backups only, install any application from outside the Apple Store, etc.</p>
  440. <p>Apple, they are my Macs, not yours, since I paid for them. Stop patronizing us. Give us options. Options are good.</p>
  441. ]]></content:encoded>
  442. </item>
  443. <item>
  444. <title>
  445. Comment on Failed Software Update on the External Drive of an Apple Silicon Mac by Michael Tsai </title>
  446. <link>https://mjtsai.com/blog/2025/04/11/failed-software-update-on-the-external-drive-of-an-apple-silicon-mac/#comment-4248585</link>
  447.  
  448. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  449. <pubDate>Sat, 12 Apr 2025 13:19:28 +0000</pubDate>
  450. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47392#comment-4248585</guid>
  451.  
  452. <description><![CDATA[@Jon I recommend disabling Activation Lock, too, but I don’t think it has any bearing on any of the boot/install issues I’ve been writing about these last few weeks.]]></description>
  453. <content:encoded><![CDATA[<p>@Jon I recommend disabling Activation Lock, too, but I don’t think it has any bearing on any of the boot/install issues I’ve been writing about these last few weeks.</p>
  454. ]]></content:encoded>
  455. </item>
  456. <item>
  457. <title>
  458. Comment on Failed Software Update on the External Drive of an Apple Silicon Mac by Sebby </title>
  459. <link>https://mjtsai.com/blog/2025/04/11/failed-software-update-on-the-external-drive-of-an-apple-silicon-mac/#comment-4248579</link>
  460.  
  461. <dc:creator><![CDATA[Sebby]]></dc:creator>
  462. <pubDate>Sat, 12 Apr 2025 13:05:25 +0000</pubDate>
  463. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47392#comment-4248579</guid>
  464.  
  465. <description><![CDATA[T2 and later require Internet, yeah. And with the T2 you have to depend on Internet Recovery if there&#039;s any failure of the internal installation unless you were clever enough to preempt this and turn off signature verification and turn on external bootability.
  466.  
  467. And for AS, yes, you had to have transferred ownership during installation for an external install to be updatable. I ran into this as well and back then there was no way to recover from this situation except starting from scratch. Unfortunately the whole thing is now very brittle and failure-prone, dependent on a load of variables that are very hard to estimate and it&#039;s pot luck more than anything whether it&#039;ll work or not. I don&#039;t think Apple intended it to be user-serviceable at all and it works only because Apple thought it was worth supporting, but not supporting well.]]></description>
  468. <content:encoded><![CDATA[<p>T2 and later require Internet, yeah. And with the T2 you have to depend on Internet Recovery if there's any failure of the internal installation unless you were clever enough to preempt this and turn off signature verification and turn on external bootability.</p>
  469. <p>And for AS, yes, you had to have transferred ownership during installation for an external install to be updatable. I ran into this as well and back then there was no way to recover from this situation except starting from scratch. Unfortunately the whole thing is now very brittle and failure-prone, dependent on a load of variables that are very hard to estimate and it's pot luck more than anything whether it'll work or not. I don't think Apple intended it to be user-serviceable at all and it works only because Apple thought it was worth supporting, but not supporting well.</p>
  470. ]]></content:encoded>
  471. </item>
  472. <item>
  473. <title>
  474. Comment on Failed Software Update on the External Drive of an Apple Silicon Mac by Jon </title>
  475. <link>https://mjtsai.com/blog/2025/04/11/failed-software-update-on-the-external-drive-of-an-apple-silicon-mac/#comment-4248574</link>
  476.  
  477. <dc:creator><![CDATA[Jon]]></dc:creator>
  478. <pubDate>Sat, 12 Apr 2025 12:41:22 +0000</pubDate>
  479. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47392#comment-4248574</guid>
  480.  
  481. <description><![CDATA[That&#039;s why primary thing I do with at least non portable Macs is disable Activation Lock.
  482. In the past I had multiple errors of updating operating system due to apple which send bad system signature via nsurl or due a not properly verified signature of iBoot prior installing firmware with system update.
  483.  
  484. Disabled Activation Lock and boom, Mac behaves like it should.]]></description>
  485. <content:encoded><![CDATA[<p>That's why primary thing I do with at least non portable Macs is disable Activation Lock.<br />
  486. In the past I had multiple errors of updating operating system due to apple which send bad system signature via nsurl or due a not properly verified signature of iBoot prior installing firmware with system update.</p>
  487. <p>Disabled Activation Lock and boom, Mac behaves like it should.</p>
  488. ]]></content:encoded>
  489. </item>
  490. <item>
  491. <title>
  492. Comment on Abysmal Services by Sebby </title>
  493. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4248539</link>
  494.  
  495. <dc:creator><![CDATA[Sebby]]></dc:creator>
  496. <pubDate>Sat, 12 Apr 2025 11:09:18 +0000</pubDate>
  497. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4248539</guid>
  498.  
  499. <description><![CDATA[Self-host email, sure. Why not? He&#039;s right, iCloud email is terrible (source: me, recovering addict). An AS Mac Mini running your email server stack in a VM will work great. Use Arq to back up the VM to Wasabi, and put the credentials in a plain text file stored in iCloud Drive (but not the encryption password, obviously).
  500.  
  501. And I used to be terrified as well, but I realised this was basically because of the trauma caused by HW failures in the past. Yes things can go wrong, but you only live once on this earth and so long as your data&#039;s backed up safely you have nothing to fear from HW failure because in the absolute worst case you can find another host (managed or otherwise). And, really, you *do* have more important things to worry about if your house burns down. You are most certainly not your email. The big players have been very successful in raising expectations, and yes there are clearly cases where it just makes more sense to recommend hosted services to others, but they are not infallible or special, and the commodification of compute resources ironically means that you have more power now than ever (despite, yes, the hardship of getting delivery working out of the gate). I used to self-host, and am happy to be doing it again.]]></description>
  502. <content:encoded><![CDATA[<p>Self-host email, sure. Why not? He's right, iCloud email is terrible (source: me, recovering addict). An AS Mac Mini running your email server stack in a VM will work great. Use Arq to back up the VM to Wasabi, and put the credentials in a plain text file stored in iCloud Drive (but not the encryption password, obviously).</p>
  503. <p>And I used to be terrified as well, but I realised this was basically because of the trauma caused by HW failures in the past. Yes things can go wrong, but you only live once on this earth and so long as your data's backed up safely you have nothing to fear from HW failure because in the absolute worst case you can find another host (managed or otherwise). And, really, you *do* have more important things to worry about if your house burns down. You are most certainly not your email. The big players have been very successful in raising expectations, and yes there are clearly cases where it just makes more sense to recommend hosted services to others, but they are not infallible or special, and the commodification of compute resources ironically means that you have more power now than ever (despite, yes, the hardship of getting delivery working out of the gate). I used to self-host, and am happy to be doing it again.</p>
  504. ]]></content:encoded>
  505. </item>
  506. <item>
  507. <title>
  508. Comment on Swiftly 1.0 by Sebby </title>
  509. <link>https://mjtsai.com/blog/2025/04/08/swiftly-1-0/#comment-4248527</link>
  510.  
  511. <dc:creator><![CDATA[Sebby]]></dc:creator>
  512. <pubDate>Sat, 12 Apr 2025 09:59:27 +0000</pubDate>
  513. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47354#comment-4248527</guid>
  514.  
  515. <description><![CDATA[OK so it genuinely looks nice. This is the sort of quickstarter that languages really benefit from; just look at the success of golang because of the self-contained toolchain. I think this is necessary to get past Xcode.]]></description>
  516. <content:encoded><![CDATA[<p>OK so it genuinely looks nice. This is the sort of quickstarter that languages really benefit from; just look at the success of golang because of the self-contained toolchain. I think this is necessary to get past Xcode.</p>
  517. ]]></content:encoded>
  518. </item>
  519. <item>
  520. <title>
  521. Comment on CSS &#8220;text-wrap: pretty&#8221; in WebKit by Plume </title>
  522. <link>https://mjtsai.com/blog/2025/04/11/css-text-wrap-pretty-in-webkit/#comment-4248482</link>
  523.  
  524. <dc:creator><![CDATA[Plume]]></dc:creator>
  525. <pubDate>Sat, 12 Apr 2025 07:26:54 +0000</pubDate>
  526. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47386#comment-4248482</guid>
  527.  
  528. <description><![CDATA[That Gruber example is devastating. How did they not think of this when designing this feature? There must be a way to define a parent relative to which all child paragraphs are formatted.]]></description>
  529. <content:encoded><![CDATA[<p>That Gruber example is devastating. How did they not think of this when designing this feature? There must be a way to define a parent relative to which all child paragraphs are formatted.</p>
  530. ]]></content:encoded>
  531. </item>
  532. <item>
  533. <title>
  534. Comment on APFS Native Normalization by A brief history of Mac native file systems </title>
  535. <link>https://mjtsai.com/blog/2017/06/27/apfs-native-normalization/#comment-4248481</link>
  536.  
  537. <dc:creator><![CDATA[A brief history of Mac native file systems]]></dc:creator>
  538. <pubDate>Sat, 12 Apr 2025 07:26:13 +0000</pubDate>
  539. <guid isPermaLink="false">https://mjtsai.com/blog/?p=18242#comment-4248481</guid>
  540.  
  541. <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>
  542. <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>
  543. ]]></content:encoded>
  544. </item>
  545. <item>
  546. <title>
  547. Comment on Failed Software Update on the External Drive of an Apple Silicon Mac by Michael Tsai </title>
  548. <link>https://mjtsai.com/blog/2025/04/11/failed-software-update-on-the-external-drive-of-an-apple-silicon-mac/#comment-4248312</link>
  549.  
  550. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  551. <pubDate>Fri, 11 Apr 2025 22:41:44 +0000</pubDate>
  552. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47392#comment-4248312</guid>
  553.  
  554. <description><![CDATA[@Mike I think the Apple Silicon Macs needs activation from Apple’s server, so I doubt they’ll be able to even install the OS.]]></description>
  555. <content:encoded><![CDATA[<p>@Mike I think the Apple Silicon Macs needs activation from Apple’s server, so I doubt they’ll be able to even install the OS.</p>
  556. ]]></content:encoded>
  557. </item>
  558. <item>
  559. <title>
  560. Comment on Failed Software Update on the External Drive of an Apple Silicon Mac by Mike Richardson </title>
  561. <link>https://mjtsai.com/blog/2025/04/11/failed-software-update-on-the-external-drive-of-an-apple-silicon-mac/#comment-4248309</link>
  562.  
  563. <dc:creator><![CDATA[Mike Richardson]]></dc:creator>
  564. <pubDate>Fri, 11 Apr 2025 22:33:37 +0000</pubDate>
  565. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47392#comment-4248309</guid>
  566.  
  567. <description><![CDATA[Why did they have to make the firmware and external booting and all of this so goddamn brittle?
  568.  
  569. 20 years from now, the retro computing crowd is going to have a hell of a time with these machines. The hardware might work perfectly fine (assuming you removed the battery before it leaked liquid death all over the logic board), but no one will be able to load any software onto the damn things.
  570.  
  571. &#062; The cynical take is that all this is an attempt to set up Macs for removal of external booting altogether.
  572.  
  573. Why even bother with all this half-ass shit then? Just kill external booting with the introduction of Apple Silicon.]]></description>
  574. <content:encoded><![CDATA[<p>Why did they have to make the firmware and external booting and all of this so goddamn brittle?</p>
  575. <p>20 years from now, the retro computing crowd is going to have a hell of a time with these machines. The hardware might work perfectly fine (assuming you removed the battery before it leaked liquid death all over the logic board), but no one will be able to load any software onto the damn things.</p>
  576. <p>&gt; The cynical take is that all this is an attempt to set up Macs for removal of external booting altogether. </p>
  577. <p>Why even bother with all this half-ass shit then? Just kill external booting with the introduction of Apple Silicon.</p>
  578. ]]></content:encoded>
  579. </item>
  580. <item>
  581. <title>
  582. Comment on CSS &#8220;text-wrap: pretty&#8221; in WebKit by Lukáš Valenta </title>
  583. <link>https://mjtsai.com/blog/2025/04/11/css-text-wrap-pretty-in-webkit/#comment-4248292</link>
  584.  
  585. <dc:creator><![CDATA[Lukáš Valenta]]></dc:creator>
  586. <pubDate>Fri, 11 Apr 2025 21:09:32 +0000</pubDate>
  587. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47386#comment-4248292</guid>
  588.  
  589. <description><![CDATA[I wonder how is it that SwiftUI does not offer anything like this - the native app loses here (for content where this might make sense)]]></description>
  590. <content:encoded><![CDATA[<p>I wonder how is it that SwiftUI does not offer anything like this - the native app loses here (for content where this might make sense)</p>
  591. ]]></content:encoded>
  592. </item>
  593. <item>
  594. <title>
  595. Comment on Failed Software Update on the External Drive of an Apple Silicon Mac by Daniel </title>
  596. <link>https://mjtsai.com/blog/2025/04/11/failed-software-update-on-the-external-drive-of-an-apple-silicon-mac/#comment-4248284</link>
  597.  
  598. <dc:creator><![CDATA[Daniel]]></dc:creator>
  599. <pubDate>Fri, 11 Apr 2025 20:35:26 +0000</pubDate>
  600. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47392#comment-4248284</guid>
  601.  
  602. <description><![CDATA[I don&#039;t like the direction computing is headed. What benefit do these policies have?
  603.  
  604. The cynical take is that all this is an attempt to set up Macs for removal of external booting altogether. iPad-ification is only getting worse...]]></description>
  605. <content:encoded><![CDATA[<p>I don't like the direction computing is headed. What benefit do these policies have? </p>
  606. <p>The cynical take is that all this is an attempt to set up Macs for removal of external booting altogether. iPad-ification is only getting worse...</p>
  607. ]]></content:encoded>
  608. </item>
  609. <item>
  610. <title>
  611. Comment on Soured by Michael Tsai </title>
  612. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4248254</link>
  613.  
  614. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  615. <pubDate>Fri, 11 Apr 2025 17:56:33 +0000</pubDate>
  616. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4248254</guid>
  617.  
  618. <description><![CDATA[@ObjC4Life I am still getting prompt and helpful responses from DTS, but most of the issues end up being bugs or known limitations with no workaround.]]></description>
  619. <content:encoded><![CDATA[<p>@ObjC4Life I am still getting prompt and helpful responses from DTS, but most of the issues end up being bugs or known limitations with no workaround.</p>
  620. ]]></content:encoded>
  621. </item>
  622. <item>
  623. <title>
  624. Comment on Why Companies Don&#8217;t Fix Bugs by Michael Tsai </title>
  625. <link>https://mjtsai.com/blog/2025/04/09/why-companies-dont-fix-bugs/#comment-4248252</link>
  626.  
  627. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  628. <pubDate>Fri, 11 Apr 2025 17:53:59 +0000</pubDate>
  629. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47362#comment-4248252</guid>
  630.  
  631. <description><![CDATA[@Vadim It’s a comment on the same blog post.]]></description>
  632. <content:encoded><![CDATA[<p>@Vadim It’s a comment on the same blog post.</p>
  633. ]]></content:encoded>
  634. </item>
  635. <item>
  636. <title>
  637. Comment on Soured by ObjC4Life </title>
  638. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4248183</link>
  639.  
  640. <dc:creator><![CDATA[ObjC4Life]]></dc:creator>
  641. <pubDate>Fri, 11 Apr 2025 13:38:30 +0000</pubDate>
  642. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4248183</guid>
  643.  
  644. <description><![CDATA[Thanks for your blog post. You were spot on talking about how Swift/SwiftUI is like chasing a moving target. I&#039;ve decided not to do it. You talked about how devs are basically in an abusive relationship and I agree.
  645.  
  646. Apple&#039;s hard push on new APIs often has developers scrambling (myself included). People who work inside Apple have their own interests/agendas that don&#039;t always align with ours.
  647.  
  648. Ideally an approaching WWDC should be an exiting time for developers. I *should* get the feeling that Apple is going to introduce all these new features that can integrate into my app that is going to make my life EASIER and better. But instead I get a feeling of dread. What APIs that are important to me are they going to deprecate? What&#039;s going to break? What new half-implemented features are they going to try to push on me?
  649.  
  650.  
  651. Everyone feels they *need* to move to SwiftUI or else ( Sonos, Overcast etc.)...but that isn&#039;t the approach I&#039;m taking. Apple&#039;s messaging has a lot to do with these feelings but they so often mislead us.
  652.  
  653. You talked about GCD vs Combine vs Async Await. Combine came out like 5 years ago (maybe?). But GCD is not deprecated and still works. There was no developer penalty for using GCD and skipping Combine entirely (other than FOMO).
  654.  
  655. When/if SwiftUI becomes a requirement, I&#039;m moving to a third party cross platform framework.
  656.  
  657. --
  658.  
  659. Also thanks for mentioning your issues with DTS.
  660.  
  661. &quot;First, you’ll be lucky to get a response. Second, if you do get a response, it will probably take multiple back and forths before the responder acknowledges what you can prove is occurring. Then they’ll likely state this is expected behaviour, note that you should have known this – despite their being no known public human record of this ‘known’ behaviour on the internet – and close the ticket as completed.&quot;
  662.  
  663. In the past DTS was very helpful to me but recently I&#039;ve been treated this way. The last couple tickets I filed were ignored completely and I was told to make a post on the developer forums instead. My post was ignored. Do they even do DTS anymore?]]></description>
  664. <content:encoded><![CDATA[<p>Thanks for your blog post. You were spot on talking about how Swift/SwiftUI is like chasing a moving target. I've decided not to do it. You talked about how devs are basically in an abusive relationship and I agree. </p>
  665. <p>Apple's hard push on new APIs often has developers scrambling (myself included). People who work inside Apple have their own interests/agendas that don't always align with ours. </p>
  666. <p>Ideally an approaching WWDC should be an exiting time for developers. I *should* get the feeling that Apple is going to introduce all these new features that can integrate into my app that is going to make my life EASIER and better. But instead I get a feeling of dread. What APIs that are important to me are they going to deprecate? What's going to break? What new half-implemented features are they going to try to push on me?</p>
  667. <p>Everyone feels they *need* to move to SwiftUI or else ( Sonos, Overcast etc.)...but that isn't the approach I'm taking. Apple's messaging has a lot to do with these feelings but they so often mislead us.</p>
  668. <p>You talked about GCD vs Combine vs Async Await. Combine came out like 5 years ago (maybe?). But GCD is not deprecated and still works. There was no developer penalty for using GCD and skipping Combine entirely (other than FOMO).</p>
  669. <p>When/if SwiftUI becomes a requirement, I'm moving to a third party cross platform framework. </p>
  670. <p>--</p>
  671. <p>Also thanks for mentioning your issues with DTS.</p>
  672. <p>"First, you’ll be lucky to get a response. Second, if you do get a response, it will probably take multiple back and forths before the responder acknowledges what you can prove is occurring. Then they’ll likely state this is expected behaviour, note that you should have known this – despite their being no known public human record of this ‘known’ behaviour on the internet – and close the ticket as completed."</p>
  673. <p>In the past DTS was very helpful to me but recently I've been treated this way. The last couple tickets I filed were ignored completely and I was told to make a post on the developer forums instead. My post was ignored. Do they even do DTS anymore?</p>
  674. ]]></content:encoded>
  675. </item>
  676. <item>
  677. <title>
  678. Comment on Why Companies Don&#8217;t Fix Bugs by Vadim </title>
  679. <link>https://mjtsai.com/blog/2025/04/09/why-companies-dont-fix-bugs/#comment-4248175</link>
  680.  
  681. <dc:creator><![CDATA[Vadim]]></dc:creator>
  682. <pubDate>Fri, 11 Apr 2025 13:12:21 +0000</pubDate>
  683. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47362#comment-4248175</guid>
  684.  
  685. <description><![CDATA[@michael: the “Tim” link seems to be pointing to the wrong page - it’s the same page as the previous link. Can you fix that?]]></description>
  686. <content:encoded><![CDATA[<p>@michael: the “Tim” link seems to be pointing to the wrong page - it’s the same page as the previous link. Can you fix that?</p>
  687. ]]></content:encoded>
  688. </item>
  689. <item>
  690. <title>
  691. Comment on How Apple Fumbled Siri&#8217;s AI Makeover by Kristoffer </title>
  692. <link>https://mjtsai.com/blog/2025/04/10/how-apple-fumbled-siris-ai-makeover/#comment-4248016</link>
  693.  
  694. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  695. <pubDate>Fri, 11 Apr 2025 04:23:12 +0000</pubDate>
  696. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47373#comment-4248016</guid>
  697.  
  698. <description><![CDATA[I actually agree with Gianandrea if he&#039;s talking as a voice assistant.
  699.  
  700. I enjoy chatGPT as a pair programmet, but as a lying voice assistant not so much.]]></description>
  701. <content:encoded><![CDATA[<p>I actually agree with Gianandrea if he's talking as a voice assistant. </p>
  702. <p>I enjoy chatGPT as a pair programmet, but as a lying voice assistant not so much.</p>
  703. ]]></content:encoded>
  704. </item>
  705. <item>
  706. <title>
  707. Comment on Soured by Matthew Bickham </title>
  708. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4248012</link>
  709.  
  710. <dc:creator><![CDATA[Matthew Bickham]]></dc:creator>
  711. <pubDate>Fri, 11 Apr 2025 03:58:40 +0000</pubDate>
  712. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4248012</guid>
  713.  
  714. <description><![CDATA[@ObjC4Life re:
  715.  
  716. &#062; Seems like Matthew&#039;s feelings on SwiftUI may have changed a bit since last July?
  717.  
  718. I wouldn&#039;t say those feelings for that particular technology has changed. What I said back then it still my position:
  719.  
  720. &#062; Personally I prefer working in SwiftUI now – probably because I no longer need to implement two similar UIs in both UIKit and AppKit.
  721.  
  722. So in my particular situation, for my particular app, I feel SwiftUI is a good approach. My expertise in AppKit and UIKit wasn&#039;t the best, so I did always feel that using those technologies, especially with Storyboards, was incredibly fragile and prone to breakage.
  723.  
  724. Despite its&#039; problems, I don&#039;t feel that way with using SwiftUI. Though I do keep my usage of SwiftUI to some of the less high-level components, which I find are the least polished. I also need to support earlier versions of iOS and macOS so cannot use some of the newer SwiftUI apis for backwards compatibility reasons.
  725.  
  726. Though saying all of that, both SwiftUI and Swift, are still part of the constant maintenance treadmill that I wrote about.
  727.  
  728. The Swift 6 language mode is another one of those technical debt items that eventually everyone will have to work through which will bring little real benefit, but lots of extra work, to most normal app developers.
  729.  
  730. The rumoured OS-wide redesign slated for iOS and macOS, is another dreaded item that will likely have to be supported in one way or another. When these things come around, I do look jealously at cross platform electron apps (that have eschewed native platform conventions completely) and can simply ignore Apple&#039;s increasingly erratic UI and language changes.]]></description>
  731. <content:encoded><![CDATA[<p>@ObjC4Life re: </p>
  732. <p>&gt; Seems like Matthew's feelings on SwiftUI may have changed a bit since last July?</p>
  733. <p>I wouldn't say those feelings for that particular technology has changed. What I said back then it still my position:</p>
  734. <p>&gt; Personally I prefer working in SwiftUI now – probably because I no longer need to implement two similar UIs in both UIKit and AppKit.</p>
  735. <p>So in my particular situation, for my particular app, I feel SwiftUI is a good approach. My expertise in AppKit and UIKit wasn't the best, so I did always feel that using those technologies, especially with Storyboards, was incredibly fragile and prone to breakage.</p>
  736. <p>Despite its' problems, I don't feel that way with using SwiftUI. Though I do keep my usage of SwiftUI to some of the less high-level components, which I find are the least polished. I also need to support earlier versions of iOS and macOS so cannot use some of the newer SwiftUI apis for backwards compatibility reasons.</p>
  737. <p>Though saying all of that, both SwiftUI and Swift, are still part of the constant maintenance treadmill that I wrote about.</p>
  738. <p>The Swift 6 language mode is another one of those technical debt items that eventually everyone will have to work through which will bring little real benefit, but lots of extra work, to most normal app developers.</p>
  739. <p>The rumoured OS-wide redesign slated for iOS and macOS, is another dreaded item that will likely have to be supported in one way or another. When these things come around, I do look jealously at cross platform electron apps (that have eschewed native platform conventions completely) and can simply ignore Apple's increasingly erratic UI and language changes.</p>
  740. ]]></content:encoded>
  741. </item>
  742. <item>
  743. <title>
  744. Comment on Awaiting APIs by Anonymous </title>
  745. <link>https://mjtsai.com/blog/2025/04/10/awaiting-apis/#comment-4247987</link>
  746.  
  747. <dc:creator><![CDATA[Anonymous]]></dc:creator>
  748. <pubDate>Fri, 11 Apr 2025 02:37:00 +0000</pubDate>
  749. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47377#comment-4247987</guid>
  750.  
  751. <description><![CDATA[Who is responsible for this…Schaffer that you bozo?]]></description>
  752. <content:encoded><![CDATA[<p>Who is responsible for this…Schaffer that you bozo?</p>
  753. ]]></content:encoded>
  754. </item>
  755. <item>
  756. <title>
  757. Comment on How Apple Fumbled Siri&#8217;s AI Makeover by Léo Natan </title>
  758. <link>https://mjtsai.com/blog/2025/04/10/how-apple-fumbled-siris-ai-makeover/#comment-4247899</link>
  759.  
  760. <dc:creator><![CDATA[Léo Natan]]></dc:creator>
  761. <pubDate>Thu, 10 Apr 2025 21:08:34 +0000</pubDate>
  762. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47373#comment-4247899</guid>
  763.  
  764. <description><![CDATA[&#062; Apple AI chief John Giannandrea
  765. &#062; Giannandrea told employees that he didn’t believe chatbots like ChatGPT added much value for users
  766.  
  767. Quality leadership at Apple, assembled in California <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f926-200d-2642-fe0f.png" alt="🤦‍♂️" class="wp-smiley" style="height: 1em; max-height: 1em;" />]]></description>
  768. <content:encoded><![CDATA[<p>&gt; Apple AI chief John Giannandrea<br />
  769. &gt; Giannandrea told employees that he didn’t believe chatbots like ChatGPT added much value for users</p>
  770. <p>Quality leadership at Apple, assembled in California 🤦‍♂️</p>
  771. ]]></content:encoded>
  772. </item>
  773. <item>
  774. <title>
  775. Comment on Soured by Bri </title>
  776. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247875</link>
  777.  
  778. <dc:creator><![CDATA[Bri]]></dc:creator>
  779. <pubDate>Thu, 10 Apr 2025 19:34:22 +0000</pubDate>
  780. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247875</guid>
  781.  
  782. <description><![CDATA[I&#039;ve recently been working on developing for old 68k Macs. It&#039;s been loads of fun! Even with things being so much more archaic than what we&#039;re used to today, there&#039;s a magic there that&#039;s absolutely lost in modern Apple. Modern Apple is nothing like the Apple from 80s and 90s. Modern Apple is basically another Microsoft.
  783.  
  784. So what I wonder is... how can we get that magic back again? Is there any chance at all for having a computer that&#039;s fun, creative and productive like classic Macs were? Or like Macs circa 2010, when Snow Leopard was the latest and greatest, and everything &quot;just worked&quot;?
  785.  
  786. It feels like the only possible option is jumping to Linux, and while there&#039;s certainly freedom to be had there, I&#039;ve never found it to be that magical. At least in my experience so far, it&#039;s lacking vision, coherence, and the human touch. Everything is patchwork, designed in haste by programmers who are only technically minded and not trying to make things that are actually pleasant to interact with. There&#039;s tons of bickering about the right way to do things, so nothing ever gets streamlined. It&#039;s not like classic Mac OS or Mac OS X at all. At least, not in any of the distros I&#039;ve tried.
  787.  
  788. Is our only hope something like an eccentric billionaire deciding to fund a new operating system with these explicit goals, and not caring at all about commercial success?]]></description>
  789. <content:encoded><![CDATA[<p>I've recently been working on developing for old 68k Macs. It's been loads of fun! Even with things being so much more archaic than what we're used to today, there's a magic there that's absolutely lost in modern Apple. Modern Apple is nothing like the Apple from 80s and 90s. Modern Apple is basically another Microsoft.</p>
  790. <p>So what I wonder is... how can we get that magic back again? Is there any chance at all for having a computer that's fun, creative and productive like classic Macs were? Or like Macs circa 2010, when Snow Leopard was the latest and greatest, and everything "just worked"?</p>
  791. <p>It feels like the only possible option is jumping to Linux, and while there's certainly freedom to be had there, I've never found it to be that magical. At least in my experience so far, it's lacking vision, coherence, and the human touch. Everything is patchwork, designed in haste by programmers who are only technically minded and not trying to make things that are actually pleasant to interact with. There's tons of bickering about the right way to do things, so nothing ever gets streamlined. It's not like classic Mac OS or Mac OS X at all. At least, not in any of the distros I've tried.</p>
  792. <p>Is our only hope something like an eccentric billionaire deciding to fund a new operating system with these explicit goals, and not caring at all about commercial success?</p>
  793. ]]></content:encoded>
  794. </item>
  795. <item>
  796. <title>
  797. Comment on Why Companies Don&#8217;t Fix Bugs by wilt </title>
  798. <link>https://mjtsai.com/blog/2025/04/09/why-companies-dont-fix-bugs/#comment-4247821</link>
  799.  
  800. <dc:creator><![CDATA[wilt]]></dc:creator>
  801. <pubDate>Thu, 10 Apr 2025 16:56:01 +0000</pubDate>
  802. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47362#comment-4247821</guid>
  803.  
  804. <description><![CDATA[I wonder what one can expect from a company whose first tier support operators are obviously drilled to urge customers (I was about writing &quot;users&quot;) to update for whatever issue they&#039;re reporting, to  follow insane &quot;diagnostic&quot; procedures, to deny the very possibility a huge bug (known to Apple) is at stake. My two calls to Apple Support over last years were both of this kind. One operator was so kind and enthusiast that I hadn&#039;t the heart to let him down and, as we were sharing screen, I proceeded to trash right away all launchagents and daemons in main Library (including Little Snitch&#039;s, Microsoft Office&#039;s etc) that were certainly responsible for my Mac issue. And I screwed everything up of my own free will. I read on the web of a mythical second tier support operators (engineers?) who most likely are at least more proficient at telling lies.]]></description>
  805. <content:encoded><![CDATA[<p>I wonder what one can expect from a company whose first tier support operators are obviously drilled to urge customers (I was about writing "users") to update for whatever issue they're reporting, to  follow insane "diagnostic" procedures, to deny the very possibility a huge bug (known to Apple) is at stake. My two calls to Apple Support over last years were both of this kind. One operator was so kind and enthusiast that I hadn't the heart to let him down and, as we were sharing screen, I proceeded to trash right away all launchagents and daemons in main Library (including Little Snitch's, Microsoft Office's etc) that were certainly responsible for my Mac issue. And I screwed everything up of my own free will. I read on the web of a mythical second tier support operators (engineers?) who most likely are at least more proficient at telling lies.</p>
  806. ]]></content:encoded>
  807. </item>
  808. <item>
  809. <title>
  810. Comment on Soured by ObjC4Life </title>
  811. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247774</link>
  812.  
  813. <dc:creator><![CDATA[ObjC4Life]]></dc:creator>
  814. <pubDate>Thu, 10 Apr 2025 13:35:46 +0000</pubDate>
  815. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247774</guid>
  816.  
  817. <description><![CDATA[&quot;If you’re an indie Apple developer, you’re on a treadmill that never slows down.
  818.  
  819. Apple’s annual OS updates mean a constant stream of changes, and unlike Apple — where teams of engineers handle updates — you’re expected to keep up with everything solo. The annual OS release cycle forces developers to scramble to update their apps, even if nothing is broken.
  820.  
  821. Apple’s constant API changes and deprecations create an ongoing headache for developers. Swift and SwiftUI continue to evolve so quickly that learning them feels like chasing a moving target, with major shifts that often require rewriting large portions of code.
  822.  
  823. StoreKit changes made in-app purchases a moving target as well, forcing developers to adapt to new implementations. StoreKit 2 completely changed the API structure, forcing rewrites to systems that had been working for years.
  824.  
  825. Other examples abound: UIKit and AppKit developers had to rethink entire UI structures when Apple pushed SwiftUI as the future. Core Data, long a staple for managing persistence, has been overshadowed by SwiftData, requiring yet another major shift. The introduction of new concurrency models — first Grand Central Dispatch, then Combine, and now async/await — may mean rewriting asynchronous code multiple times over in just a few years.
  826.  
  827. For Apple, these changes represent progress. For developers, they represent an endless cycle of busy maintenance work that doesn’t always improve their apps, but is necessary just to keep them running.&quot;
  828.  
  829. Being expected to reimplement entire codebases constantly for a &quot;new API&quot; is absurd. Usually the new API isn&#039;t an enhancement at all and just makes things worse and often results in us actually losing API features rather than gaining. &quot;I didn&#039;t implement this someone else did years, let&#039;s rewrite it in Swift&quot; seems more like Apple&#039;s attitude/goal. Throwaway years of polish just to chase a new language is a mistake. Sucks to read that someone with a popular app now recommends against developing on Apple platforms. Apple is doing a great job fucking up dev relations.
  830.  
  831. Seems like Matthew&#039;s feelings on SwiftUI may have changed a bit since last July? https://mjtsai.com/blog/2024/07/29/magic-lasso-redesigned/  
  832.  
  833. Swift / SwiftUI has been a disaster for all parties.  AppKit/UIKit still work just fine. I recommend devs not move to SwiftUI. Developer pushback can help Apple realize (faster) that SwiftUI was a mistake. I think some people at Apple already know this but can&#039;t say it...]]></description>
  834. <content:encoded><![CDATA[<p>"If you’re an indie Apple developer, you’re on a treadmill that never slows down.</p>
  835. <p>Apple’s annual OS updates mean a constant stream of changes, and unlike Apple — where teams of engineers handle updates — you’re expected to keep up with everything solo. The annual OS release cycle forces developers to scramble to update their apps, even if nothing is broken.</p>
  836. <p>Apple’s constant API changes and deprecations create an ongoing headache for developers. Swift and SwiftUI continue to evolve so quickly that learning them feels like chasing a moving target, with major shifts that often require rewriting large portions of code.</p>
  837. <p>StoreKit changes made in-app purchases a moving target as well, forcing developers to adapt to new implementations. StoreKit 2 completely changed the API structure, forcing rewrites to systems that had been working for years.</p>
  838. <p>Other examples abound: UIKit and AppKit developers had to rethink entire UI structures when Apple pushed SwiftUI as the future. Core Data, long a staple for managing persistence, has been overshadowed by SwiftData, requiring yet another major shift. The introduction of new concurrency models — first Grand Central Dispatch, then Combine, and now async/await — may mean rewriting asynchronous code multiple times over in just a few years.</p>
  839. <p>For Apple, these changes represent progress. For developers, they represent an endless cycle of busy maintenance work that doesn’t always improve their apps, but is necessary just to keep them running."</p>
  840. <p>Being expected to reimplement entire codebases constantly for a "new API" is absurd. Usually the new API isn't an enhancement at all and just makes things worse and often results in us actually losing API features rather than gaining. "I didn't implement this someone else did years, let's rewrite it in Swift" seems more like Apple's attitude/goal. Throwaway years of polish just to chase a new language is a mistake. Sucks to read that someone with a popular app now recommends against developing on Apple platforms. Apple is doing a great job fucking up dev relations. </p>
  841. <p>Seems like Matthew's feelings on SwiftUI may have changed a bit since last July? <a href="https://mjtsai.com/blog/2024/07/29/magic-lasso-redesigned/" rel="ugc">https://mjtsai.com/blog/2024/07/29/magic-lasso-redesigned/</a>  </p>
  842. <p> Swift / SwiftUI has been a disaster for all parties.  AppKit/UIKit still work just fine. I recommend devs not move to SwiftUI. Developer pushback can help Apple realize (faster) that SwiftUI was a mistake. I think some people at Apple already know this but can't say it...</p>
  843. ]]></content:encoded>
  844. </item>
  845. <item>
  846. <title>
  847. Comment on Soured by Kristoffer </title>
  848. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247766</link>
  849.  
  850. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  851. <pubDate>Thu, 10 Apr 2025 13:06:38 +0000</pubDate>
  852. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247766</guid>
  853.  
  854. <description><![CDATA[@Bart Americans love hair. They can&#039;t disrespect a guy with loads of hair. It really is as simple as that.]]></description>
  855. <content:encoded><![CDATA[<p>@Bart Americans love hair. They can't disrespect a guy with loads of hair. It really is as simple as that.</p>
  856. ]]></content:encoded>
  857. </item>
  858. <item>
  859. <title>
  860. Comment on Soured by Software Tyrannosaur </title>
  861. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247736</link>
  862.  
  863. <dc:creator><![CDATA[Software Tyrannosaur]]></dc:creator>
  864. <pubDate>Thu, 10 Apr 2025 09:43:25 +0000</pubDate>
  865. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247736</guid>
  866.  
  867. <description><![CDATA[There is no reason to have Macs on a 12-month release schedule or keep it in lock step with iOS because of services.  If the backend processes for services are that embedded into the OS THAT is a problem.  They could rework the relevant bit to accommodate the new iOS and incorporate that without jacking up the entire codebase.  With every iteration Apple makes it tougher to troubleshoot and manage the Mac by locking stuff down in the name of &quot;security&quot;.  Nuts.  I left Windows behind more than 20 years ago because of the black hole that was the registry.  Now I need to tweak system bits and deal with the death of kernel extensions, Mail extensions and Safari extensions because dog forbid that anyone might want to do something Apple has decided isn&#039;t in their best interests.]]></description>
  868. <content:encoded><![CDATA[<p>There is no reason to have Macs on a 12-month release schedule or keep it in lock step with iOS because of services.  If the backend processes for services are that embedded into the OS THAT is a problem.  They could rework the relevant bit to accommodate the new iOS and incorporate that without jacking up the entire codebase.  With every iteration Apple makes it tougher to troubleshoot and manage the Mac by locking stuff down in the name of "security".  Nuts.  I left Windows behind more than 20 years ago because of the black hole that was the registry.  Now I need to tweak system bits and deal with the death of kernel extensions, Mail extensions and Safari extensions because dog forbid that anyone might want to do something Apple has decided isn't in their best interests.</p>
  869. ]]></content:encoded>
  870. </item>
  871. <item>
  872. <title>
  873. Comment on Why Companies Don&#8217;t Fix Bugs by Software Tyrannosaur </title>
  874. <link>https://mjtsai.com/blog/2025/04/09/why-companies-dont-fix-bugs/#comment-4247735</link>
  875.  
  876. <dc:creator><![CDATA[Software Tyrannosaur]]></dc:creator>
  877. <pubDate>Thu, 10 Apr 2025 09:33:25 +0000</pubDate>
  878. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47362#comment-4247735</guid>
  879.  
  880. <description><![CDATA[I had a similar experience working more than 2 decades for another large Silicon Valley tech firm.  When I started it was like Google.  In one of my interviews I was told that if what I did was good for the customer, good for my team or good for the company, in that order, I wouldn&#039;t be punished if I failed.  That shifted as the company grow and the MBAs moved in.  Now it&#039;s simply down to juggling the numbers to look good for Wall Street every quarter.  They haven&#039;t come out with a new product in years and just keep milking their cash cow while laying off left right and centre to goose that bottom line.  I got out before they hit the iceberg that is coming.
  881.  
  882. As to the other thread about developers being sour, when I started at the same company in the 90s their code base was a huge monolithic blob where fixing a bug in one feature sometimes broke something somewhere else.   I remember filing the same bug report 3 times because of the fix/break scenario.  The final time I ran dtrace, found the offending line in the source and attached it to the bug report with the fix because I (and the customers) were tired of the constant break/fix repeat scenario.
  883.  
  884. I discussed this with a VP in software development and suggested an approach similar to what I saw with IBM.  Rework out code base to make it modular and patchable so that if something broke we could issue a patch for that specific bug without having to upgrade the entire image.  His response was that as much as that is an excellent engineering solution it isn&#039;t sexy enough to get the required funding because it involves no new features, no new products, nothing other than more stable software.  But if I could prove that such an effort would lead to increased revenue he&#039;d try to sell it.  That&#039;s the mentality in the C-suites, new features = more revenue.  
  885.  
  886. As for Apple, they&#039;ve been trying to make macos into IOS for years now, something I predicted years ago.  Forget that it&#039;s a different use case and lock it down.  Catalyst anyone?  The net result is that if I didn&#039;t didn&#039;t have a bunch of Mac-only apps I&#039;d have moved on by now.  That and unfortunately Linux always promises a great user experience but rarely if ever delivers.]]></description>
  887. <content:encoded><![CDATA[<p>I had a similar experience working more than 2 decades for another large Silicon Valley tech firm.  When I started it was like Google.  In one of my interviews I was told that if what I did was good for the customer, good for my team or good for the company, in that order, I wouldn't be punished if I failed.  That shifted as the company grow and the MBAs moved in.  Now it's simply down to juggling the numbers to look good for Wall Street every quarter.  They haven't come out with a new product in years and just keep milking their cash cow while laying off left right and centre to goose that bottom line.  I got out before they hit the iceberg that is coming.</p>
  888. <p>As to the other thread about developers being sour, when I started at the same company in the 90s their code base was a huge monolithic blob where fixing a bug in one feature sometimes broke something somewhere else.   I remember filing the same bug report 3 times because of the fix/break scenario.  The final time I ran dtrace, found the offending line in the source and attached it to the bug report with the fix because I (and the customers) were tired of the constant break/fix repeat scenario.</p>
  889. <p>I discussed this with a VP in software development and suggested an approach similar to what I saw with IBM.  Rework out code base to make it modular and patchable so that if something broke we could issue a patch for that specific bug without having to upgrade the entire image.  His response was that as much as that is an excellent engineering solution it isn't sexy enough to get the required funding because it involves no new features, no new products, nothing other than more stable software.  But if I could prove that such an effort would lead to increased revenue he'd try to sell it.  That's the mentality in the C-suites, new features = more revenue.  </p>
  890. <p>As for Apple, they've been trying to make macos into IOS for years now, something I predicted years ago.  Forget that it's a different use case and lock it down.  Catalyst anyone?  The net result is that if I didn't didn't have a bunch of Mac-only apps I'd have moved on by now.  That and unfortunately Linux always promises a great user experience but rarely if ever delivers.</p>
  891. ]]></content:encoded>
  892. </item>
  893. <item>
  894. <title>
  895. Comment on Soured by Tomáš Kafka </title>
  896. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247732</link>
  897.  
  898. <dc:creator><![CDATA[Tomáš Kafka]]></dc:creator>
  899. <pubDate>Thu, 10 Apr 2025 09:28:11 +0000</pubDate>
  900. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247732</guid>
  901.  
  902. <description><![CDATA[Last week I filled a bug report for retracting a WWDC talk (Efficiency awaits: Background tasks in SwiftUI) that presents  APIs that are either unfinished or not implemented at all even almost 3 years later.
  903.  
  904. https://x.com/tomaskafka/status/1907003833546657803
  905.  
  906. I wasted at least a day on this, finding forum and StackOverflow posts of many others who got burned as well.
  907.  
  908. And in the end, @eskimo told me to file a bug against the talk: https://developer.apple.com/forums/thread/726443?answerId=823711022&#038;page=1#832295022
  909.  
  910. I don’t expect anything to happen, but man, the comment section on PHP documentation was a godsend for centralizing these kinds of corrections and real world implementation experiences.]]></description>
  911. <content:encoded><![CDATA[<p>Last week I filled a bug report for retracting a WWDC talk (Efficiency awaits: Background tasks in SwiftUI) that presents  APIs that are either unfinished or not implemented at all even almost 3 years later.</p>
  912. <p><a href="https://x.com/tomaskafka/status/1907003833546657803" rel="nofollow ugc">https://x.com/tomaskafka/status/1907003833546657803</a></p>
  913. <p>I wasted at least a day on this, finding forum and StackOverflow posts of many others who got burned as well.</p>
  914. <p>And in the end, @eskimo told me to file a bug against the talk: <a href="https://developer.apple.com/forums/thread/726443?answerId=823711022&#038;page=1#832295022" rel="nofollow ugc">https://developer.apple.com/forums/thread/726443?answerId=823711022&#038;page=1#832295022</a></p>
  915. <p>I don’t expect anything to happen, but man, the comment section on PHP documentation was a godsend for centralizing these kinds of corrections and real world implementation experiences.</p>
  916. ]]></content:encoded>
  917. </item>
  918. <item>
  919. <title>
  920. Comment on Soured by Plume </title>
  921. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247689</link>
  922.  
  923. <dc:creator><![CDATA[Plume]]></dc:creator>
  924. <pubDate>Thu, 10 Apr 2025 07:05:46 +0000</pubDate>
  925. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247689</guid>
  926.  
  927. <description><![CDATA[&#062;porting their products to Linux
  928.  
  929. One nice thing about using open source is that you can fix bugs that bother you. In my experience, maintainers are always super grateful if you do.
  930.  
  931. And if you can&#039;t code, you can still set bounties.]]></description>
  932. <content:encoded><![CDATA[<p>&gt;porting their products to Linux</p>
  933. <p>One nice thing about using open source is that you can fix bugs that bother you. In my experience, maintainers are always super grateful if you do.</p>
  934. <p>And if you can't code, you can still set bounties.</p>
  935. ]]></content:encoded>
  936. </item>
  937. <item>
  938. <title>
  939. Comment on Why Companies Don&#8217;t Fix Bugs by CowMonkey </title>
  940. <link>https://mjtsai.com/blog/2025/04/09/why-companies-dont-fix-bugs/#comment-4247657</link>
  941.  
  942. <dc:creator><![CDATA[CowMonkey]]></dc:creator>
  943. <pubDate>Thu, 10 Apr 2025 04:29:21 +0000</pubDate>
  944. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47362#comment-4247657</guid>
  945.  
  946. <description><![CDATA[@Bart: it is interesting that they are pushing &quot;New Outlook&quot; like this, as it is obviously way, way worse than the established version. The new one is, as all apps are, just a shell to their web interface; missing essential features (try dragging an attachment out of an email to your desktop for example).
  947.  
  948. I&#039;m probably missing the situational awareness that is necessary to understand why such decisions and the one for a MS account are being made - it doesn&#039;t feel like such changes are in the users interest.]]></description>
  949. <content:encoded><![CDATA[<p>@Bart: it is interesting that they are pushing "New Outlook" like this, as it is obviously way, way worse than the established version. The new one is, as all apps are, just a shell to their web interface; missing essential features (try dragging an attachment out of an email to your desktop for example).</p>
  950. <p>I'm probably missing the situational awareness that is necessary to understand why such decisions and the one for a MS account are being made - it doesn't feel like such changes are in the users interest.</p>
  951. ]]></content:encoded>
  952. </item>
  953. <item>
  954. <title>
  955. Comment on Soured by Wu Ming </title>
  956. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247635</link>
  957.  
  958. <dc:creator><![CDATA[Wu Ming]]></dc:creator>
  959. <pubDate>Thu, 10 Apr 2025 02:59:14 +0000</pubDate>
  960. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247635</guid>
  961.  
  962. <description><![CDATA[Scott Forstall should be back into the company he greatly helped to become successful. And begin tiding up.]]></description>
  963. <content:encoded><![CDATA[<p>Scott Forstall should be back into the company he greatly helped to become successful. And begin tiding up.</p>
  964. ]]></content:encoded>
  965. </item>
  966. <item>
  967. <title>
  968. Comment on Soured by Someone </title>
  969. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247628</link>
  970.  
  971. <dc:creator><![CDATA[Someone]]></dc:creator>
  972. <pubDate>Thu, 10 Apr 2025 02:14:02 +0000</pubDate>
  973. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247628</guid>
  974.  
  975. <description><![CDATA[Maybe developers, instead of complaining and continuing to develop for Apple hardware, should stop work on Apple kit, and devote themselves to porting their products to Linux. KDE Plasma / Qt. Gnome, these are all workable setups.
  976.  
  977. As long as developers have users who rely on their software, and they&#039;re Mac / iOS only, they&#039;re part of the problem preventing Apple&#039;s bad software from having any consequence.
  978.  
  979. @Bart Yes, Federighi has been a disaster of greater proportion than when Jonny Ive was operating without Steve Jobs. But damn, he has nice hair, so I guess no consequences.]]></description>
  980. <content:encoded><![CDATA[<p>Maybe developers, instead of complaining and continuing to develop for Apple hardware, should stop work on Apple kit, and devote themselves to porting their products to Linux. KDE Plasma / Qt. Gnome, these are all workable setups.</p>
  981. <p>As long as developers have users who rely on their software, and they're Mac / iOS only, they're part of the problem preventing Apple's bad software from having any consequence.</p>
  982. <p>@Bart Yes, Federighi has been a disaster of greater proportion than when Jonny Ive was operating without Steve Jobs. But damn, he has nice hair, so I guess no consequences.</p>
  983. ]]></content:encoded>
  984. </item>
  985. <item>
  986. <title>
  987. Comment on Soured by Matthew Bickham </title>
  988. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247597</link>
  989.  
  990. <dc:creator><![CDATA[Matthew Bickham]]></dc:creator>
  991. <pubDate>Thu, 10 Apr 2025 00:22:18 +0000</pubDate>
  992. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247597</guid>
  993.  
  994. <description><![CDATA[@Michael if these stats are correct:
  995.  
  996. https://www.statista.com/statistics/1485088/app-revenue-distribution-by-category-worldwide/
  997.  
  998. As at mid-2024, Games made up 55% of app revenue worldwide, with Entertainment at 14% and Photo and video at 8%.
  999.  
  1000. This is total app revenue, not just the Apple App Store app revenue, so it&#039;s probably not 100% correct but in the ballpark of accuracy.]]></description>
  1001. <content:encoded><![CDATA[<p>@Michael if these stats are correct:</p>
  1002. <p><a href="https://www.statista.com/statistics/1485088/app-revenue-distribution-by-category-worldwide/" rel="nofollow ugc">https://www.statista.com/statistics/1485088/app-revenue-distribution-by-category-worldwide/</a></p>
  1003. <p>As at mid-2024, Games made up 55% of app revenue worldwide, with Entertainment at 14% and Photo and video at 8%.</p>
  1004. <p>This is total app revenue, not just the Apple App Store app revenue, so it's probably not 100% correct but in the ballpark of accuracy.</p>
  1005. ]]></content:encoded>
  1006. </item>
  1007. <item>
  1008. <title>
  1009. Comment on Soured by Michael Tsai </title>
  1010. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247590</link>
  1011.  
  1012. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  1013. <pubDate>Thu, 10 Apr 2025 00:08:17 +0000</pubDate>
  1014. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247590</guid>
  1015.  
  1016. <description><![CDATA[@Matthew And I wonder if the App Store revenue is still mostly from games.]]></description>
  1017. <content:encoded><![CDATA[<p>@Matthew And I wonder if the App Store revenue is still mostly from games.</p>
  1018. ]]></content:encoded>
  1019. </item>
  1020. <item>
  1021. <title>
  1022. Comment on Why Companies Don&#8217;t Fix Bugs by BentoCorp </title>
  1023. <link>https://mjtsai.com/blog/2025/04/09/why-companies-dont-fix-bugs/#comment-4247582</link>
  1024.  
  1025. <dc:creator><![CDATA[BentoCorp]]></dc:creator>
  1026. <pubDate>Wed, 09 Apr 2025 23:43:03 +0000</pubDate>
  1027. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47362#comment-4247582</guid>
  1028.  
  1029. <description><![CDATA[As an indie developer, one of the best things I did was to make the feedback and support email accessible to users and come directly to my inbox to handle.
  1030.  
  1031. Seeing multiple bugs or queries on the same issue is annoying, but also a great motivator to fix those issues – both in order to improve the product quality, but also to reduce the load of having to constantly handle the same questions or issues.
  1032.  
  1033. I can pretty much judge the quality of the product by the volume of email. As time has gone on, and issues have been fixed, the volume has dropped dramatically.
  1034.  
  1035. I think in larger companies this is where the bug fixing downfall occurs. It&#039;s easy to be separate and put up a firewall between the constant and pressing issues that your customers are experiencing and what you prioritise as an organisation to do everyday.]]></description>
  1036. <content:encoded><![CDATA[<p>As an indie developer, one of the best things I did was to make the feedback and support email accessible to users and come directly to my inbox to handle.</p>
  1037. <p>Seeing multiple bugs or queries on the same issue is annoying, but also a great motivator to fix those issues – both in order to improve the product quality, but also to reduce the load of having to constantly handle the same questions or issues.</p>
  1038. <p>I can pretty much judge the quality of the product by the volume of email. As time has gone on, and issues have been fixed, the volume has dropped dramatically.</p>
  1039. <p>I think in larger companies this is where the bug fixing downfall occurs. It's easy to be separate and put up a firewall between the constant and pressing issues that your customers are experiencing and what you prioritise as an organisation to do everyday.</p>
  1040. ]]></content:encoded>
  1041. </item>
  1042. <item>
  1043. <title>
  1044. Comment on Soured by Matthew Bickham </title>
  1045. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247568</link>
  1046.  
  1047. <dc:creator><![CDATA[Matthew Bickham]]></dc:creator>
  1048. <pubDate>Wed, 09 Apr 2025 23:03:33 +0000</pubDate>
  1049. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247568</guid>
  1050.  
  1051. <description><![CDATA[@Bart agree that Craig does not get blamed for a lot of these issues, but I think as I wrote in the linked piece, that it goes further than a single exec.
  1052.  
  1053. The annual release cadence is almost entirely driven by the annual iPhone release cadence. Apple believes they need a new iOS with each new iPhone cycle in order to market the newness. Now with services, this inevitably ties all of their other device OS&#039;s together, including macOS, on the same release cycle to retain compatibility.
  1054.  
  1055. If we want to play blame the execs, from my little knowledge, I don&#039;t think Craig would be the main culprit in the deterioration of developer experience.
  1056.  
  1057. Every indication is that Phil Schiller is the main culprit behind the App Store&#039;s mafia style tactics, obviously supported and backed by Tim Cook. This is in order to continue to keep absolute software control, as well as to extract as much revenue as possible, in order to support their only growing revenue stream, which is &#039;services&#039;.
  1058.  
  1059. They are also doing a very clever magic trick each time they talk about their services. In financial calls and other PR pieces they always talk about services as if it is Apple Music, Apple TV+, iCloud etc. When in fact the reality is that an overwhelming majority of their services income and revenue is actually due to taxing 15-30% from developers on the App Store and getting $20+ billion per/annum by selling their users privacy to Google via the Google Search deal.
  1060.  
  1061. All the other Apple One services they like to talk about are all second-tier – when looking at it from a competitive marketshare standpoint – and bring in relatively little revenue or profit in comparison to App Store tax and the Google Search deal.]]></description>
  1062. <content:encoded><![CDATA[<p>@Bart agree that Craig does not get blamed for a lot of these issues, but I think as I wrote in the linked piece, that it goes further than a single exec.</p>
  1063. <p>The annual release cadence is almost entirely driven by the annual iPhone release cadence. Apple believes they need a new iOS with each new iPhone cycle in order to market the newness. Now with services, this inevitably ties all of their other device OS's together, including macOS, on the same release cycle to retain compatibility.</p>
  1064. <p>If we want to play blame the execs, from my little knowledge, I don't think Craig would be the main culprit in the deterioration of developer experience.</p>
  1065. <p>Every indication is that Phil Schiller is the main culprit behind the App Store's mafia style tactics, obviously supported and backed by Tim Cook. This is in order to continue to keep absolute software control, as well as to extract as much revenue as possible, in order to support their only growing revenue stream, which is 'services'.</p>
  1066. <p>They are also doing a very clever magic trick each time they talk about their services. In financial calls and other PR pieces they always talk about services as if it is Apple Music, Apple TV+, iCloud etc. When in fact the reality is that an overwhelming majority of their services income and revenue is actually due to taxing 15-30% from developers on the App Store and getting $20+ billion per/annum by selling their users privacy to Google via the Google Search deal.</p>
  1067. <p>All the other Apple One services they like to talk about are all second-tier – when looking at it from a competitive marketshare standpoint – and bring in relatively little revenue or profit in comparison to App Store tax and the Google Search deal.</p>
  1068. ]]></content:encoded>
  1069. </item>
  1070. <item>
  1071. <title>
  1072. Comment on Soured by someone </title>
  1073. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247555</link>
  1074.  
  1075. <dc:creator><![CDATA[someone]]></dc:creator>
  1076. <pubDate>Wed, 09 Apr 2025 22:31:36 +0000</pubDate>
  1077. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247555</guid>
  1078.  
  1079. <description><![CDATA[&quot;And, recently, they’ve made it worse by announcing stuff that they know won’t ship in the 0.0 release. This is spun as clever planning to deliver new delights throughout the year. But it seems more like a cope for squeezing more into the major release than they should.&quot;
  1080.  
  1081. We used to call this vaporware back in the days.]]></description>
  1082. <content:encoded><![CDATA[<p>"And, recently, they’ve made it worse by announcing stuff that they know won’t ship in the 0.0 release. This is spun as clever planning to deliver new delights throughout the year. But it seems more like a cope for squeezing more into the major release than they should."</p>
  1083. <p>We used to call this vaporware back in the days.</p>
  1084. ]]></content:encoded>
  1085. </item>
  1086. <item>
  1087. <title>
  1088. Comment on Unable to Send Messages With Apple Mail on macOS 15.4 by someone </title>
  1089. <link>https://mjtsai.com/blog/2025/04/09/unable-to-send-messages-with-apple-mail-on-macos-15-4/#comment-4247543</link>
  1090.  
  1091. <dc:creator><![CDATA[someone]]></dc:creator>
  1092. <pubDate>Wed, 09 Apr 2025 22:06:03 +0000</pubDate>
  1093. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47365#comment-4247543</guid>
  1094.  
  1095. <description><![CDATA[Could it be Apple Intelligence being invoked at this step to be able to suggest rewording the message?]]></description>
  1096. <content:encoded><![CDATA[<p>Could it be Apple Intelligence being invoked at this step to be able to suggest rewording the message?</p>
  1097. ]]></content:encoded>
  1098. </item>
  1099. <item>
  1100. <title>
  1101. Comment on Unable to Send Messages With Apple Mail on macOS 15.4 by Jerry </title>
  1102. <link>https://mjtsai.com/blog/2025/04/09/unable-to-send-messages-with-apple-mail-on-macos-15-4/#comment-4247542</link>
  1103.  
  1104. <dc:creator><![CDATA[Jerry]]></dc:creator>
  1105. <pubDate>Wed, 09 Apr 2025 22:00:43 +0000</pubDate>
  1106. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47365#comment-4247542</guid>
  1107.  
  1108. <description><![CDATA[What I have been seeing so far in 15.4 is that read messages sometimes will not be shown as being read. (You still have to get a sent message back into the Sent Messages folder in order to be allowed to “Send again” that some less clever person at Apple decided (some time ago now) was appropriate.)]]></description>
  1109. <content:encoded><![CDATA[<p>What I have been seeing so far in 15.4 is that read messages sometimes will not be shown as being read. (You still have to get a sent message back into the Sent Messages folder in order to be allowed to “Send again” that some less clever person at Apple decided (some time ago now) was appropriate.)</p>
  1110. ]]></content:encoded>
  1111. </item>
  1112. <item>
  1113. <title>
  1114. Comment on Why Companies Don&#8217;t Fix Bugs by Adam Maxwell </title>
  1115. <link>https://mjtsai.com/blog/2025/04/09/why-companies-dont-fix-bugs/#comment-4247537</link>
  1116.  
  1117. <dc:creator><![CDATA[Adam Maxwell]]></dc:creator>
  1118. <pubDate>Wed, 09 Apr 2025 21:32:11 +0000</pubDate>
  1119. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47362#comment-4247537</guid>
  1120.  
  1121. <description><![CDATA[I build furniture by hand for a hobby, and my first instinct was to point out that I intentionally do not finish the backs of cabinets: I leave roughsawn boards because this is a hallmark of antique, handmade furniture of a certain vintage. Hopefully my notional grandchildren will see them someday and realize they&#039;re descended from a madman who resawed 12&quot; wide boards by hand.
  1122.  
  1123. The point, though, is the same: I&#039;m trying to craft a bookcase that doesn&#039;t sag and lasts a long time, using traditional joinery where I allow for seasonal wood movement, and I make mouldings to cover the end grain and give it a more finished appearance. This is that &quot;back of the cabinet&quot; mentality that Apple used to have, where the end product was carefully fit together, did its job, and looked like it had been designed and crafted for a purpose.
  1124.  
  1125. Present-day Apple has a bunch of people who polish their parts of the system, but there&#039;s no cohesion or overall thought, and all those shiny buttons look like a polished heap of rabbit dung at the end of the day. I think Jobs could enforce standards within Apple, as he mostly had good taste (except for those damn iCal editable labels) and limited tolerance for usability problems. For 3rd parties, Interface Builder made it easy to get to 90% of the HIG, and users would complain and quote chapter and verse of the HIG until you finished the other 10% (&quot;yes, thank you for pointing out that the label at the bottom of BibDesk&#039;s editor windows is off by 2 points&quot;).
  1126.  
  1127. I&#039;m guessing iPod and iTunes worked pretty well because Jobs loved music and had a collection he&#039;d curated over decades, as I do, on physical media, and wanted access to it all the time. Marketdroids who have have never ripped a CD or used iTunes as a portable analogue of their home music collection will just see it as another place to put advertising, rather than something with intrinsic value on its own.]]></description>
  1128. <content:encoded><![CDATA[<p>I build furniture by hand for a hobby, and my first instinct was to point out that I intentionally do not finish the backs of cabinets: I leave roughsawn boards because this is a hallmark of antique, handmade furniture of a certain vintage. Hopefully my notional grandchildren will see them someday and realize they're descended from a madman who resawed 12" wide boards by hand.</p>
  1129. <p>The point, though, is the same: I'm trying to craft a bookcase that doesn't sag and lasts a long time, using traditional joinery where I allow for seasonal wood movement, and I make mouldings to cover the end grain and give it a more finished appearance. This is that "back of the cabinet" mentality that Apple used to have, where the end product was carefully fit together, did its job, and looked like it had been designed and crafted for a purpose.</p>
  1130. <p>Present-day Apple has a bunch of people who polish their parts of the system, but there's no cohesion or overall thought, and all those shiny buttons look like a polished heap of rabbit dung at the end of the day. I think Jobs could enforce standards within Apple, as he mostly had good taste (except for those damn iCal editable labels) and limited tolerance for usability problems. For 3rd parties, Interface Builder made it easy to get to 90% of the HIG, and users would complain and quote chapter and verse of the HIG until you finished the other 10% ("yes, thank you for pointing out that the label at the bottom of BibDesk's editor windows is off by 2 points").</p>
  1131. <p>I'm guessing iPod and iTunes worked pretty well because Jobs loved music and had a collection he'd curated over decades, as I do, on physical media, and wanted access to it all the time. Marketdroids who have have never ripped a CD or used iTunes as a portable analogue of their home music collection will just see it as another place to put advertising, rather than something with intrinsic value on its own.</p>
  1132. ]]></content:encoded>
  1133. </item>
  1134. <item>
  1135. <title>
  1136. Comment on Soured by Bart </title>
  1137. <link>https://mjtsai.com/blog/2025/04/09/soured/#comment-4247535</link>
  1138.  
  1139. <dc:creator><![CDATA[Bart]]></dc:creator>
  1140. <pubDate>Wed, 09 Apr 2025 21:16:59 +0000</pubDate>
  1141. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47360#comment-4247535</guid>
  1142.  
  1143. <description><![CDATA[Once again surprised at how Craig Federighi never comes up in all this. Is he not ultimately in charge of all software? Are not almost all of Apple&#039;s problems (aside from legal ones, and even some of those) software related?
  1144.  
  1145. Why does he just get to pop up in a pre-recorded video once a year, do something silly, announce some features which may or may not exist yet, and then just fast cut off into the sunset? Well, he then usually does a couple puff piece interviews with the same friendly journalists who ask the same softball, pre-approved questions.
  1146.  
  1147. If Tim isn&#039;t going to address it, shouldn&#039;t it fall to him?]]></description>
  1148. <content:encoded><![CDATA[<p>Once again surprised at how Craig Federighi never comes up in all this. Is he not ultimately in charge of all software? Are not almost all of Apple's problems (aside from legal ones, and even some of those) software related?</p>
  1149. <p>Why does he just get to pop up in a pre-recorded video once a year, do something silly, announce some features which may or may not exist yet, and then just fast cut off into the sunset? Well, he then usually does a couple puff piece interviews with the same friendly journalists who ask the same softball, pre-approved questions.</p>
  1150. <p>If Tim isn't going to address it, shouldn't it fall to him?</p>
  1151. ]]></content:encoded>
  1152. </item>
  1153. <item>
  1154. <title>
  1155. Comment on Why Companies Don&#8217;t Fix Bugs by Bart </title>
  1156. <link>https://mjtsai.com/blog/2025/04/09/why-companies-dont-fix-bugs/#comment-4247530</link>
  1157.  
  1158. <dc:creator><![CDATA[Bart]]></dc:creator>
  1159. <pubDate>Wed, 09 Apr 2025 21:07:25 +0000</pubDate>
  1160. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47362#comment-4247530</guid>
  1161.  
  1162. <description><![CDATA[Not to go on and on but even just today I had to deal with people being forced into &quot;New Outlook&quot; which broke their profile, but Microsoft doesn&#039;t actually care that the user&#039;s mail works. A popup comes up saying that New Outlook WILL be enabled on next startup, with the choices to either do it now or wait until restart. And since the &quot;New outlook ON/OFF&quot; toggle is still set to OFF, because the user never wanted it on, there&#039;s nothing they can do about it.
  1163.  
  1164. And so the timebomb goes off and it&#039;s New Outlook they get. For now they haven&#039;t removed the toggle, but they have gotten more and more aggressive. It replaces the shortcut for the Office 365 version, so even when that version is clicked on, New Outlook launches anyway. Launching it directly from the Program folder works, so they are hijacking the shortcut.
  1165.  
  1166. These are the kinds of things Microsoft, just for one specific example, spends its time on now. Fixing bugs, unless they are in the way of management engagement metrics, is simply not a consideration anymore. They don&#039;t have time. They have to hurry up and implement the next user hostile trick the psychology department has come up with to get .1% more users on Edge this month.]]></description>
  1167. <content:encoded><![CDATA[<p>Not to go on and on but even just today I had to deal with people being forced into "New Outlook" which broke their profile, but Microsoft doesn't actually care that the user's mail works. A popup comes up saying that New Outlook WILL be enabled on next startup, with the choices to either do it now or wait until restart. And since the "New outlook ON/OFF" toggle is still set to OFF, because the user never wanted it on, there's nothing they can do about it.</p>
  1168. <p>And so the timebomb goes off and it's New Outlook they get. For now they haven't removed the toggle, but they have gotten more and more aggressive. It replaces the shortcut for the Office 365 version, so even when that version is clicked on, New Outlook launches anyway. Launching it directly from the Program folder works, so they are hijacking the shortcut.</p>
  1169. <p>These are the kinds of things Microsoft, just for one specific example, spends its time on now. Fixing bugs, unless they are in the way of management engagement metrics, is simply not a consideration anymore. They don't have time. They have to hurry up and implement the next user hostile trick the psychology department has come up with to get .1% more users on Edge this month.</p>
  1170. ]]></content:encoded>
  1171. </item>
  1172. <item>
  1173. <title>
  1174. Comment on Why Companies Don&#8217;t Fix Bugs by Bart </title>
  1175. <link>https://mjtsai.com/blog/2025/04/09/why-companies-dont-fix-bugs/#comment-4247528</link>
  1176.  
  1177. <dc:creator><![CDATA[Bart]]></dc:creator>
  1178. <pubDate>Wed, 09 Apr 2025 21:00:38 +0000</pubDate>
  1179. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47362#comment-4247528</guid>
  1180.  
  1181. <description><![CDATA[Ah, a post directly relevant to my pet peeve.
  1182.  
  1183. I seem to recall people predicting this was coming even back in the 90s (maybe even before then) when we really started just pumping out MBAs and taking a Gordon Gecko mentality to absolutely every aspect of business.
  1184.  
  1185. It&#039;s also possible that those who have been around long enough were simply spoiled by a situation that couldn&#039;t continue to exist. When the Internet was young the people and companies using it and making software for it were doing it mostly because they loved it and it directly benefited them to help build it.
  1186.  
  1187. Now many of those successful companies have become incumbents or absorbed into the corporate machine and the entire situation has flipped.
  1188.  
  1189. To a degree, Google and Apple no longer have to care if the users like what they do. What are you gonna do, not use it? Same thing with Microsoft and what they keep doing to Windows. Nobody likes it, everyone hates it, the user hostility has gotten to the point of almost being blatant. But what are you gonna do, not use that Windows software that there is no replacement for?
  1190.  
  1191. It&#039;s not even about not fixing bugs. Now they are actively introducing hostile features like the strict enforcement of Microsoft accounts in Windows 11, patching out workarounds. It&#039;s almost laughable to think that they would fix bugs, their priorities are absolutely at the other end of the spectrum, far more focused on controlling what the users do in order to continue to funnel them into sales.]]></description>
  1192. <content:encoded><![CDATA[<p>Ah, a post directly relevant to my pet peeve.</p>
  1193. <p>I seem to recall people predicting this was coming even back in the 90s (maybe even before then) when we really started just pumping out MBAs and taking a Gordon Gecko mentality to absolutely every aspect of business.</p>
  1194. <p>It's also possible that those who have been around long enough were simply spoiled by a situation that couldn't continue to exist. When the Internet was young the people and companies using it and making software for it were doing it mostly because they loved it and it directly benefited them to help build it.</p>
  1195. <p>Now many of those successful companies have become incumbents or absorbed into the corporate machine and the entire situation has flipped.</p>
  1196. <p>To a degree, Google and Apple no longer have to care if the users like what they do. What are you gonna do, not use it? Same thing with Microsoft and what they keep doing to Windows. Nobody likes it, everyone hates it, the user hostility has gotten to the point of almost being blatant. But what are you gonna do, not use that Windows software that there is no replacement for?</p>
  1197. <p>It's not even about not fixing bugs. Now they are actively introducing hostile features like the strict enforcement of Microsoft accounts in Windows 11, patching out workarounds. It's almost laughable to think that they would fix bugs, their priorities are absolutely at the other end of the spectrum, far more focused on controlling what the users do in order to continue to funnel them into sales.</p>
  1198. ]]></content:encoded>
  1199. </item>
  1200. <item>
  1201. <title>
  1202. Comment on Unable to Send Messages With Apple Mail on macOS 15.4 by Old Coot </title>
  1203. <link>https://mjtsai.com/blog/2025/04/09/unable-to-send-messages-with-apple-mail-on-macos-15-4/#comment-4247525</link>
  1204.  
  1205. <dc:creator><![CDATA[Old Coot]]></dc:creator>
  1206. <pubDate>Wed, 09 Apr 2025 20:56:24 +0000</pubDate>
  1207. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47365#comment-4247525</guid>
  1208.  
  1209. <description><![CDATA[I might consider re-installing the latest Sequoia update.]]></description>
  1210. <content:encoded><![CDATA[<p>I might consider re-installing the latest Sequoia update.</p>
  1211. ]]></content:encoded>
  1212. </item>
  1213. <item>
  1214. <title>
  1215. Comment on Why Companies Don&#8217;t Fix Bugs by Dmitri Zdorov </title>
  1216. <link>https://mjtsai.com/blog/2025/04/09/why-companies-dont-fix-bugs/#comment-4247522</link>
  1217.  
  1218. <dc:creator><![CDATA[Dmitri Zdorov]]></dc:creator>
  1219. <pubDate>Wed, 09 Apr 2025 20:42:53 +0000</pubDate>
  1220. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47362#comment-4247522</guid>
  1221.  
  1222. <description><![CDATA[It’s not just about bugs. It’s about caring for small things that seemingly don’t directly impact the bottom line. From a corporate strategy point of view, there’s not much difference between not fixing a bug in the Music app, deciding the iPhone mini shouldn’t be manufactured because only a few million people are buying it (vs. tens of millions), or not updating QuickTime to support modern video formats.]]></description>
  1223. <content:encoded><![CDATA[<p>It’s not just about bugs. It’s about caring for small things that seemingly don’t directly impact the bottom line. From a corporate strategy point of view, there’s not much difference between not fixing a bug in the Music app, deciding the iPhone mini shouldn’t be manufactured because only a few million people are buying it (vs. tens of millions), or not updating QuickTime to support modern video formats.</p>
  1224. ]]></content:encoded>
  1225. </item>
  1226. <item>
  1227. <title>
  1228. Comment on Numbers 14.4 by Dave </title>
  1229. <link>https://mjtsai.com/blog/2025/04/07/numbers-14-4/#comment-4247497</link>
  1230.  
  1231. <dc:creator><![CDATA[Dave]]></dc:creator>
  1232. <pubDate>Wed, 09 Apr 2025 18:45:30 +0000</pubDate>
  1233. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47332#comment-4247497</guid>
  1234.  
  1235. <description><![CDATA[@Daniel,
  1236.  
  1237. This was just posted today:
  1238.  
  1239. https://sixcolors.com/post/2025/04/a-full-list-of-new-functions-in-numbers-14-4/
  1240.  
  1241. It lists the 34 new functions. Hope this helps!]]></description>
  1242. <content:encoded><![CDATA[<p>@Daniel,</p>
  1243. <p>This was just posted today:</p>
  1244. <p><a href="https://sixcolors.com/post/2025/04/a-full-list-of-new-functions-in-numbers-14-4/" rel="nofollow ugc">https://sixcolors.com/post/2025/04/a-full-list-of-new-functions-in-numbers-14-4/</a></p>
  1245. <p>It lists the 34 new functions. Hope this helps!</p>
  1246. ]]></content:encoded>
  1247. </item>
  1248. <item>
  1249. <title>
  1250. Comment on Abysmal Services by Plume </title>
  1251. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247455</link>
  1252.  
  1253. <dc:creator><![CDATA[Plume]]></dc:creator>
  1254. <pubDate>Wed, 09 Apr 2025 16:08:57 +0000</pubDate>
  1255. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247455</guid>
  1256.  
  1257. <description><![CDATA[Yeah, that doesn&#039;t exist in my 1Password, version 8.10.70.]]></description>
  1258. <content:encoded><![CDATA[<p>Yeah, that doesn't exist in my 1Password, version 8.10.70.</p>
  1259. ]]></content:encoded>
  1260. </item>
  1261. <item>
  1262. <title>
  1263. Comment on Abysmal Services by Michael Tsai </title>
  1264. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247449</link>
  1265.  
  1266. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  1267. <pubDate>Wed, 09 Apr 2025 15:56:44 +0000</pubDate>
  1268. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247449</guid>
  1269.  
  1270. <description><![CDATA[@Plume There used to be a whole Backups tab in the Preferences window. It would back up at least once a day and you could easily pick one to restore from. From what I’m reading, it looks like now it only does automatic backups in the cloud account.]]></description>
  1271. <content:encoded><![CDATA[<p>@Plume There used to be a whole Backups tab in the Preferences window. It would back up at least once a day and you could easily pick one to restore from. From what I’m reading, it looks like now it only does automatic backups in the cloud account.</p>
  1272. ]]></content:encoded>
  1273. </item>
  1274. <item>
  1275. <title>
  1276. Comment on Abysmal Services by Plume </title>
  1277. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247445</link>
  1278.  
  1279. <dc:creator><![CDATA[Plume]]></dc:creator>
  1280. <pubDate>Wed, 09 Apr 2025 15:41:07 +0000</pubDate>
  1281. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247445</guid>
  1282.  
  1283. <description><![CDATA[&#062;1Password got rid of the built-in automatic local backup feature
  1284.  
  1285. I don&#039;t know. I opened it on my Mac and looked through the settings and menus, but I could not find an automatic backup feature. There&#039;s a one-time export feature; that&#039;s all I found.]]></description>
  1286. <content:encoded><![CDATA[<p>&gt;1Password got rid of the built-in automatic local backup feature</p>
  1287. <p>I don't know. I opened it on my Mac and looked through the settings and menus, but I could not find an automatic backup feature. There's a one-time export feature; that's all I found.</p>
  1288. ]]></content:encoded>
  1289. </item>
  1290. <item>
  1291. <title>
  1292. Comment on Abysmal Services by Bri </title>
  1293. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247442</link>
  1294.  
  1295. <dc:creator><![CDATA[Bri]]></dc:creator>
  1296. <pubDate>Wed, 09 Apr 2025 15:38:59 +0000</pubDate>
  1297. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247442</guid>
  1298.  
  1299. <description><![CDATA[@gildarts This is why I use a cloud backup provider, Backblaze specifically. So I have my local backups using Time Machine along with my cloud backup. I&#039;d never rely on just one backup provider to work, and have had many instances where one failed and so I needed the other. And that&#039;s all on top of what&#039;s being synced between my devices.
  1300.  
  1301. I&#039;m still using 1Password 7 and am going to stick with it as long as I possibly can, since I still haven&#039;t found anything I actually like more. (Though I never tried Strongbox.) And that means I can back up my password vault using Time Machine and Backblaze, so that&#039;s fairly secure too.]]></description>
  1302. <content:encoded><![CDATA[<p>@gildarts This is why I use a cloud backup provider, Backblaze specifically. So I have my local backups using Time Machine along with my cloud backup. I'd never rely on just one backup provider to work, and have had many instances where one failed and so I needed the other. And that's all on top of what's being synced between my devices.</p>
  1303. <p>I'm still using 1Password 7 and am going to stick with it as long as I possibly can, since I still haven't found anything I actually like more. (Though I never tried Strongbox.) And that means I can back up my password vault using Time Machine and Backblaze, so that's fairly secure too.</p>
  1304. ]]></content:encoded>
  1305. </item>
  1306. <item>
  1307. <title>
  1308. Comment on Abysmal Services by Michael Tsai </title>
  1309. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247437</link>
  1310.  
  1311. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  1312. <pubDate>Wed, 09 Apr 2025 15:11:24 +0000</pubDate>
  1313. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247437</guid>
  1314.  
  1315. <description><![CDATA[@Plume 1Password got rid of the built-in automatic local backup feature?]]></description>
  1316. <content:encoded><![CDATA[<p>@Plume 1Password got rid of the built-in automatic local backup feature?</p>
  1317. ]]></content:encoded>
  1318. </item>
  1319. <item>
  1320. <title>
  1321. Comment on Abysmal Services by Glaurung </title>
  1322. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247431</link>
  1323.  
  1324. <dc:creator><![CDATA[Glaurung]]></dc:creator>
  1325. <pubDate>Wed, 09 Apr 2025 15:08:12 +0000</pubDate>
  1326. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247431</guid>
  1327.  
  1328. <description><![CDATA[@gildarts:
  1329.  
  1330. If disaster strikes and your house is gone, then it&#039;s entirely possible your phone will be gone as well.  There are some passwords that you simply have to commit to memory - the one for the email address you use to register on your banking/insurance/etc websites, the one for your apple (for ios) or google (for android) account is another. And for some things, (the data on your phone, for instance) using cloud backup (as a final line of defence) is essential as well.  
  1331.  
  1332. In a worst case situation, you need to be able to get a new phone up and running with your old number, get access to your email account, and only then will you be able to regain access to all the online accounts which have random passwords that were backed up on devices that are now gone.]]></description>
  1333. <content:encoded><![CDATA[<p>@gildarts:</p>
  1334. <p>If disaster strikes and your house is gone, then it's entirely possible your phone will be gone as well.  There are some passwords that you simply have to commit to memory - the one for the email address you use to register on your banking/insurance/etc websites, the one for your apple (for ios) or google (for android) account is another. And for some things, (the data on your phone, for instance) using cloud backup (as a final line of defence) is essential as well.  </p>
  1335. <p>In a worst case situation, you need to be able to get a new phone up and running with your old number, get access to your email account, and only then will you be able to regain access to all the online accounts which have random passwords that were backed up on devices that are now gone.</p>
  1336. ]]></content:encoded>
  1337. </item>
  1338. <item>
  1339. <title>
  1340. Comment on Abysmal Services by Plume </title>
  1341. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247424</link>
  1342.  
  1343. <dc:creator><![CDATA[Plume]]></dc:creator>
  1344. <pubDate>Wed, 09 Apr 2025 14:47:42 +0000</pubDate>
  1345. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247424</guid>
  1346.  
  1347. <description><![CDATA[&quot;Not to mention the low level constant dread about losing everything if you bork something&quot;
  1348.  
  1349. You can also lose things when they&#039;re hosted by somebody else in their cloud. So, either way, you need to have a backup strategy. IMO, it&#039;s way easier to back up your own Vaultwarden data than to back up something like 1Password (which, as far as I know, has no automatic backup functionality built-in).
  1350.  
  1351. I&#039;ve never felt safer about my data. I back up all the data from one NAS to another on-site NAS and all of my important data to a Filen account. At some point, I&#039;ll probably drop off another NAS at a family member&#039;s and sync things to that, too. With Tailscale, this kind of thing has become borderline trivial.
  1352.  
  1353. Self-hosting has become much easier than in the past, and the services available—things like Immich, hoarder, or Vaultwarden—have become much better, to the point where they are better than many services provided by A-tier cloud providers.
  1354.  
  1355. Obviously, I still wouldn&#039;t tell any random person to stop using Google Drive and self-host their data, but anyone reading this blog can do this in half a weekend.]]></description>
  1356. <content:encoded><![CDATA[<p>"Not to mention the low level constant dread about losing everything if you bork something"</p>
  1357. <p>You can also lose things when they're hosted by somebody else in their cloud. So, either way, you need to have a backup strategy. IMO, it's way easier to back up your own Vaultwarden data than to back up something like 1Password (which, as far as I know, has no automatic backup functionality built-in).</p>
  1358. <p>I've never felt safer about my data. I back up all the data from one NAS to another on-site NAS and all of my important data to a Filen account. At some point, I'll probably drop off another NAS at a family member's and sync things to that, too. With Tailscale, this kind of thing has become borderline trivial.</p>
  1359. <p>Self-hosting has become much easier than in the past, and the services available—things like Immich, hoarder, or Vaultwarden—have become much better, to the point where they are better than many services provided by A-tier cloud providers.</p>
  1360. <p>Obviously, I still wouldn't tell any random person to stop using Google Drive and self-host their data, but anyone reading this blog can do this in half a weekend.</p>
  1361. ]]></content:encoded>
  1362. </item>
  1363. <item>
  1364. <title>
  1365. Comment on Abysmal Services by gildarts </title>
  1366. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247398</link>
  1367.  
  1368. <dc:creator><![CDATA[gildarts]]></dc:creator>
  1369. <pubDate>Wed, 09 Apr 2025 12:50:07 +0000</pubDate>
  1370. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247398</guid>
  1371.  
  1372. <description><![CDATA[@Bri: Not to mention the low level constant dread about losing everything if you bork something or your house burns down. Admittedly, losing synced files is kind of the least of your problems if your house burns down, but it has kept me from self-hosting Bitwarden, etc. I can&#039;t afford to lose my house AND my ability to access every account I have, insurance for example.]]></description>
  1373. <content:encoded><![CDATA[<p>@Bri: Not to mention the low level constant dread about losing everything if you bork something or your house burns down. Admittedly, losing synced files is kind of the least of your problems if your house burns down, but it has kept me from self-hosting Bitwarden, etc. I can't afford to lose my house AND my ability to access every account I have, insurance for example.</p>
  1374. ]]></content:encoded>
  1375. </item>
  1376. <item>
  1377. <title>
  1378. Comment on Locked Out of Apple Developer Accounts by Bri </title>
  1379. <link>https://mjtsai.com/blog/2025/04/08/locked-out-of-apple-developer-accounts/#comment-4247393</link>
  1380.  
  1381. <dc:creator><![CDATA[Bri]]></dc:creator>
  1382. <pubDate>Wed, 09 Apr 2025 12:38:46 +0000</pubDate>
  1383. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47350#comment-4247393</guid>
  1384.  
  1385. <description><![CDATA[For reasons like this I&#039;m avoiding being reliant on any major tech company for earning a living, especially Apple given that they are actively hostile towards their own third party developers. I do make some free mac apps, but I don&#039;t strictly *need* to notarize them. In fact, I hate notarizing them, because I feel like a chump every time I do it.]]></description>
  1386. <content:encoded><![CDATA[<p>For reasons like this I'm avoiding being reliant on any major tech company for earning a living, especially Apple given that they are actively hostile towards their own third party developers. I do make some free mac apps, but I don't strictly *need* to notarize them. In fact, I hate notarizing them, because I feel like a chump every time I do it.</p>
  1387. ]]></content:encoded>
  1388. </item>
  1389. <item>
  1390. <title>
  1391. Comment on Abysmal Services by Bri </title>
  1392. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247389</link>
  1393.  
  1394. <dc:creator><![CDATA[Bri]]></dc:creator>
  1395. <pubDate>Wed, 09 Apr 2025 12:24:45 +0000</pubDate>
  1396. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247389</guid>
  1397.  
  1398. <description><![CDATA[I&#039;ve stopped using iCloud, except for syncing contacts, and that does occasionally just fail to work.
  1399.  
  1400. The only real syncing service I&#039;m using at this point is Nextcloud, self hosted by me, which isn&#039;t great, but it at least does its one main job well enough. But it&#039;s not like I can recommend self hosting to just anyone.]]></description>
  1401. <content:encoded><![CDATA[<p>I've stopped using iCloud, except for syncing contacts, and that does occasionally just fail to work.</p>
  1402. <p>The only real syncing service I'm using at this point is Nextcloud, self hosted by me, which isn't great, but it at least does its one main job well enough. But it's not like I can recommend self hosting to just anyone.</p>
  1403. ]]></content:encoded>
  1404. </item>
  1405. <item>
  1406. <title>
  1407. Comment on Abysmal Services by Kristoffer </title>
  1408. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247317</link>
  1409.  
  1410. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  1411. <pubDate>Wed, 09 Apr 2025 07:59:59 +0000</pubDate>
  1412. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247317</guid>
  1413.  
  1414. <description><![CDATA[@Plume +1
  1415.  
  1416. Google Photos is the poster child of this.
  1417.  
  1418. I was soooo delighted when that launched, and I&#039;m still a big fan. But free became payed became full of duplicate copies because my wife wants access to all photos and maybe I don&#039;t understand how to do that properly but right now I share all vacation picuters and that menas we pay twice for each in the family plan and it&#039;s just ....
  1419.  
  1420. On the other hand. Back when I had a NAS in the cupboard that was a right nightmare to.]]></description>
  1421. <content:encoded><![CDATA[<p>@Plume +1</p>
  1422. <p>Google Photos is the poster child of this.</p>
  1423. <p>I was soooo delighted when that launched, and I'm still a big fan. But free became payed became full of duplicate copies because my wife wants access to all photos and maybe I don't understand how to do that properly but right now I share all vacation picuters and that menas we pay twice for each in the family plan and it's just .... </p>
  1424. <p>On the other hand. Back when I had a NAS in the cupboard that was a right nightmare to.</p>
  1425. ]]></content:encoded>
  1426. </item>
  1427. <item>
  1428. <title>
  1429. Comment on Abysmal Services by Plume </title>
  1430. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247309</link>
  1431.  
  1432. <dc:creator><![CDATA[Plume]]></dc:creator>
  1433. <pubDate>Wed, 09 Apr 2025 07:39:51 +0000</pubDate>
  1434. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247309</guid>
  1435.  
  1436. <description><![CDATA[The main problem, as with the &quot;Locked Out of Apple Developer Accounts&quot; sibling post, is that there is nothing you can do about this. These companies are moving all of their customers to their cloud services, locking them in, and then slowly degrading these services, and there is no recourse. You hope that things magically resolve themselves, and they probably usually do, but sometimes they don&#039;t, and then you&#039;re just screwed.
  1437.  
  1438. You can&#039;t call or email anyone who has any power to do anything for you.
  1439.  
  1440. This is why I&#039;m moving as much as possible to self-hosting. Things can still go wrong, but at least now I can do something about it.]]></description>
  1441. <content:encoded><![CDATA[<p>The main problem, as with the "Locked Out of Apple Developer Accounts" sibling post, is that there is nothing you can do about this. These companies are moving all of their customers to their cloud services, locking them in, and then slowly degrading these services, and there is no recourse. You hope that things magically resolve themselves, and they probably usually do, but sometimes they don't, and then you're just screwed.</p>
  1442. <p>You can't call or email anyone who has any power to do anything for you.</p>
  1443. <p>This is why I'm moving as much as possible to self-hosting. Things can still go wrong, but at least now I can do something about it.</p>
  1444. ]]></content:encoded>
  1445. </item>
  1446. <item>
  1447. <title>
  1448. Comment on The Signal Chat Leak and the NSA by Plume </title>
  1449. <link>https://mjtsai.com/blog/2025/04/07/the-signal-chat-leak-and-the-nsa/#comment-4247307</link>
  1450.  
  1451. <dc:creator><![CDATA[Plume]]></dc:creator>
  1452. <pubDate>Wed, 09 Apr 2025 07:33:48 +0000</pubDate>
  1453. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47329#comment-4247307</guid>
  1454.  
  1455. <description><![CDATA[&#062;It looks like this
  1456.  
  1457. That&#039;s wild. If Apple makes this association based on a phone number merely just appearing in an email, then I absolutely believe this is what happened. The fact that this prompt doesn&#039;t even give any context for where the number was found is atrocious design.
  1458.  
  1459.  
  1460. &#062;no one in government wants to use the official secure communication channels
  1461.  
  1462. This actually pisses me off. I work for a company that has government contracts, and we have some security restrictions, and I just do that shit even if it&#039;s annoying and makes my work harder.
  1463.  
  1464. These people are literally making decisions that affect the whole world, and they can&#039;t be bothered to follow the most basic security protocols.]]></description>
  1465. <content:encoded><![CDATA[<p>&gt;It looks like this</p>
  1466. <p>That's wild. If Apple makes this association based on a phone number merely just appearing in an email, then I absolutely believe this is what happened. The fact that this prompt doesn't even give any context for where the number was found is atrocious design.</p>
  1467. <p>&gt;no one in government wants to use the official secure communication channels</p>
  1468. <p>This actually pisses me off. I work for a company that has government contracts, and we have some security restrictions, and I just do that shit even if it's annoying and makes my work harder.</p>
  1469. <p>These people are literally making decisions that affect the whole world, and they can't be bothered to follow the most basic security protocols.</p>
  1470. ]]></content:encoded>
  1471. </item>
  1472. <item>
  1473. <title>
  1474. Comment on iOS 18.4: Ambient Music by Nathan </title>
  1475. <link>https://mjtsai.com/blog/2025/04/07/ios-18-4-ambient-music/#comment-4247234</link>
  1476.  
  1477. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1478. <pubDate>Wed, 09 Apr 2025 03:25:19 +0000</pubDate>
  1479. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47334#comment-4247234</guid>
  1480.  
  1481. <description><![CDATA[I noticed this in the release notes and set it up on both my phone and iPad. The music’s nice.
  1482.  
  1483. However, when I went to turn one of them on after reading this post last night, it just failed to start. I have no idea why.]]></description>
  1484. <content:encoded><![CDATA[<p>I noticed this in the release notes and set it up on both my phone and iPad. The music’s nice.</p>
  1485. <p>However, when I went to turn one of them on after reading this post last night, it just failed to start. I have no idea why.</p>
  1486. ]]></content:encoded>
  1487. </item>
  1488. <item>
  1489. <title>
  1490. Comment on Abysmal Services by Mac Folklore Radio </title>
  1491. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247200</link>
  1492.  
  1493. <dc:creator><![CDATA[Mac Folklore Radio]]></dc:creator>
  1494. <pubDate>Wed, 09 Apr 2025 00:19:22 +0000</pubDate>
  1495. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247200</guid>
  1496.  
  1497. <description><![CDATA[Don&#039;t worry, I&#039;m sure another re-branding will solve everything. (Younger folks: see iTools, .Mac, and MobileMe. I had no reason to believe they&#039;d get it right the fourth time around.)
  1498.  
  1499. Watch the problem-ridden iTools demo at Macworld San Francisco 2000. Nothing has changed. I use iMessage and nothing else. The hardware is great. Everything else is a disaster and nobody at Apple seems to notice or care.
  1500.  
  1501. Plug: a third-party IMAP/CalDAV/CardDAV service is well worth the money.]]></description>
  1502. <content:encoded><![CDATA[<p>Don't worry, I'm sure another re-branding will solve everything. (Younger folks: see iTools, .Mac, and MobileMe. I had no reason to believe they'd get it right the fourth time around.)</p>
  1503. <p>Watch the problem-ridden iTools demo at Macworld San Francisco 2000. Nothing has changed. I use iMessage and nothing else. The hardware is great. Everything else is a disaster and nobody at Apple seems to notice or care.</p>
  1504. <p>Plug: a third-party IMAP/CalDAV/CardDAV service is well worth the money.</p>
  1505. ]]></content:encoded>
  1506. </item>
  1507. <item>
  1508. <title>
  1509. Comment on Abysmal Services by Jason </title>
  1510. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247185</link>
  1511.  
  1512. <dc:creator><![CDATA[Jason]]></dc:creator>
  1513. <pubDate>Tue, 08 Apr 2025 22:45:33 +0000</pubDate>
  1514. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247185</guid>
  1515.  
  1516. <description><![CDATA[He didn&#039;t even mention the ridiculous PITA that is Shortcuts sync conflicts.]]></description>
  1517. <content:encoded><![CDATA[<p>He didn't even mention the ridiculous PITA that is Shortcuts sync conflicts.</p>
  1518. ]]></content:encoded>
  1519. </item>
  1520. <item>
  1521. <title>
  1522. Comment on Abysmal Services by Matt B </title>
  1523. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247179</link>
  1524.  
  1525. <dc:creator><![CDATA[Matt B]]></dc:creator>
  1526. <pubDate>Tue, 08 Apr 2025 22:17:15 +0000</pubDate>
  1527. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247179</guid>
  1528.  
  1529. <description><![CDATA[The problem is that they all &quot;mostly work&quot; but not fully work. Like you, I&#039;ve had issues with iMessage syncing. Sometimes it works and sometimes it doesn&#039;t. And one of my computers displays &quot;29 unread messages&quot; but when selecting &quot;unread&quot; nothing shows. With no way to know the current state of syncing and no way to push &quot;sync now&quot; I just have to deal with the frustration.
  1530.  
  1531. It&#039;s the death by a thousand cuts. Apple doesn&#039;t care any more.]]></description>
  1532. <content:encoded><![CDATA[<p>The problem is that they all "mostly work" but not fully work. Like you, I've had issues with iMessage syncing. Sometimes it works and sometimes it doesn't. And one of my computers displays "29 unread messages" but when selecting "unread" nothing shows. With no way to know the current state of syncing and no way to push "sync now" I just have to deal with the frustration. </p>
  1533. <p>It's the death by a thousand cuts. Apple doesn't care any more.</p>
  1534. ]]></content:encoded>
  1535. </item>
  1536. <item>
  1537. <title>
  1538. Comment on Abysmal Services by Anonymous </title>
  1539. <link>https://mjtsai.com/blog/2025/04/08/abysmal-services/#comment-4247177</link>
  1540.  
  1541. <dc:creator><![CDATA[Anonymous]]></dc:creator>
  1542. <pubDate>Tue, 08 Apr 2025 22:11:32 +0000</pubDate>
  1543. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47348#comment-4247177</guid>
  1544.  
  1545. <description><![CDATA[“It ended up overheating my phone battery to the point it could no longer hold a charge.”
  1546.  
  1547. Okay buddy, sure. It doesn’t even matter which service this is about, that’s just silly.]]></description>
  1548. <content:encoded><![CDATA[<p>“It ended up overheating my phone battery to the point it could no longer hold a charge.”</p>
  1549. <p>Okay buddy, sure. It doesn’t even matter which service this is about, that’s just silly.</p>
  1550. ]]></content:encoded>
  1551. </item>
  1552. <item>
  1553. <title>
  1554. Comment on Locked Out of Apple Developer Accounts by MeX </title>
  1555. <link>https://mjtsai.com/blog/2025/04/08/locked-out-of-apple-developer-accounts/#comment-4247167</link>
  1556.  
  1557. <dc:creator><![CDATA[MeX]]></dc:creator>
  1558. <pubDate>Tue, 08 Apr 2025 21:17:03 +0000</pubDate>
  1559. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47350#comment-4247167</guid>
  1560.  
  1561. <description><![CDATA[The same here (I could not login) and after months requesting including phone calls I could login my account. Really frustrating.]]></description>
  1562. <content:encoded><![CDATA[<p>The same here (I could not login) and after months requesting including phone calls I could login my account. Really frustrating.</p>
  1563. ]]></content:encoded>
  1564. </item>
  1565. <item>
  1566. <title>
  1567. Comment on The Signal Chat Leak and the NSA by NaOH </title>
  1568. <link>https://mjtsai.com/blog/2025/04/07/the-signal-chat-leak-and-the-nsa/#comment-4247159</link>
  1569.  
  1570. <dc:creator><![CDATA[NaOH]]></dc:creator>
  1571. <pubDate>Tue, 08 Apr 2025 20:54:48 +0000</pubDate>
  1572. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47329#comment-4247159</guid>
  1573.  
  1574. <description><![CDATA[I’ve got a little over 500 contact cards. On the Mac, back on 10.14 Mojave (and earlier; I can’t speak to later macOS versions), Siri/data detectors will display information that’s been found in other apps in an existing contact card. I found an instance of this, essentially like this:
  1575.  
  1576. TimCook@gmail.com (added by me)
  1577.  
  1578. tim.cook@gmail.com (noticed by Siri in an email)
  1579.  
  1580. I prefer the capitalization, and I remove periods from Gmail usernames since they have no effect. The two addresses as shown would get to the same person.
  1581.  
  1582. But the Siri-added info isn’t really in the contact card. For one, it’s not shown in Contacts on my up-to-date iPhone (13 mini, so no AI). On top of that, in Mac Contacts, off to the right of the Siri/data detectors suggestion, is a lowercase i in a circle, akin to an Information icon/emoji. Clicking that, the data source is shown and buttons are there to add the information to the contact or to ignore it. Again, this is only on the Mac, not on an up-to-date iPhone.
  1583.  
  1584. For as tight-lipped as Apple can be, for as obstinate as Apple can be about product mistakes/shortcomings, I’m more confident it’s not their work that was the problem rather than a mistake by a politician within a group of people who never admit any wrongdoing.]]></description>
  1585. <content:encoded><![CDATA[<p>I’ve got a little over 500 contact cards. On the Mac, back on 10.14 Mojave (and earlier; I can’t speak to later macOS versions), Siri/data detectors will display information that’s been found in other apps in an existing contact card. I found an instance of this, essentially like this:</p>
  1586. <p><a href="mailto:TimCook@gmail.com">TimCook@gmail.com</a> (added by me)</p>
  1587. <p><a href="mailto:tim.cook@gmail.com">tim.cook@gmail.com</a> (noticed by Siri in an email)</p>
  1588. <p>I prefer the capitalization, and I remove periods from Gmail usernames since they have no effect. The two addresses as shown would get to the same person.</p>
  1589. <p>But the Siri-added info isn’t really in the contact card. For one, it’s not shown in Contacts on my up-to-date iPhone (13 mini, so no AI). On top of that, in Mac Contacts, off to the right of the Siri/data detectors suggestion, is a lowercase i in a circle, akin to an Information icon/emoji. Clicking that, the data source is shown and buttons are there to add the information to the contact or to ignore it. Again, this is only on the Mac, not on an up-to-date iPhone.</p>
  1590. <p>For as tight-lipped as Apple can be, for as obstinate as Apple can be about product mistakes/shortcomings, I’m more confident it’s not their work that was the problem rather than a mistake by a politician within a group of people who never admit any wrongdoing.</p>
  1591. ]]></content:encoded>
  1592. </item>
  1593. <item>
  1594. <title>
  1595. Comment on The Signal Chat Leak and the NSA by gildarts </title>
  1596. <link>https://mjtsai.com/blog/2025/04/07/the-signal-chat-leak-and-the-nsa/#comment-4247144</link>
  1597.  
  1598. <dc:creator><![CDATA[gildarts]]></dc:creator>
  1599. <pubDate>Tue, 08 Apr 2025 19:39:29 +0000</pubDate>
  1600. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47329#comment-4247144</guid>
  1601.  
  1602. <description><![CDATA[&#062; If this actually happens, this is clearly the most plausible explanation, but does it happen?
  1603.  
  1604. Absolutely does happen. It doesn&#039;t just add it without some level of user interaction, but it does suggest it and if you weren&#039;t paying attention it would be an easy mistake to make.
  1605.  
  1606. &#062; These people just don&#039;t want to use them.
  1607.  
  1608. The evidence I&#039;ve seen from the last 1.5-2 decades is that no one in government wants to use the official secure communication channels. See Hillary Clinton and her email server. Having never used any of the official government tools, I don&#039;t know how insufferable they are to use, but having used other IT from various government organizations, I&#039;d guess pretty terrible. And there is zero incentive to improve it because that would cost money and everyone /has/ to use it anyway.
  1609.  
  1610. &#062; Hegseth detailed the operational timeline for the strikes and specified launch times for F-18 fighter jets and MQ-9 drones. He gave the timeline for when bombs would be dropped.
  1611.  
  1612. That is fair. I was uncertain on the timing of the details vs the attacks happening. If it was hours in advance, yeah, that is, at best, unwise. If it was more or less real time, I have less of a problem with it as after the attacks are happening, keeping such information secret is minimally important.]]></description>
  1613. <content:encoded><![CDATA[<p>&gt; If this actually happens, this is clearly the most plausible explanation, but does it happen?</p>
  1614. <p>Absolutely does happen. It doesn't just add it without some level of user interaction, but it does suggest it and if you weren't paying attention it would be an easy mistake to make.</p>
  1615. <p>&gt; These people just don't want to use them.</p>
  1616. <p>The evidence I've seen from the last 1.5-2 decades is that no one in government wants to use the official secure communication channels. See Hillary Clinton and her email server. Having never used any of the official government tools, I don't know how insufferable they are to use, but having used other IT from various government organizations, I'd guess pretty terrible. And there is zero incentive to improve it because that would cost money and everyone /has/ to use it anyway.</p>
  1617. <p>&gt; Hegseth detailed the operational timeline for the strikes and specified launch times for F-18 fighter jets and MQ-9 drones. He gave the timeline for when bombs would be dropped.</p>
  1618. <p>That is fair. I was uncertain on the timing of the details vs the attacks happening. If it was hours in advance, yeah, that is, at best, unwise. If it was more or less real time, I have less of a problem with it as after the attacks are happening, keeping such information secret is minimally important.</p>
  1619. ]]></content:encoded>
  1620. </item>
  1621. <item>
  1622. <title>
  1623. Comment on The Signal Chat Leak and the NSA by Michael Tsai </title>
  1624. <link>https://mjtsai.com/blog/2025/04/07/the-signal-chat-leak-and-the-nsa/#comment-4247125</link>
  1625.  
  1626. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  1627. <pubDate>Tue, 08 Apr 2025 18:33:32 +0000</pubDate>
  1628. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47329#comment-4247125</guid>
  1629.  
  1630. <description><![CDATA[@Plume It looks like &lt;a href=&quot;https://www.reddit.com/r/Scams/comments/1bk8hh5/this_person_added_themselves_to_my_iphone_contacts/&quot; rel=&quot;nofollow ugc&quot;&gt;this&lt;/a&gt; and has happened to me, though I think Siri was correct in my experience. I’ve also seen a bunch of cases when I wish it would have offered the option but didn’t. I don’t understand what the criteria are.]]></description>
  1631. <content:encoded><![CDATA[<p>@Plume It looks like <a href="https://www.reddit.com/r/Scams/comments/1bk8hh5/this_person_added_themselves_to_my_iphone_contacts/" rel="nofollow ugc">this</a> and has happened to me, though I think Siri was correct in my experience. I’ve also seen a bunch of cases when I wish it would have offered the option but didn’t. I don’t understand what the criteria are.</p>
  1632. ]]></content:encoded>
  1633. </item>
  1634. <item>
  1635. <title>
  1636. Comment on The Signal Chat Leak and the NSA by Dave </title>
  1637. <link>https://mjtsai.com/blog/2025/04/07/the-signal-chat-leak-and-the-nsa/#comment-4247123</link>
  1638.  
  1639. <dc:creator><![CDATA[Dave]]></dc:creator>
  1640. <pubDate>Tue, 08 Apr 2025 18:29:08 +0000</pubDate>
  1641. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47329#comment-4247123</guid>
  1642.  
  1643. <description><![CDATA[I agree. But still....why did Waltz need to call Goldberg &quot;a loser&quot;? It was a mistake on the part of Waltz. Has he apologized or been fired for *his* actions? (I&#039;d go for a simple - but public - reprimand. American soldier lives were put in danger because of this.)]]></description>
  1644. <content:encoded><![CDATA[<p>I agree. But still....why did Waltz need to call Goldberg "a loser"? It was a mistake on the part of Waltz. Has he apologized or been fired for *his* actions? (I'd go for a simple - but public - reprimand. American soldier lives were put in danger because of this.)</p>
  1645. ]]></content:encoded>
  1646. </item>
  1647. <item>
  1648. <title>
  1649. Comment on The Signal Chat Leak and the NSA by Plume </title>
  1650. <link>https://mjtsai.com/blog/2025/04/07/the-signal-chat-leak-and-the-nsa/#comment-4247120</link>
  1651.  
  1652. <dc:creator><![CDATA[Plume]]></dc:creator>
  1653. <pubDate>Tue, 08 Apr 2025 18:25:25 +0000</pubDate>
  1654. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47329#comment-4247120</guid>
  1655.  
  1656. <description><![CDATA[&#062;I, for one, totally believe the data detectors explanation
  1657.  
  1658. I don&#039;t understand what they&#039;re saying. I haven&#039;t used an iPhone in a few years. Still, when I did, it never exhibited the above behavior (&quot;an iPhone algorithm adds a previously unknown number to an existing contact that it detects may be related).&quot;
  1659.  
  1660. If this actually happens, this is clearly the most plausible explanation, but does it happen?
  1661.  
  1662.  
  1663. &#062;I&#039;m not sure why the Fed hasn&#039;t stood up their own Signal network
  1664.  
  1665. They have officially sanctioned secure messaging apps (e.g. they use Wickr). These people just don&#039;t want to use them.
  1666.  
  1667.  
  1668. &#062;I&#039;ve seen zero indication that Signal is less secure than the government networks
  1669.  
  1670. It is. Not because it&#039;s technically insecure but because it&#039;s controlled by a private company outside of government control. The threat model for these people is very different from ours.
  1671.  
  1672.  
  1673. &#062;I buy it for really sensitive stuff, I&#039;m not sure this qualifies
  1674.  
  1675. Hegseth detailed the operational timeline for the strikes and specified launch times for F-18 fighter jets and MQ-9 drones. He gave the timeline for when bombs would be dropped.]]></description>
  1676. <content:encoded><![CDATA[<p>&gt;I, for one, totally believe the data detectors explanation</p>
  1677. <p>I don't understand what they're saying. I haven't used an iPhone in a few years. Still, when I did, it never exhibited the above behavior ("an iPhone algorithm adds a previously unknown number to an existing contact that it detects may be related)."</p>
  1678. <p>If this actually happens, this is clearly the most plausible explanation, but does it happen?</p>
  1679. <p>&gt;I'm not sure why the Fed hasn't stood up their own Signal network</p>
  1680. <p>They have officially sanctioned secure messaging apps (e.g. they use Wickr). These people just don't want to use them.</p>
  1681. <p>&gt;I've seen zero indication that Signal is less secure than the government networks</p>
  1682. <p>It is. Not because it's technically insecure but because it's controlled by a private company outside of government control. The threat model for these people is very different from ours.</p>
  1683. <p>&gt;I buy it for really sensitive stuff, I'm not sure this qualifies</p>
  1684. <p>Hegseth detailed the operational timeline for the strikes and specified launch times for F-18 fighter jets and MQ-9 drones. He gave the timeline for when bombs would be dropped.</p>
  1685. ]]></content:encoded>
  1686. </item>
  1687. <item>
  1688. <title>
  1689. Comment on The Signal Chat Leak and the NSA by gildarts </title>
  1690. <link>https://mjtsai.com/blog/2025/04/07/the-signal-chat-leak-and-the-nsa/#comment-4247076</link>
  1691.  
  1692. <dc:creator><![CDATA[gildarts]]></dc:creator>
  1693. <pubDate>Tue, 08 Apr 2025 15:57:40 +0000</pubDate>
  1694. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47329#comment-4247076</guid>
  1695.  
  1696. <description><![CDATA[I, for one, totally believe the data detectors explanation. I&#039;ve had several near misses on adding the wrong contact information to someone&#039;s contact because of scenarios just like this. If you are paying attention, it shouldn&#039;t be a problem, but data detectors are pretty dumb and if some contact info is in an email from someone it will often suggest a info update, even if the data is unrelated to the person actually sending the data.
  1697.  
  1698. Honestly, I&#039;m not sure why the Fed hasn&#039;t stood up their own Signal network/app that doesn&#039;t use the phone address book, etc. The thing is freaking open source. I&#039;ve considered setting something like that up for better parental controls for family/friends and find it hard to believe that the government couldn&#039;t setup something like that. Either the encryption works or it doesn&#039;t. Outside of user error or the person&#039;s device being compromised, I&#039;ve seen zero indication that Signal is less secure than the government networks. You could argue that Signal is more secure because it doesn&#039;t retain messages in a manner that can be retrieved from archives. Of course not storing that runs into Federal records laws, but that is a different argument from the security of the conversation.
  1699.  
  1700. I know there is an argument that conversations like this should be taking place in specific secure facilities, and while I buy it for really sensitive stuff, I&#039;m not sure this qualifies. If they were talking about the mole they have standing behind Putin for instance, that shouldn&#039;t be talked about outside of the most secure devices.]]></description>
  1701. <content:encoded><![CDATA[<p>I, for one, totally believe the data detectors explanation. I've had several near misses on adding the wrong contact information to someone's contact because of scenarios just like this. If you are paying attention, it shouldn't be a problem, but data detectors are pretty dumb and if some contact info is in an email from someone it will often suggest a info update, even if the data is unrelated to the person actually sending the data.</p>
  1702. <p>Honestly, I'm not sure why the Fed hasn't stood up their own Signal network/app that doesn't use the phone address book, etc. The thing is freaking open source. I've considered setting something like that up for better parental controls for family/friends and find it hard to believe that the government couldn't setup something like that. Either the encryption works or it doesn't. Outside of user error or the person's device being compromised, I've seen zero indication that Signal is less secure than the government networks. You could argue that Signal is more secure because it doesn't retain messages in a manner that can be retrieved from archives. Of course not storing that runs into Federal records laws, but that is a different argument from the security of the conversation.</p>
  1703. <p>I know there is an argument that conversations like this should be taking place in specific secure facilities, and while I buy it for really sensitive stuff, I'm not sure this qualifies. If they were talking about the mole they have standing behind Putin for instance, that shouldn't be talked about outside of the most secure devices.</p>
  1704. ]]></content:encoded>
  1705. </item>
  1706. <item>
  1707. <title>
  1708. Comment on Numbers 14.4 by Daniel </title>
  1709. <link>https://mjtsai.com/blog/2025/04/07/numbers-14-4/#comment-4247059</link>
  1710.  
  1711. <dc:creator><![CDATA[Daniel]]></dc:creator>
  1712. <pubDate>Tue, 08 Apr 2025 14:53:42 +0000</pubDate>
  1713. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47332#comment-4247059</guid>
  1714.  
  1715. <description><![CDATA[As a very frequent user of Numbers, I&#039;m very happy with this update — array support is long overdue, and they enabled me to migrate my last spreadsheet from Excel. But wow, they really botched the release process. &quot;Over 30 functions&quot; with no listing of them anywhere? I couldn&#039;t even find the new functions in the linked documentation, because for some reason it switches back to the previous release.
  1716.  
  1717. Even with this, though, Numbers still lags far behind Excel for Mac, which in turn seems to be significantly behind Excel for Windows. Not being able to use functions defined in other cells is particularly bad. This update&#039;s `LET()` may make doing complex calculations ten times better than it was last week, but even now it&#039;s still a hundred times worse than in Excel for Windows.]]></description>
  1718. <content:encoded><![CDATA[<p>As a very frequent user of Numbers, I'm very happy with this update — array support is long overdue, and they enabled me to migrate my last spreadsheet from Excel. But wow, they really botched the release process. "Over 30 functions" with no listing of them anywhere? I couldn't even find the new functions in the linked documentation, because for some reason it switches back to the previous release.</p>
  1719. <p>Even with this, though, Numbers still lags far behind Excel for Mac, which in turn seems to be significantly behind Excel for Windows. Not being able to use functions defined in other cells is particularly bad. This update's `LET()` may make doing complex calculations ten times better than it was last week, but even now it's still a hundred times worse than in Excel for Windows.</p>
  1720. ]]></content:encoded>
  1721. </item>
  1722. <item>
  1723. <title>
  1724. Comment on Numbers 14.4 by cowmonkey </title>
  1725. <link>https://mjtsai.com/blog/2025/04/07/numbers-14-4/#comment-4246955</link>
  1726.  
  1727. <dc:creator><![CDATA[cowmonkey]]></dc:creator>
  1728. <pubDate>Tue, 08 Apr 2025 07:02:06 +0000</pubDate>
  1729. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47332#comment-4246955</guid>
  1730.  
  1731. <description><![CDATA[@gildarts: you are correct, I am a heavey user of spreadsheets (professionally, of course ;)) and unfortunately there is no alternative to Excel - Not Google Sheets, Not Libre Calc and sure AF not Numbers.
  1732.  
  1733. The main problem with the Pages, Numbers and Keynotes app is that while they all look nice and polished, they continually get in the way of the user - How far we&#039;ve strayed from Claris Works and FileMaker Pro]]></description>
  1734. <content:encoded><![CDATA[<p>@gildarts: you are correct, I am a heavey user of spreadsheets (professionally, of course ;)) and unfortunately there is no alternative to Excel - Not Google Sheets, Not Libre Calc and sure AF not Numbers. </p>
  1735. <p>The main problem with the Pages, Numbers and Keynotes app is that while they all look nice and polished, they continually get in the way of the user - How far we've strayed from Claris Works and FileMaker Pro</p>
  1736. ]]></content:encoded>
  1737. </item>
  1738. <item>
  1739. <title>
  1740. Comment on XcodeBenchmark by ihatexcode </title>
  1741. <link>https://mjtsai.com/blog/2025/02/25/xcodebenchmark/#comment-4246911</link>
  1742.  
  1743. <dc:creator><![CDATA[ihatexcode]]></dc:creator>
  1744. <pubDate>Tue, 08 Apr 2025 03:57:35 +0000</pubDate>
  1745. <guid isPermaLink="false">https://mjtsai.com/blog/?p=46847#comment-4246911</guid>
  1746.  
  1747. <description><![CDATA[Practically speaking, is there a benefit for xcode development picking a mac mini with more than 16gb ram (options include 24/32gb)? I&#039;m not particularly concerned with the downsides of using swap if it&#039;s enough for getting work done well. Only reason I ask is because of the ram pricing scheme.]]></description>
  1748. <content:encoded><![CDATA[<p>Practically speaking, is there a benefit for xcode development picking a mac mini with more than 16gb ram (options include 24/32gb)? I'm not particularly concerned with the downsides of using swap if it's enough for getting work done well. Only reason I ask is because of the ram pricing scheme.</p>
  1749. ]]></content:encoded>
  1750. </item>
  1751. <item>
  1752. <title>
  1753. Comment on Numbers 14.4 by Dave </title>
  1754. <link>https://mjtsai.com/blog/2025/04/07/numbers-14-4/#comment-4246883</link>
  1755.  
  1756. <dc:creator><![CDATA[Dave]]></dc:creator>
  1757. <pubDate>Tue, 08 Apr 2025 01:12:06 +0000</pubDate>
  1758. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47332#comment-4246883</guid>
  1759.  
  1760. <description><![CDATA[@Michael_Tsai, a direct quote from your post:
  1761.  
  1762. &quot;Apple today updated its iWork apps Keynote, Numbers, and Pages with new features that require iOS 18.4, iPadOS 18.4, or macOS 15.4&quot;
  1763.  
  1764. No explanation, and none needed. Except.... over 30 new functions? I guess some require Apple Intelligence in some sort of way? The way you quoted make it sounds like 14.4 *requires* macOS 15.4. It simply does not.
  1765.  
  1766. I have come to rely o your blog for both a place I can rely on for news (even if secondhand, you are awesome about attribution) and accuracy. My point with my comment maybe should have been directed elsewhere, but based on your post I thought it best to say macOS 14.X can still download - without certain AI features - the latest version of Numbers.
  1767.  
  1768. Peace.]]></description>
  1769. <content:encoded><![CDATA[<p>@Michael_Tsai, a direct quote from your post:</p>
  1770. <p>"Apple today updated its iWork apps Keynote, Numbers, and Pages with new features that require iOS 18.4, iPadOS 18.4, or macOS 15.4"</p>
  1771. <p>No explanation, and none needed. Except.... over 30 new functions? I guess some require Apple Intelligence in some sort of way? The way you quoted make it sounds like 14.4 *requires* macOS 15.4. It simply does not.</p>
  1772. <p>I have come to rely o your blog for both a place I can rely on for news (even if secondhand, you are awesome about attribution) and accuracy. My point with my comment maybe should have been directed elsewhere, but based on your post I thought it best to say macOS 14.X can still download - without certain AI features - the latest version of Numbers.</p>
  1773. <p>Peace.</p>
  1774. ]]></content:encoded>
  1775. </item>
  1776. <item>
  1777. <title>
  1778. Comment on Numbers 14.4 by Ulysses </title>
  1779. <link>https://mjtsai.com/blog/2025/04/07/numbers-14-4/#comment-4246849</link>
  1780.  
  1781. <dc:creator><![CDATA[Ulysses]]></dc:creator>
  1782. <pubDate>Mon, 07 Apr 2025 22:49:32 +0000</pubDate>
  1783. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47332#comment-4246849</guid>
  1784.  
  1785. <description><![CDATA[Numbers has unique (distinct) counts in pivot tables, while Excel for Mac still doesn’t have it after years and years.
  1786.  
  1787. Plus Excel has horrible tiny fonts and cruddy scientific number auto formatting when I open CSVs in it, whereas Numbers just displays my CSV intact and readable.  
  1788.  
  1789. I do wish Numbers get rid of the popup about “formatting can be changed” when opening CSVs though.  It covers up the column headers I&#039;m trying to read.]]></description>
  1790. <content:encoded><![CDATA[<p>Numbers has unique (distinct) counts in pivot tables, while Excel for Mac still doesn’t have it after years and years. </p>
  1791. <p>Plus Excel has horrible tiny fonts and cruddy scientific number auto formatting when I open CSVs in it, whereas Numbers just displays my CSV intact and readable.  </p>
  1792. <p>I do wish Numbers get rid of the popup about “formatting can be changed” when opening CSVs though.  It covers up the column headers I'm trying to read.</p>
  1793. ]]></content:encoded>
  1794. </item>
  1795. <item>
  1796. <title>
  1797. Comment on Rebuilding the Social Security Administration&#8217;s Codebase by Anonymous </title>
  1798. <link>https://mjtsai.com/blog/2025/04/02/rebuilding-the-social-security-administrations-codebase/#comment-4246828</link>
  1799.  
  1800. <dc:creator><![CDATA[Anonymous]]></dc:creator>
  1801. <pubDate>Mon, 07 Apr 2025 21:15:32 +0000</pubDate>
  1802. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47290#comment-4246828</guid>
  1803.  
  1804. <description><![CDATA[re: &quot;easier to find developers&quot; -- this is to allow the bossman to churn employees who don&#039;t kiss the ring. It used to be that merit mattered, or so went the illusion, now it&#039;s more the case that Capital wants everyone to be a gig worker, even employees. These skilled Cobol programmers have too much security for The Modern Workforce. Employees need to be contingent, otherwise they might have opinions.]]></description>
  1805. <content:encoded><![CDATA[<p>re: "easier to find developers" -- this is to allow the bossman to churn employees who don't kiss the ring. It used to be that merit mattered, or so went the illusion, now it's more the case that Capital wants everyone to be a gig worker, even employees. These skilled Cobol programmers have too much security for The Modern Workforce. Employees need to be contingent, otherwise they might have opinions.</p>
  1806. ]]></content:encoded>
  1807. </item>
  1808. </channel>
  1809. </rss>
  1810.  

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