FEED Validator

Congratulations!

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.

• line 85, column 0: style attribute contains potentially dangerous content: max-height (2 occurrences) [help]

  					<description><![CDATA[Abracadabra where did the code snippets + button  ...
  

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/"
7. >
8. <channel>
9. <title>
10. Comments for Michael Tsai </title>
11. <atom:link href="https://mjtsai.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
12. <link>https://mjtsai.com/blog</link>
13. <description></description>
14. <lastBuildDate>Wed, 17 Sep 2025 05:37:57 +0000</lastBuildDate>
15. <sy:updatePeriod>
16. hourly </sy:updatePeriod>
17. <sy:updateFrequency>
18. 1 </sy:updateFrequency>
19. <generator>https://wordpress.org/?v=6.2.2</generator>
20. <item>
21. <title>
22. Comment on Final Cut Camera 2.0 by Daniel </title>
23. <link>https://mjtsai.com/blog/2025/09/11/final-cut-camera-2-0/#comment-4307417</link>
24.  
25. <dc:creator><![CDATA[Daniel]]></dc:creator>
26. <pubDate>Wed, 17 Sep 2025 05:37:57 +0000</pubDate>
27. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49254#comment-4307417</guid>
28.  
29. <description><![CDATA[I wish they borrowed the recent Kino update for mic selection since some mics break, flooding videos with static]]></description>
30. <content:encoded><![CDATA[<p>I wish they borrowed the recent Kino update for mic selection since some mics break, flooding videos with static</p>
31. ]]></content:encoded>
33. </item>
34. <item>
35. <title>
36. Comment on Xcode 26 by Michael Tsai </title>
37. <link>https://mjtsai.com/blog/2025/09/16/xcode-26/#comment-4307343</link>
38.  
39. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
40. <pubDate>Tue, 16 Sep 2025 23:48:30 +0000</pubDate>
41. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49299#comment-4307343</guid>
42.  
43. <description><![CDATA[@Brendan Ah, you’re right. I must have been comparing the first two lines, which are both the release version (since they have a separate Apple Silicon build now).]]></description>
44. <content:encoded><![CDATA[<p>@Brendan Ah, you’re right. I must have been comparing the first two lines, which are both the release version (since they have a separate Apple Silicon build now).</p>
45. ]]></content:encoded>
47. </item>
48. <item>
49. <title>
50. Comment on Xcode 26 by Brendan </title>
51. <link>https://mjtsai.com/blog/2025/09/16/xcode-26/#comment-4307341</link>
52.  
53. <dc:creator><![CDATA[Brendan]]></dc:creator>
54. <pubDate>Tue, 16 Sep 2025 23:41:07 +0000</pubDate>
55. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49299#comment-4307341</guid>
56.  
57. <description><![CDATA[xcodereleases shows that the release build number (17A324) is incremented from the RC (17A321)]]></description>
58. <content:encoded><![CDATA[<p>xcodereleases shows that the release build number (17A324) is incremented from the RC (17A321)</p>
59. ]]></content:encoded>
61. </item>
62. <item>
63. <title>
64. Comment on ToothFairy 2.8.7 by Michael Tsai </title>
65. <link>https://mjtsai.com/blog/2025/09/16/toothfairy-2-8-7/#comment-4307337</link>
66.  
67. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
68. <pubDate>Tue, 16 Sep 2025 23:23:20 +0000</pubDate>
69. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49301#comment-4307337</guid>
70.  
71. <description><![CDATA[@Bart I think most people are using Icon Composer, and some seem to be adapting old-format icons by making sure everything fits into the squircle. Is there more to it than that?]]></description>
72. <content:encoded><![CDATA[<p>@Bart I think most people are using Icon Composer, and some seem to be adapting old-format icons by making sure everything fits into the squircle. Is there more to it than that?</p>
73. ]]></content:encoded>
75. </item>
76. <item>
77. <title>
78. Comment on Xcode 26 by ObjC4Life </title>
79. <link>https://mjtsai.com/blog/2025/09/16/xcode-26/#comment-4307336</link>
80.  
81. <dc:creator><![CDATA[ObjC4Life]]></dc:creator>
82. <pubDate>Tue, 16 Sep 2025 23:23:11 +0000</pubDate>
83. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49299#comment-4307336</guid>
84.  
85. <description><![CDATA[Abracadabra where did the code snippets + button go?  Poof<img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f4a8.png" alt="💨" class="wp-smiley" style="height: 1em; max-height: 1em;" />]]></description>
86. <content:encoded><![CDATA[<p>Abracadabra where did the code snippets + button go?  Poof💨</p>
87. ]]></content:encoded>
89. </item>
90. <item>
91. <title>
92. Comment on ToothFairy 2.8.7 by Bart </title>
93. <link>https://mjtsai.com/blog/2025/09/16/toothfairy-2-8-7/#comment-4307332</link>
94.  
95. <dc:creator><![CDATA[Bart]]></dc:creator>
96. <pubDate>Tue, 16 Sep 2025 23:13:32 +0000</pubDate>
97. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49301#comment-4307332</guid>
98.  
99. <description><![CDATA[Might I suggest a post about apps and techniques to break free of Squircle Jail? This seems like a great blog for it.]]></description>
100. <content:encoded><![CDATA[<p>Might I suggest a post about apps and techniques to break free of Squircle Jail? This seems like a great blog for it.</p>
101. ]]></content:encoded>
103. </item>
104. <item>
105. <title>
106. Comment on Icon Composer Notes by Christopher Snowhill </title>
107. <link>https://mjtsai.com/blog/2025/06/23/icon-composer-notes/#comment-4307330</link>
108.  
109. <dc:creator><![CDATA[Christopher Snowhill]]></dc:creator>
110. <pubDate>Tue, 16 Sep 2025 22:59:43 +0000</pubDate>
111. <guid isPermaLink="false">https://mjtsai.com/blog/?p=48182#comment-4307330</guid>
112.  
113. <description><![CDATA[I&#039;ve gotten composer icons to load with NSImage imageNamed: from Xcode 26 final builds, but I haven&#039;t figured out how to make it load any variation other than the light style.]]></description>
114. <content:encoded><![CDATA[<p>I've gotten composer icons to load with NSImage imageNamed: from Xcode 26 final builds, but I haven't figured out how to make it load any variation other than the light style.</p>
115. ]]></content:encoded>
117. </item>
118. <item>
119. <title>
120. Comment on watchOS 26 by Bart </title>
121. <link>https://mjtsai.com/blog/2025/09/16/watchos-26/#comment-4307323</link>
122.  
123. <dc:creator><![CDATA[Bart]]></dc:creator>
124. <pubDate>Tue, 16 Sep 2025 22:25:47 +0000</pubDate>
125. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49295#comment-4307323</guid>
126.  
127. <description><![CDATA[Someone has got to be trolling with that Liquid Glass watch face. The time is completely illegible.]]></description>
128. <content:encoded><![CDATA[<p>Someone has got to be trolling with that Liquid Glass watch face. The time is completely illegible.</p>
129. ]]></content:encoded>
131. </item>
132. <item>
133. <title>
134. Comment on iOS 26 by Chris Brandow </title>
135. <link>https://mjtsai.com/blog/2025/09/15/ios-26/#comment-4307299</link>
136.  
137. <dc:creator><![CDATA[Chris Brandow]]></dc:creator>
138. <pubDate>Tue, 16 Sep 2025 20:26:01 +0000</pubDate>
139. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49276#comment-4307299</guid>
140.  
141. <description><![CDATA[I had held off on iOS 26 until now. Whoa it&#039;s rough on both implementation, jumpy/odd animations on an iPhone 16 pro and navigation perspective, like i couldn&#039;t figure out how to save a screenshot to photos.
142.  
143. I was trying to keep a non-jaded, open mind, but that posture crumbled almost immediately upon contact.]]></description>
144. <content:encoded><![CDATA[<p>I had held off on iOS 26 until now. Whoa it's rough on both implementation, jumpy/odd animations on an iPhone 16 pro and navigation perspective, like i couldn't figure out how to save a screenshot to photos.</p>
145. <p>I was trying to keep a non-jaded, open mind, but that posture crumbled almost immediately upon contact.</p>
146. ]]></content:encoded>
148. </item>
149. <item>
150. <title>
151. Comment on macOS 15.7 and macOS 14.8 by Daniel </title>
152. <link>https://mjtsai.com/blog/2025/09/15/macos-15-7-and-macos-14-8/#comment-4307296</link>
153.  
154. <dc:creator><![CDATA[Daniel]]></dc:creator>
155. <pubDate>Tue, 16 Sep 2025 20:12:44 +0000</pubDate>
156. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49274#comment-4307296</guid>
157.  
158. <description><![CDATA[I was very confused with the description I see here for the update:
159.  
160. > This update introduces 8 new emojis, the ability to create Memory movies in Photos with Apple Intelligence, a new Sketch Style option in Image Playground, Mail Categorization, and enhancements to better organize and filter your library in Photos. This release also includes other features, bug fixes, and security updates for your Mac.
161.  
162. Appears to be copy-pasted from 15.4 unchanged. (I&#039;m on 15.6.1)]]></description>
163. <content:encoded><![CDATA[<p>I was very confused with the description I see here for the update:</p>
164. <p>&gt; This update introduces 8 new emojis, the ability to create Memory movies in Photos with Apple Intelligence, a new Sketch Style option in Image Playground, Mail Categorization, and enhancements to better organize and filter your library in Photos. This release also includes other features, bug fixes, and security updates for your Mac.</p>
165. <p>Appears to be copy-pasted from 15.4 unchanged. (I'm on 15.6.1)</p>
166. ]]></content:encoded>
168. </item>
169. <item>
170. <title>
171. Comment on macOS Tahoe 26 by Bart </title>
172. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307264</link>
173.  
174. <dc:creator><![CDATA[Bart]]></dc:creator>
175. <pubDate>Tue, 16 Sep 2025 18:18:03 +0000</pubDate>
176. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307264</guid>
177.  
178. <description><![CDATA[@ObjC4Life the Trash Can is the most telling thing about their dumb icon idea. They seem to realize they couldn’t ruin that one because this whole concept is flawed and incompatible with the concept of the Trash Can icon.
179.  
180. Unfortunately I think it will be Trash Can that gets the bin before this poorly conceived icon scheme.]]></description>
181. <content:encoded><![CDATA[<p>@ObjC4Life the Trash Can is the most telling thing about their dumb icon idea. They seem to realize they couldn’t ruin that one because this whole concept is flawed and incompatible with the concept of the Trash Can icon. </p>
182. <p>Unfortunately I think it will be Trash Can that gets the bin before this poorly conceived icon scheme.</p>
183. ]]></content:encoded>
185. </item>
186. <item>
187. <title>
188. Comment on macOS Tahoe 26 by ObjC4Life </title>
189. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307257</link>
190.  
191. <dc:creator><![CDATA[ObjC4Life]]></dc:creator>
192. <pubDate>Tue, 16 Sep 2025 17:43:37 +0000</pubDate>
193. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307257</guid>
194.  
195. <description><![CDATA[Guess the Trash icon gets a get out of squircle jail free card]]></description>
196. <content:encoded><![CDATA[<p>Guess the Trash icon gets a get out of squircle jail free card</p>
197. ]]></content:encoded>
199. </item>
200. <item>
201. <title>
202. Comment on Separate Icons for macOS Tahoe vs. Earlier by Objc4Life </title>
203. <link>https://mjtsai.com/blog/2025/08/08/separate-icons-for-macos-tahoe-vs-earlier/#comment-4307254</link>
204.  
205. <dc:creator><![CDATA[Objc4Life]]></dc:creator>
206. <pubDate>Tue, 16 Sep 2025 17:41:51 +0000</pubDate>
207. <guid isPermaLink="false">https://mjtsai.com/blog/?p=48842#comment-4307254</guid>
208.  
209. <description><![CDATA[So you can export from icon composer without the lighting effect.
210.  
211. 1) Customize the Toolbar
212. 2) add a FX toolbar item and toggle it off.
213. 3) Then export.
214.  
215. Weird that the option to turn off FX is not in the export panel though.]]></description>
216. <content:encoded><![CDATA[<p>So you can export from icon composer without the lighting effect. </p>
217. <p>1) Customize the Toolbar<br />
218. 2) add a FX toolbar item and toggle it off.<br />
219. 3) Then export. </p>
220. <p>Weird that the option to turn off FX is not in the export panel though.</p>
221. ]]></content:encoded>
223. </item>
224. <item>
225. <title>
226. Comment on The Mac App Flea Market by Bart </title>
227. <link>https://mjtsai.com/blog/2025/09/15/the-mac-app-flea-market/#comment-4307245</link>
228.  
229. <dc:creator><![CDATA[Bart]]></dc:creator>
230. <pubDate>Tue, 16 Sep 2025 16:45:28 +0000</pubDate>
231. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49272#comment-4307245</guid>
232.  
233. <description><![CDATA[The Mac App Store is bad. That sums it up. Everything it attempts to do, it does poorly.
234.  
235. I've found success with an app called Latest. I don't have much installed, and very little from the Mac App Store, but it found all the updates prior to upgrading to Tahoe, managed to one-click update all of them.
236.  
237. https://max.codes/latest/
238.  
239. Seems we really have never moved away from the package manager model. Things like that, winget on Windows. The &quot;App Store&quot; concept has run its course. It&#039;s just an especially bad, proprietary package manager now.]]></description>
240. <content:encoded><![CDATA[<p>The Mac App Store is bad. That sums it up. Everything it attempts to do, it does poorly.</p>
241. <p>I've found success with an app called Latest. I don't have much installed, and very little from the Mac App Store, but it found all the updates prior to upgrading to Tahoe, managed to one-click update all of them.</p>
242. <p><a href="https://max.codes/latest/" rel="nofollow ugc">https://max.codes/latest/</a></p>
243. <p>Seems we really have never moved away from the package manager model. Things like that, winget on Windows. The "App Store" concept has run its course. It's just an especially bad, proprietary package manager now.</p>
244. ]]></content:encoded>
246. </item>
247. <item>
248. <title>
249. Comment on macOS Tahoe 26 by DJ </title>
250. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307235</link>
251.  
252. <dc:creator><![CDATA[DJ]]></dc:creator>
253. <pubDate>Tue, 16 Sep 2025 16:22:35 +0000</pubDate>
254. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307235</guid>
255.  
256. <description><![CDATA[Regarding wifi: I occasionally see a device drop off my wifi network.  Sometimes turning the device&#039;s wifi off and on will get it back online.  Sometimes I&#039;ve had to &quot;forget&quot; that wifi network and then connect to it again.]]></description>
257. <content:encoded><![CDATA[<p>Regarding wifi: I occasionally see a device drop off my wifi network.  Sometimes turning the device's wifi off and on will get it back online.  Sometimes I've had to "forget" that wifi network and then connect to it again.</p>
258. ]]></content:encoded>
260. </item>
261. <item>
262. <title>
263. Comment on macOS Tahoe 26 by DJ </title>
264. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307230</link>
265.  
266. <dc:creator><![CDATA[DJ]]></dc:creator>
267. <pubDate>Tue, 16 Sep 2025 16:17:35 +0000</pubDate>
268. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307230</guid>
269.  
270. <description><![CDATA[I&#039;ve been running all of the 26 developer betas since WWDC, and they&#039;ve been fine.  I actually thought the changes would be more drastic than they are.  I don&#039;t understand why Apple would limit icons the way they have.  What&#039;s the harm in having some little something protrude from the edge(s)?  Let developers make icons look however they want to -- the &quot;modern Internet&quot; will come to our rescue and let them know if said icons suck.]]></description>
271. <content:encoded><![CDATA[<p>I've been running all of the 26 developer betas since WWDC, and they've been fine.  I actually thought the changes would be more drastic than they are.  I don't understand why Apple would limit icons the way they have.  What's the harm in having some little something protrude from the edge(s)?  Let developers make icons look however they want to -- the "modern Internet" will come to our rescue and let them know if said icons suck.</p>
272. ]]></content:encoded>
274. </item>
275. <item>
276. <title>
277. Comment on macOS Tahoe 26 by Bart </title>
278. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307223</link>
279.  
280. <dc:creator><![CDATA[Bart]]></dc:creator>
281. <pubDate>Tue, 16 Sep 2025 15:43:49 +0000</pubDate>
282. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307223</guid>
283.  
284. <description><![CDATA[I was surprised that nothing actually broke for me. I made sure to update all my apps using Latest before the upgrade.
285.  
286. The worst part by far is squircle jail. That was just unnecessary. Really hoping they fix that but I doubt it.
287.  
288. The second worst part is their justifications for it, which are all backwards talk doublespeak. It gets in the way, it doesn’t look that much better, doesn’t work better.
289.  
290. But not the worst thing they’ve ever done. They did actually fix a few small annoyances. Finder does actually look better and seems to work slightly better. Safari on Mac looks fine, but it’s awful on iOS.]]></description>
291. <content:encoded><![CDATA[<p>I was surprised that nothing actually broke for me. I made sure to update all my apps using Latest before the upgrade. </p>
292. <p>The worst part by far is squircle jail. That was just unnecessary. Really hoping they fix that but I doubt it. </p>
293. <p>The second worst part is their justifications for it, which are all backwards talk doublespeak. It gets in the way, it doesn’t look that much better, doesn’t work better. </p>
294. <p>But not the worst thing they’ve ever done. They did actually fix a few small annoyances. Finder does actually look better and seems to work slightly better. Safari on Mac looks fine, but it’s awful on iOS.</p>
295. ]]></content:encoded>
297. </item>
298. <item>
299. <title>
300. Comment on Separate Icons for macOS Tahoe vs. Earlier by Objc4Life </title>
301. <link>https://mjtsai.com/blog/2025/08/08/separate-icons-for-macos-tahoe-vs-earlier/#comment-4307216</link>
302.  
303. <dc:creator><![CDATA[Objc4Life]]></dc:creator>
304. <pubDate>Tue, 16 Sep 2025 15:18:40 +0000</pubDate>
305. <guid isPermaLink="false">https://mjtsai.com/blog/?p=48842#comment-4307216</guid>
306.  
307. <description><![CDATA[Heh so I exported a PNG from icon composer and added them to asset catalog to avoid squircle jail. Using icon composer ensured I got the masking right.
308.  
309. Issue with this: Looks fine pre-Tahoe but macOS Tahoe the System automatically seems to apply a lighting effect to all icons (regardless of whether you built your app on the new Xcode or not). But when you export a png from icon composer, it includes the lighting effect in the png (and there doesn't seem to be a way to export a png without the lighting effect). So on Tahoe the icon png has a lighting effect but it gets a double lighting effect and it looks bad.
310.  
311. I remember back in the early iOS days they would apply a gloss lighting to every app icon but there was an Info.plist key you could use to turn it off...is there anything like that for macOS Tahoe?]]></description>
312. <content:encoded><![CDATA[<p>Heh so I exported a PNG from icon composer and added them to asset catalog to avoid squircle jail. Using icon composer ensured I got the masking right.</p>
313. <p>Issue with this: Looks fine pre-Tahoe but macOS Tahoe the System automatically seems to apply a lighting effect to all icons (regardless of whether you built your app on the new Xcode or not). But when you export a png from icon composer, it includes the lighting effect in the png (and there doesn't seem to be a way to export a png without the lighting effect). So on Tahoe the icon png has a lighting effect but it gets a double lighting effect and it looks bad. </p>
314. <p>I remember back in the early iOS days they would apply a gloss lighting to every app icon but there was an Info.plist key you could use to turn it off...is there anything like that for macOS Tahoe?</p>
315. ]]></content:encoded>
317. </item>
318. <item>
319. <title>
320. Comment on iOS 26 by Michael Tsai </title>
321. <link>https://mjtsai.com/blog/2025/09/15/ios-26/#comment-4307203</link>
322.  
323. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
324. <pubDate>Tue, 16 Sep 2025 14:33:13 +0000</pubDate>
325. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49276#comment-4307203</guid>
326.  
327. <description><![CDATA[Thanks!]]></description>
328. <content:encoded><![CDATA[<p>Thanks!</p>
329. ]]></content:encoded>
331. </item>
332. <item>
333. <title>
334. Comment on macOS Tahoe 26 by Michael Tsai </title>
335. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307202</link>
336.  
337. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
338. <pubDate>Tue, 16 Sep 2025 14:33:01 +0000</pubDate>
339. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307202</guid>
340.  
341. <description><![CDATA[@Someone and Liquid: Thanks!]]></description>
342. <content:encoded><![CDATA[<p>@Someone and Liquid: Thanks!</p>
343. ]]></content:encoded>
345. </item>
346. <item>
347. <title>
348. Comment on iOS 26 by Liquid Digital </title>
349. <link>https://mjtsai.com/blog/2025/09/15/ios-26/#comment-4307200</link>
350.  
351. <dc:creator><![CDATA[Liquid Digital]]></dc:creator>
352. <pubDate>Tue, 16 Sep 2025 14:30:33 +0000</pubDate>
353. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49276#comment-4307200</guid>
354.  
355. <description><![CDATA[There is a new page for the &quot;What&#039;s new for enterprise for iOS 26”
356.  
357. https://support.apple.com/en-us/125073]]></description>
358. <content:encoded><![CDATA[<p>There is a new page for the "What's new for enterprise for iOS 26”</p>
359. <p><a href="https://support.apple.com/en-us/125073" rel="nofollow ugc">https://support.apple.com/en-us/125073</a></p>
360. ]]></content:encoded>
362. </item>
363. <item>
364. <title>
365. Comment on macOS Tahoe 26 by Liquid Digital </title>
366. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307199</link>
367.  
368. <dc:creator><![CDATA[Liquid Digital]]></dc:creator>
369. <pubDate>Tue, 16 Sep 2025 14:28:58 +0000</pubDate>
370. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307199</guid>
371.  
372. <description><![CDATA[There is a new page for the &quot;What&#039;s new for enterprise in macOS for Tahoe&quot;
373.  
374. https://support.apple.com/en-us/124963]]></description>
375. <content:encoded><![CDATA[<p>There is a new page for the "What's new for enterprise in macOS for Tahoe"</p>
376. <p><a href="https://support.apple.com/en-us/124963" rel="nofollow ugc">https://support.apple.com/en-us/124963</a></p>
377. ]]></content:encoded>
379. </item>
380. <item>
381. <title>
382. Comment on macOS Tahoe 26 by Michael Tsai </title>
383. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307192</link>
384.  
385. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
386. <pubDate>Tue, 16 Sep 2025 14:02:28 +0000</pubDate>
387. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307192</guid>
388.  
389. <description><![CDATA[@Objc4Life I had the same problem right after updating (to the GM, never with any of the betas). Instead of the firewall, I toggled Wi-Fi a few times, and eventually it worked.]]></description>
390. <content:encoded><![CDATA[<p>@Objc4Life I had the same problem right after updating (to the GM, never with any of the betas). Instead of the firewall, I toggled Wi-Fi a few times, and eventually it worked.</p>
391. ]]></content:encoded>
393. </item>
394. <item>
395. <title>
396. Comment on macOS Tahoe 26 by Objc4Life </title>
397. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307187</link>
398.  
399. <dc:creator><![CDATA[Objc4Life]]></dc:creator>
400. <pubDate>Tue, 16 Sep 2025 13:44:28 +0000</pubDate>
401. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307187</guid>
402.  
403. <description><![CDATA[I&#039;ll throw this out there in case anyone else runs into this:
404.  
405. I was unable to get a network connection after updating to Tahoe. Settings displays my network status as "connected" but nothing was loading. Safari says "You are not connected to the internet". Turned on Personal Hotspot on my iPhone and tried to connect to that network instead. Still nothing.
406. All other devices connected to the same Wifi network were working as expected, so it wasn't that. Tried a restart. Nope.
407.  
408. So I did a quick Google search on my iPad and someone posted a comment in a Youtube video that said to turn on Firewall in System Settings. I didn&#039;t expect that to work... but it did.]]></description>
409. <content:encoded><![CDATA[<p>I'll throw this out there in case anyone else runs into this:</p>
410. <p>I was unable to get a network connection after updating to Tahoe. Settings displays my network status as "connected" but nothing was loading. Safari says "You are not connected to the internet". Turned on Personal Hotspot on my iPhone and tried to connect to that network instead. Still nothing.<br />
411. All other devices connected to the same Wifi network were working as expected, so it wasn't that. Tried a restart. Nope.</p>
412. <p>So I did a quick Google search on my iPad and someone posted a comment in a Youtube video that said to turn on Firewall in System Settings. I didn't expect that to work... but it did.</p>
413. ]]></content:encoded>
415. </item>
416. <item>
417. <title>
418. Comment on macOS Tahoe 26 by Mogden </title>
419. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307180</link>
420.  
421. <dc:creator><![CDATA[Mogden]]></dc:creator>
422. <pubDate>Tue, 16 Sep 2025 13:28:23 +0000</pubDate>
423. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307180</guid>
424.  
425. <description><![CDATA[I installed it just to take a look at the horror show that everyone rants about.  Well, to me anyway, it looks fine.  There are quirks in spots, but overall quite usable.  I think I could install this on my parents&#039; computers and they would barely notice.]]></description>
426. <content:encoded><![CDATA[<p>I installed it just to take a look at the horror show that everyone rants about.  Well, to me anyway, it looks fine.  There are quirks in spots, but overall quite usable.  I think I could install this on my parents' computers and they would barely notice.</p>
427. ]]></content:encoded>
429. </item>
430. <item>
431. <title>
432. Comment on macOS Tahoe 26 by ObjC4Life </title>
433. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307168</link>
434.  
435. <dc:creator><![CDATA[ObjC4Life]]></dc:creator>
436. <pubDate>Tue, 16 Sep 2025 12:59:42 +0000</pubDate>
437. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307168</guid>
438.  
439. <description><![CDATA[Just installed. The new “app launcher” Spotlight window is especially annoying. I have this ultra wide monitor and it looks ridiculously narrow. I instinctively keep trying to enlarge it but like System Settings width resizing is not allowed…
440.  
441. The left aligned text and image in alerts looks weird.]]></description>
442. <content:encoded><![CDATA[<p>Just installed. The new “app launcher” Spotlight window is especially annoying. I have this ultra wide monitor and it looks ridiculously narrow. I instinctively keep trying to enlarge it but like System Settings width resizing is not allowed…</p>
443. <p>The left aligned text and image in alerts looks weird.</p>
444. ]]></content:encoded>
446. </item>
447. <item>
448. <title>
449. Comment on macOS Tahoe 26 by Michael Tsai </title>
450. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307164</link>
451.  
452. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
453. <pubDate>Tue, 16 Sep 2025 12:45:29 +0000</pubDate>
454. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307164</guid>
455.  
456. <description><![CDATA[@BillyOK I’ve been retaking the screenshots for my apps (and their instructions that refer to System Settings, etc.), and it presents a question. If I just set things up normally for the screenshot, sometimes part of the window looks really bad, with unreadable text. To me, that ruins the shot in that even though it’s accurate it distracts and sometimes messes up what I’m trying to communicate. So I find that, instead of capturing au naturel, I’m making micro adjustments to make it look as good as possible (e.g. &lt;a href=&quot;https://c-command.com/spamsieve/images/3.2/automation-access@2x.png&quot; rel=&quot;nofollow ugc&quot;&gt;here&lt;/a&gt; I have made sure there’s no colored icon underneath the search field). I don’t know whether others are doing the same, but my guess is that if you look at screenshots that are not &lt;em&gt;intended&lt;/em&gt; to critique Liquid Glass they are not a fair representation of what it’s like in actual use. (Also, if you take a window screenshot it often doesn’t capture how the window’s background actually looks…)]]></description>
457. <content:encoded><![CDATA[<p>@BillyOK I’ve been retaking the screenshots for my apps (and their instructions that refer to System Settings, etc.), and it presents a question. If I just set things up normally for the screenshot, sometimes part of the window looks really bad, with unreadable text. To me, that ruins the shot in that even though it’s accurate it distracts and sometimes messes up what I’m trying to communicate. So I find that, instead of capturing au naturel, I’m making micro adjustments to make it look as good as possible (e.g. <a href="https://c-command.com/spamsieve/images/3.2/automation-access@2x.png" rel="nofollow ugc">here</a> I have made sure there’s no colored icon underneath the search field). I don’t know whether others are doing the same, but my guess is that if you look at screenshots that are not <em>intended</em> to critique Liquid Glass they are not a fair representation of what it’s like in actual use. (Also, if you take a window screenshot it often doesn’t capture how the window’s background actually looks…)</p>
458. ]]></content:encoded>
460. </item>
461. <item>
462. <title>
463. Comment on macOS Tahoe 26 by BillyOK </title>
464. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307157</link>
465.  
466. <dc:creator><![CDATA[BillyOK]]></dc:creator>
467. <pubDate>Tue, 16 Sep 2025 12:26:30 +0000</pubDate>
468. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307157</guid>
469.  
470. <description><![CDATA[Not angry about it but I too was dismayed at the reviews I read, then skimmed as that dismay settled in. Soft language to excuse an absolutely user-hostile-for-no-reason UI redesign. We’ll all just get used to the frying ban being a little warmer I guess.
471.  
472. Probably the last year I’ll read these reviews. A damning screenshot goes a much longer way, and there are plenty of those to be found.]]></description>
473. <content:encoded><![CDATA[<p>Not angry about it but I too was dismayed at the reviews I read, then skimmed as that dismay settled in. Soft language to excuse an absolutely user-hostile-for-no-reason UI redesign. We’ll all just get used to the frying ban being a little warmer I guess. </p>
474. <p>Probably the last year I’ll read these reviews. A damning screenshot goes a much longer way, and there are plenty of those to be found.</p>
475. ]]></content:encoded>
477. </item>
478. <item>
479. <title>
480. Comment on macOS Tahoe 26 by Michael Tsai </title>
481. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307151</link>
482.  
483. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
484. <pubDate>Tue, 16 Sep 2025 12:17:21 +0000</pubDate>
485. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307151</guid>
486.  
487. <description><![CDATA[@Hammer I thought &lt;a href=&quot;https://sixcolors.com/post/2025/09/ios-26-review-through-a-glass-liquidly/&quot; rel=&quot;nofollow ugc&quot;&gt;Dan Moren&lt;/a&gt; had a good take (on iOS).]]></description>
488. <content:encoded><![CDATA[<p>@Hammer I thought <a href="https://sixcolors.com/post/2025/09/ios-26-review-through-a-glass-liquidly/" rel="nofollow ugc">Dan Moren</a> had a good take (on iOS).</p>
489. ]]></content:encoded>
491. </item>
492. <item>
493. <title>
494. Comment on macOS Tahoe 26 by Plume </title>
495. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307144</link>
496.  
497. <dc:creator><![CDATA[Plume]]></dc:creator>
498. <pubDate>Tue, 16 Sep 2025 11:27:02 +0000</pubDate>
499. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307144</guid>
500.  
501. <description><![CDATA[&#062; afraid of losing their precious Apple invites
502.  
503. Or maybe they just genuinely have a different opinion.
504.  
505. > You can't hate journalists enough.
506.  
507. This is an absolutely ridiculous overreaction to people not mirroring your hatred for a new UI design, regardless of how bad it is.]]></description>
508. <content:encoded><![CDATA[<p>&gt; afraid of losing their precious Apple invites</p>
509. <p>Or maybe they just genuinely have a different opinion.</p>
510. <p>&gt; You can't hate journalists enough.</p>
511. <p>This is an absolutely ridiculous overreaction to people not mirroring your hatred for a new UI design, regardless of how bad it is.</p>
512. ]]></content:encoded>
514. </item>
515. <item>
516. <title>
517. Comment on The Mac App Flea Market by Plume </title>
518. <link>https://mjtsai.com/blog/2025/09/15/the-mac-app-flea-market/#comment-4307143</link>
519.  
520. <dc:creator><![CDATA[Plume]]></dc:creator>
521. <pubDate>Tue, 16 Sep 2025 11:21:13 +0000</pubDate>
522. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49272#comment-4307143</guid>
523.  
524. <description><![CDATA[The Mac App Store is generally bad at noticing when updates are available. If you use the sadly moribund MacUpdater app, you&#039;ll see that it usually lists about twice as many App Store apps with available updates as the App Store itself does.]]></description>
525. <content:encoded><![CDATA[<p>The Mac App Store is generally bad at noticing when updates are available. If you use the sadly moribund MacUpdater app, you'll see that it usually lists about twice as many App Store apps with available updates as the App Store itself does.</p>
526. ]]></content:encoded>
528. </item>
529. <item>
530. <title>
531. Comment on macOS 15.7 and macOS 14.8 by ED </title>
532. <link>https://mjtsai.com/blog/2025/09/15/macos-15-7-and-macos-14-8/#comment-4307134</link>
533.  
534. <dc:creator><![CDATA[ED]]></dc:creator>
535. <pubDate>Tue, 16 Sep 2025 10:50:18 +0000</pubDate>
536. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49274#comment-4307134</guid>
537.  
538. <description><![CDATA[Oh! I always &lt;a href=&quot;https://mastodon.social/@ednl/115213710177084687&quot; rel=&quot;nofollow ugc&quot;&gt;enable&lt;/a&gt; Tab layout = Compact in Safari Settings. All the troubles disappear, everything works again, with Tab layout = Separate. Still, that is not what I like so this is very disappointing.]]></description>
539. <content:encoded><![CDATA[<p>Oh! I always <a href="https://mastodon.social/@ednl/115213710177084687" rel="nofollow ugc">enable</a> Tab layout = Compact in Safari Settings. All the troubles disappear, everything works again, with Tab layout = Separate. Still, that is not what I like so this is very disappointing.</p>
540. ]]></content:encoded>
542. </item>
543. <item>
544. <title>
545. Comment on macOS Tahoe 26 by Hammer </title>
546. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307132</link>
547.  
548. <dc:creator><![CDATA[Hammer]]></dc:creator>
549. <pubDate>Tue, 16 Sep 2025 10:43:16 +0000</pubDate>
550. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307132</guid>
551.  
552. <description><![CDATA[Every review I&#039;ve read for macOS 26 shows 0 taste in UI and 100% cowardice:
553.  
554. "Liquid Glass isn’t perfect" -- John Voorhees
555. "You mostly won’t notice it" -- Jason Snell
556. "I could take or leave Liquid Glass—I mostly don't mind it" -- Andrew Cunningham
557.  
558. All of them cucked, afraid of losing their precious Apple invites. Lukewarm takes, little pushback, not worth reading.
559.  
560. You can&#039;t hate journalists enough.]]></description>
561. <content:encoded><![CDATA[<p>Every review I've read for macOS 26 shows 0 taste in UI and 100% cowardice:</p>
562. <p>"Liquid Glass isn’t perfect" -- John Voorhees<br />
563. "You mostly won’t notice it" -- Jason Snell<br />
564. "I could take or leave Liquid Glass—I mostly don't mind it" -- Andrew Cunningham</p>
565. <p>All of them cucked, afraid of losing their precious Apple invites. Lukewarm takes, little pushback, not worth reading.</p>
566. <p>You can't hate journalists enough.</p>
567. ]]></content:encoded>
569. </item>
570. <item>
571. <title>
572. Comment on macOS 15.7 and macOS 14.8 by ED </title>
573. <link>https://mjtsai.com/blog/2025/09/15/macos-15-7-and-macos-14-8/#comment-4307131</link>
574.  
575. <dc:creator><![CDATA[ED]]></dc:creator>
576. <pubDate>Tue, 16 Sep 2025 10:36:15 +0000</pubDate>
577. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49274#comment-4307131</guid>
578.  
579. <description><![CDATA[I updated to MacOS 15.7 on my M1 Mini (recently completely fresh reinstalled, using localised (Dutch) settings). Then I checked updates again and installed Command Line Tools for Xcode and Safari 26.0. This Safaris version is b0rked! Can&#039;t interact with the address bar, not by selecting it with the mouse anyway. Changing tabs by clicking works. The tab close icon, the address, the reload icon which does appear on hover, and that other icon are completely unresponsive. The remaining ways to close a tab are via the Safari menu, the context menu (had never seen that before today) or Cmd-W. Can&#039;t click to select or right-click the address, I have to Tab to it with Keyboard navigation enabled.]]></description>
580. <content:encoded><![CDATA[<p>I updated to MacOS 15.7 on my M1 Mini (recently completely fresh reinstalled, using localised (Dutch) settings). Then I checked updates again and installed Command Line Tools for Xcode and Safari 26.0. This Safaris version is b0rked! Can't interact with the address bar, not by selecting it with the mouse anyway. Changing tabs by clicking works. The tab close icon, the address, the reload icon which does appear on hover, and that other icon are completely unresponsive. The remaining ways to close a tab are via the Safari menu, the context menu (had never seen that before today) or Cmd-W. Can't click to select or right-click the address, I have to Tab to it with Keyboard navigation enabled.</p>
581. ]]></content:encoded>
583. </item>
584. <item>
585. <title>
586. Comment on The Mac App Flea Market by Alan Ralph </title>
587. <link>https://mjtsai.com/blog/2025/09/15/the-mac-app-flea-market/#comment-4307121</link>
588.  
589. <dc:creator><![CDATA[Alan Ralph]]></dc:creator>
590. <pubDate>Tue, 16 Sep 2025 09:56:18 +0000</pubDate>
591. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49272#comment-4307121</guid>
592.  
593. <description><![CDATA[@Jon H
594.  
595. My experience with the Mac App Store has been that apps only disappear from their if you manually hide them, or if the developer shuts up shop entirely.
596.  
597. I was amused to see that I still have the old iWork apps listed in my purchase history (this was before I got a new Mac and had them 'bundled' with the purchase.)
598.  
599. Confusingly, the summary of my iOS app purchases seems uncertain on which ones will run on my M3 MacBook Air. Clicking through to the app listing _usually_ helps, but sometimes it&#039;s a case of try it &#038; see. I&#039;ll a little sad that WTForecast doesn&#039;t appear to work, because I usually need cheering up when I check the weather forecast.]]></description>
600. <content:encoded><![CDATA[<p>@Jon H</p>
601. <p>My experience with the Mac App Store has been that apps only disappear from their if you manually hide them, or if the developer shuts up shop entirely.</p>
602. <p>I was amused to see that I still have the old iWork apps listed in my purchase history (this was before I got a new Mac and had them 'bundled' with the purchase.)</p>
603. <p>Confusingly, the summary of my iOS app purchases seems uncertain on which ones will run on my M3 MacBook Air. Clicking through to the app listing _usually_ helps, but sometimes it's a case of try it &amp; see. I'll a little sad that WTForecast doesn't appear to work, because I usually need cheering up when I check the weather forecast.</p>
604. ]]></content:encoded>
606. </item>
607. <item>
608. <title>
609. Comment on macOS Tahoe 26 by Marek </title>
610. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307066</link>
611.  
612. <dc:creator><![CDATA[Marek]]></dc:creator>
613. <pubDate>Tue, 16 Sep 2025 07:17:53 +0000</pubDate>
614. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307066</guid>
615.  
616. <description><![CDATA[Is it just me or the Tahoe in VM is incredibly slow? M1 Pro 32GB RAM. No other macOS is this slow.]]></description>
617. <content:encoded><![CDATA[<p>Is it just me or the Tahoe in VM is incredibly slow? M1 Pro 32GB RAM. No other macOS is this slow.</p>
618. ]]></content:encoded>
620. </item>
621. <item>
622. <title>
623. Comment on macOS Tahoe 26 by Ben </title>
624. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307060</link>
625.  
626. <dc:creator><![CDATA[Ben]]></dc:creator>
627. <pubDate>Tue, 16 Sep 2025 07:04:40 +0000</pubDate>
628. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307060</guid>
629.  
630. <description><![CDATA[I&#039;m not sure if it&#039;s an preceptory illusion, but my M4 iMac actually feels faster after installing 26.
631.  
632. The menu bar menus icons are missing, and that&#039;s jarring, the menubar being invisible is also a weird ui mode, but the thing with the roughest edge is the new sidebar ui pattern. In safari, edge-to-edge imagery is is stopped short of the edge of the sidebar.]]></description>
633. <content:encoded><![CDATA[<p>I'm not sure if it's an preceptory illusion, but my M4 iMac actually feels faster after installing 26.</p>
634. <p>The menu bar menus icons are missing, and that's jarring, the menubar being invisible is also a weird ui mode, but the thing with the roughest edge is the new sidebar ui pattern. In safari, edge-to-edge imagery is is stopped short of the edge of the sidebar.</p>
635. ]]></content:encoded>
637. </item>
638. <item>
639. <title>
640. Comment on macOS Tahoe 26 by ghill </title>
641. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4307051</link>
642.  
643. <dc:creator><![CDATA[ghill]]></dc:creator>
644. <pubDate>Tue, 16 Sep 2025 06:31:15 +0000</pubDate>
645. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4307051</guid>
646.  
647. <description><![CDATA[I decided to install it on my Mac. Good lord it&#039;s bad. The menu icons mean absolutely nothing to me. Third-party **and first-party** apps use vaguely similar icons to mean different things, and use very different icons to mean the same things. I just end up not using them to help me find the menu items, and the icons just end up cluttering the menus. The app icons are a tragedy.
648.  
649. Needless to say I strongly dislike the Liquid Glass rendition here, not to mention all the bugs from previous 10+ macOS releases that still haven't been fixed and the many more they've just added pushing this release out when it clearly needs more time.
650.  
651. Yeah, they absolutely love the Mac.]]></description>
652. <content:encoded><![CDATA[<p>I decided to install it on my Mac. Good lord it's bad. The menu icons mean absolutely nothing to me. Third-party **and first-party** apps use vaguely similar icons to mean different things, and use very different icons to mean the same things. I just end up not using them to help me find the menu items, and the icons just end up cluttering the menus. The app icons are a tragedy.</p>
653. <p>Needless to say I strongly dislike the Liquid Glass rendition here, not to mention all the bugs from previous 10+ macOS releases that still haven't been fixed and the many more they've just added pushing this release out when it clearly needs more time.</p>
654. <p>Yeah, they absolutely love the Mac.</p>
655. ]]></content:encoded>
657. </item>
658. <item>
659. <title>
660. Comment on macOS Tahoe 26 by Someone </title>
661. <link>https://mjtsai.com/blog/2025/09/15/macos-tahoe-26/#comment-4306977</link>
662.  
663. <dc:creator><![CDATA[Someone]]></dc:creator>
664. <pubDate>Tue, 16 Sep 2025 00:44:14 +0000</pubDate>
665. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49278#comment-4306977</guid>
666.  
667. <description><![CDATA[Here’s the feature list: https://www.apple.com/os/pdf/All_New_Features_macOS_Tahoe_Sept_2025.pdf]]></description>
668. <content:encoded><![CDATA[<p>Here’s the feature list: <a href="https://www.apple.com/os/pdf/All_New_Features_macOS_Tahoe_Sept_2025.pdf" rel="nofollow ugc">https://www.apple.com/os/pdf/All_New_Features_macOS_Tahoe_Sept_2025.pdf</a></p>
669. ]]></content:encoded>
671. </item>
672. <item>
673. <title>
674. Comment on The Mac App Flea Market by Jon H </title>
675. <link>https://mjtsai.com/blog/2025/09/15/the-mac-app-flea-market/#comment-4306924</link>
676.  
677. <dc:creator><![CDATA[Jon H]]></dc:creator>
678. <pubDate>Mon, 15 Sep 2025 21:11:54 +0000</pubDate>
679. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49272#comment-4306924</guid>
680.  
681. <description><![CDATA[I&#039;ve noticed that the Mac App Store has stopped updating my apps, and apps don&#039;t even show that an update is available unless I go to the app&#039;s page in the store.
682.  
683. Also, for some reason the Mac App Store isn&#039;t even showing most of the Mac apps I&#039;ve downloaded or purchased from there. The list of iOS apps it shows is much more complete. Maybe that&#039;s because I&#039;m on Apple Silicon now, I don&#039;t know.]]></description>
684. <content:encoded><![CDATA[<p>I've noticed that the Mac App Store has stopped updating my apps, and apps don't even show that an update is available unless I go to the app's page in the store.</p>
685. <p>Also, for some reason the Mac App Store isn't even showing most of the Mac apps I've downloaded or purchased from there. The list of iOS apps it shows is much more complete. Maybe that's because I'm on Apple Silicon now, I don't know.</p>
686. ]]></content:encoded>
688. </item>
689. <item>
690. <title>
691. Comment on AirPods Live Translation Blocked for EU Users by Mark </title>
692. <link>https://mjtsai.com/blog/2025/09/12/airpods-live-translation-blocked-for-eu-users/#comment-4306902</link>
693.  
694. <dc:creator><![CDATA[Mark]]></dc:creator>
695. <pubDate>Mon, 15 Sep 2025 19:41:11 +0000</pubDate>
696. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49270#comment-4306902</guid>
697.  
698. <description><![CDATA[The other interoperability aspect is allowing the use of other translation services, such as Google Translate or even something like ChatGPT. And because Apple&#039;s translation service supports so few languages, I think support for other services would actually make this feature (and thus AirPods) more interesting for many consumers.]]></description>
699. <content:encoded><![CDATA[<p>The other interoperability aspect is allowing the use of other translation services, such as Google Translate or even something like ChatGPT. And because Apple's translation service supports so few languages, I think support for other services would actually make this feature (and thus AirPods) more interesting for many consumers.</p>
700. ]]></content:encoded>
702. </item>
703. <item>
704. <title>
705. Comment on AirPods Live Translation Blocked for EU Users by Benjamin </title>
706. <link>https://mjtsai.com/blog/2025/09/12/airpods-live-translation-blocked-for-eu-users/#comment-4306895</link>
707.  
708. <dc:creator><![CDATA[Benjamin]]></dc:creator>
709. <pubDate>Mon, 15 Sep 2025 19:26:15 +0000</pubDate>
710. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49270#comment-4306895</guid>
711.  
712. <description><![CDATA[I think (if this is DMA related) it is likely related to interoperability. No other bluetooth headphone maker can integrate with Apple&#039;s on device translation service in the same way, giving Apple a competitive advantage that is leveraging the iPhone&#039;s dominance to sell AirPods in what is likely an anticompetitive way. Generally I think that the EU is right on this, if you want to run your translation model on the phone and just have the headphones be a basic microphone and speaker interface you can&#039;t only apple gets permission to do that... Theoretically any headphone maker could use the BLE interface to do this but Apple would have to allow the BLE headphones to launch a background translation service (which they allow themselves to do).]]></description>
713. <content:encoded><![CDATA[<p>I think (if this is DMA related) it is likely related to interoperability. No other bluetooth headphone maker can integrate with Apple's on device translation service in the same way, giving Apple a competitive advantage that is leveraging the iPhone's dominance to sell AirPods in what is likely an anticompetitive way. Generally I think that the EU is right on this, if you want to run your translation model on the phone and just have the headphones be a basic microphone and speaker interface you can't only apple gets permission to do that... Theoretically any headphone maker could use the BLE interface to do this but Apple would have to allow the BLE headphones to launch a background translation service (which they allow themselves to do).</p>
714. ]]></content:encoded>
716. </item>
717. <item>
718. <title>
719. Comment on AirPods Live Translation Blocked for EU Users by Mark </title>
720. <link>https://mjtsai.com/blog/2025/09/12/airpods-live-translation-blocked-for-eu-users/#comment-4306779</link>
721.  
722. <dc:creator><![CDATA[Mark]]></dc:creator>
723. <pubDate>Mon, 15 Sep 2025 11:32:39 +0000</pubDate>
724. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49270#comment-4306779</guid>
725.  
726. <description><![CDATA[Dutch news site Tweakers.net has a statement from Apple where they point to the Digital Markets Act (DMA) for blocking this feature in the EU: https://tweakers.net/nieuws/239120/apple-brengt-livevertalingen-met-airpods-vooralsnog-niet-in-eu-uit-vanwege-dma.html]]></description>
727. <content:encoded><![CDATA[<p>Dutch news site Tweakers.net has a statement from Apple where they point to the Digital Markets Act (DMA) for blocking this feature in the EU: <a href="https://tweakers.net/nieuws/239120/apple-brengt-livevertalingen-met-airpods-vooralsnog-niet-in-eu-uit-vanwege-dma.html" rel="nofollow ugc">https://tweakers.net/nieuws/239120/apple-brengt-livevertalingen-met-airpods-vooralsnog-niet-in-eu-uit-vanwege-dma.html</a></p>
728. ]]></content:encoded>
730. </item>
731. <item>
732. <title>
733. Comment on Tahoe Free Space Problems by Ernst Mulder </title>
734. <link>https://mjtsai.com/blog/2025/08/19/tahoe-free-space-problems/#comment-4306738</link>
735.  
736. <dc:creator><![CDATA[Ernst Mulder]]></dc:creator>
737. <pubDate>Mon, 15 Sep 2025 08:59:28 +0000</pubDate>
738. <guid isPermaLink="false">https://mjtsai.com/blog/?p=48956#comment-4306738</guid>
739.  
740. <description><![CDATA[One possible reason for disk usage is, as mentioned here previously, local snapshots (for Time Machine).
741.  
742. My Mac mini has multiple VM's running all day. Local snapshots of the VMs' data caused my Mac to run out of space. This even caused VM's to complain that they couldn't save data anymore.
743.  
744. To solve this I created a small LaunchDaemon that deletes all excess snapshots and leaves just four of them, for Time Machine and to have a fallback after accidentally deleting a file. It runs without root privileges under any admin account. I'll try to paste it here but I'm not sure if will get scrambled, so beware.
745.  
746. <pre>
747. #!/bin/sh
748. # Find list of snapshots, skipping the first four
749. excessshots=`/usr/bin/tmutil listlocalsnapshotdates | sed "1d" | sort -rn | sed "1,4d"`
750. # Delete excess snapshots
751. if [ -n "$excessshots" ]; then
752.  for i in $excessshots; do
753.    /usr/bin/tmutil deletelocalsnapshots $i
754.  done
755. fi
756. &lt;/pre&gt;]]></description>
757. <content:encoded><![CDATA[<p>One possible reason for disk usage is, as mentioned here previously, local snapshots (for Time Machine).</p>
758. <p>My Mac mini has multiple VM's running all day. Local snapshots of the VMs' data caused my Mac to run out of space. This even caused VM's to complain that they couldn't save data anymore.</p>
759. <p>To solve this I created a small LaunchDaemon that deletes all excess snapshots and leaves just four of them, for Time Machine and to have a fallback after accidentally deleting a file. It runs without root privileges under any admin account. I'll try to paste it here but I'm not sure if will get scrambled, so beware.</p>
760. <pre>
761. #!/bin/sh
762. # Find list of snapshots, skipping the first four
763. excessshots=`/usr/bin/tmutil listlocalsnapshotdates | sed "1d" | sort -rn | sed "1,4d"`
764. # Delete excess snapshots
765. if [ -n "$excessshots" ]; then
766.  for i in $excessshots; do
767.    /usr/bin/tmutil deletelocalsnapshots $i
768.  done
769. fi
770. </pre>
771. ]]></content:encoded>
773. </item>
774. <item>
775. <title>
776. Comment on AirPods Live Translation Blocked for EU Users by Martin </title>
777. <link>https://mjtsai.com/blog/2025/09/12/airpods-live-translation-blocked-for-eu-users/#comment-4306696</link>
778.  
779. <dc:creator><![CDATA[Martin]]></dc:creator>
780. <pubDate>Mon, 15 Sep 2025 07:04:01 +0000</pubDate>
781. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49270#comment-4306696</guid>
782.  
783. <description><![CDATA[You can easily buy live translate headphones in the EU: https://amzn.eu/d/0LwIMa4 a family member that struggles with English bought these recently and they work OK]]></description>
784. <content:encoded><![CDATA[<p>You can easily buy live translate headphones in the EU: <a href="https://amzn.eu/d/0LwIMa4" rel="nofollow ugc">https://amzn.eu/d/0LwIMa4</a> a family member that struggles with English bought these recently and they work OK</p>
785. ]]></content:encoded>
787. </item>
788. <item>
789. <title>
790. Comment on Enabling Defragmentation on APFS Hard Drives by TrinitronX </title>
791. <link>https://mjtsai.com/blog/2019/10/28/enabling-defragmentation-on-apfs-hard-drives/#comment-4306554</link>
792.  
793. <dc:creator><![CDATA[TrinitronX]]></dc:creator>
794. <pubDate>Sun, 14 Sep 2025 21:33:44 +0000</pubDate>
795. <guid isPermaLink="false">https://mjtsai.com/blog/?p=27078#comment-4306554</guid>
796.  
797. <description><![CDATA[&#062; Is there any way to explicitly run a full defrag?
798. >
799. > I'm trying to lower the high watermark on some APFS-formatted sparsebundles, hoping I could then `hdiutil compact` them
800.  
801. It appears that there is: https://apple.stackexchange.com/a/372168/46665
802.  
803. I did an experiment on a macOS VM which had been plagued by the disk image constantly ballooning and increasing in size.  First, I ensured that the QEMU VM was running with: "discard=unmap", "detect_zeroes=unmap", and "rotation_rate=1".  For example, this LibVirt domain XML:
804.  
805. ```xml
806.    
807.      
808.      
809.      
810.      
811.      
812.    
813. ```
814.  
815. This forced the qcow2 disk image to unmap any zero writes (try to keep the backing image sparse) and to trick the VM into thinking that the disk was an SSD ("rotation_rate=1" is the special value for SSD).
816.  
817. Then, in the macOS VM, I enabled SSD TRIM via: `sudo trimforce enable`
818.  
819. Thus, any TRIM/discard operations in the VM get mapped to "unmap" on the QCOW2 image storage layer.
820.  
821. Next, defrag was enabled on the APFS container for "/System/Volumes/Data" ("/dev/disk1s1" in my case):
822.  
823.    sudo diskutil apfs defragment /dev/disk1s1 enable
824.  
825.  
826. While Apple fails to fully and properly document the internals of "apfsd", we can glean some information from the system log.  To follow the live logs we can use "log stream" and filter on the "apfsd" process in a separate terminal:
827.  
828.     log stream --predicate 'process == "apfsd"'
829.  
830. Finally, to force the automatic defrag routines in apfsd, we can force disk access to every file on the "Data" volume (`find -x` to stay on the "Data" volume only):
831.  
832.    sudo find -x /System/Volumes/Data -type f -exec /bin/sh -c "head '{}' 2>&1 1>/dev/null" \; 2>&1 1>/dev/null
833.  
834. Watching the "apfsd" logs, we then see many mentions of the APFS volume identifier: "com.apple.apfs.defrag.disk1s1"
835.  
836. Unfortunately, Apple fails to fully document what apfsd is doing internally.  The apfsd man page is quite "sparse" (pun intended).
837.  
838. So, we can only assume that "apfsd" is defragmenting files as they are accessed based on mention of defrag routines and the "disk1s1" which we enabled for the same APFS volume earlier.  While this was ongoing, the QCOW2 disk image still kept its original size.  In order to shrink it back down, it appears that another tool must be run.  Often, one re-sparsifying trick is to write a file full of zeroes to fill up the disk with zeroes (thus triggering the "detect_zeroes=unmap" behavior), and immediately removing it:
839.  
840.    sudo dd if=/dev/zero bs=4096  of=${HOME}/ZERO_DISK ; sudo rm ${HOME}/ZERO_DISK
841.  
842. For QEMU images, there are also these tools: `virt-sparsify`, or `qemu-img convert`.  With `qemu-img convert`, the image can also be re-compressed to slim it down further.
843.  
844. For example:
845.  
846.    qemu-img convert -p -f qcow2 -O qcow2 -c -o compression_type=zstd  /var/lib/libvirt/images/macos-12-1_ORIGINAL.img  /var/lib/libvirt/images/macos-12-1_REPACKED.img
847.  
848. I assume for an APFS sparsebundle file, there may be some diskutil command that could re-sparsify it?]]></description>
849. <content:encoded><![CDATA[<p>&gt; Is there any way to explicitly run a full defrag?<br />
850. &gt;<br />
851. &gt; I'm trying to lower the high watermark on some APFS-formatted sparsebundles, hoping I could then `hdiutil compact` them</p>
852. <p>It appears that there is: <a href="https://apple.stackexchange.com/a/372168/46665" rel="nofollow ugc">https://apple.stackexchange.com/a/372168/46665</a></p>
853. <p>I did an experiment on a macOS VM which had been plagued by the disk image constantly ballooning and increasing in size.  First, I ensured that the QEMU VM was running with: "discard=unmap", "detect_zeroes=unmap", and "rotation_rate=1".  For example, this LibVirt domain XML:</p>
854. <p>```xml</p>
855. <p>```</p>
856. <p>This forced the qcow2 disk image to unmap any zero writes (try to keep the backing image sparse) and to trick the VM into thinking that the disk was an SSD ("rotation_rate=1" is the special value for SSD).</p>
857. <p>Then, in the macOS VM, I enabled SSD TRIM via: `sudo trimforce enable`</p>
858. <p>Thus, any TRIM/discard operations in the VM get mapped to "unmap" on the QCOW2 image storage layer.</p>
859. <p>Next, defrag was enabled on the APFS container for "/System/Volumes/Data" ("/dev/disk1s1" in my case):</p>
860. <p>    sudo diskutil apfs defragment /dev/disk1s1 enable</p>
861. <p>While Apple fails to fully and properly document the internals of "apfsd", we can glean some information from the system log.  To follow the live logs we can use "log stream" and filter on the "apfsd" process in a separate terminal:</p>
862. <p>     log stream --predicate 'process == "apfsd"'</p>
863. <p>Finally, to force the automatic defrag routines in apfsd, we can force disk access to every file on the "Data" volume (`find -x` to stay on the "Data" volume only):</p>
864. <p>    sudo find -x /System/Volumes/Data -type f -exec /bin/sh -c "head '{}' 2&gt;&amp;1 1&gt;/dev/null" \; 2&gt;&amp;1 1&gt;/dev/null</p>
865. <p>Watching the "apfsd" logs, we then see many mentions of the APFS volume identifier: "com.apple.apfs.defrag.disk1s1"</p>
866. <p>Unfortunately, Apple fails to fully document what apfsd is doing internally.  The apfsd man page is quite "sparse" (pun intended).</p>
867. <p>So, we can only assume that "apfsd" is defragmenting files as they are accessed based on mention of defrag routines and the "disk1s1" which we enabled for the same APFS volume earlier.  While this was ongoing, the QCOW2 disk image still kept its original size.  In order to shrink it back down, it appears that another tool must be run.  Often, one re-sparsifying trick is to write a file full of zeroes to fill up the disk with zeroes (thus triggering the "detect_zeroes=unmap" behavior), and immediately removing it:</p>
868. <p>    sudo dd if=/dev/zero bs=4096  of=${HOME}/ZERO_DISK ; sudo rm ${HOME}/ZERO_DISK</p>
869. <p>For QEMU images, there are also these tools: `virt-sparsify`, or `qemu-img convert`.  With `qemu-img convert`, the image can also be re-compressed to slim it down further.</p>
870. <p>For example:</p>
871. <p>    qemu-img convert -p -f qcow2 -O qcow2 -c -o compression_type=zstd  /var/lib/libvirt/images/macos-12-1_ORIGINAL.img  /var/lib/libvirt/images/macos-12-1_REPACKED.img</p>
872. <p>I assume for an APFS sparsebundle file, there may be some diskutil command that could re-sparsify it?</p>
873. ]]></content:encoded>
875. </item>
876. <item>
877. <title>
878. Comment on Search Engines and SEO Spam by Stuff &#8211; Letters to Me </title>
879. <link>https://mjtsai.com/blog/2022/01/04/search-engines-and-seo-spam/#comment-4306533</link>
880.  
881. <dc:creator><![CDATA[Stuff &#8211; Letters to Me]]></dc:creator>
882. <pubDate>Sun, 14 Sep 2025 20:31:27 +0000</pubDate>
883. <guid isPermaLink="false">https://mjtsai.com/blog/?p=34618#comment-4306533</guid>
884.  
885. <description><![CDATA[[&#8230;] https://mjtsai.com/blog/2022/01/04/search-engines-and-seo-spam/ [&#8230;]]]></description>
886. <content:encoded><![CDATA[<p>[&#8230;] <a href="https://mjtsai.com/blog/2022/01/04/search-engines-and-seo-spam/" rel="ugc">https://mjtsai.com/blog/2022/01/04/search-engines-and-seo-spam/</a> [&#8230;]</p>
887. ]]></content:encoded>
889. </item>
890. <item>
891. <title>
892. Comment on AirPods Live Translation Blocked for EU Users by Kristoffer </title>
893. <link>https://mjtsai.com/blog/2025/09/12/airpods-live-translation-blocked-for-eu-users/#comment-4306314</link>
894.  
895. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
896. <pubDate>Sun, 14 Sep 2025 07:29:28 +0000</pubDate>
897. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49270#comment-4306314</guid>
898.  
899. <description><![CDATA[Work each passing year I become more and more grateful for GDPR.
900.  
901. I love clicking on the Block All button after seeing a list of 300+ vendors that would like to track me.]]></description>
902. <content:encoded><![CDATA[<p>Work each passing year I become more and more grateful for GDPR.</p>
903. <p>I love clicking on the Block All button after seeing a list of 300+ vendors that would like to track me.</p>
904. ]]></content:encoded>
906. </item>
907. <item>
908. <title>
909. Comment on mg Text Editor by Lars-Johan Liman </title>
910. <link>https://mjtsai.com/blog/2023/08/28/mg-text-editor/#comment-4306309</link>
911.  
912. <dc:creator><![CDATA[Lars-Johan Liman]]></dc:creator>
913. <pubDate>Sun, 14 Sep 2025 06:57:32 +0000</pubDate>
914. <guid isPermaLink="false">https://mjtsai.com/blog/?p=40468#comment-4306309</guid>
915.  
916. <description><![CDATA[Well, it actually _has_ UTF-8 capabilities, even if I wouldn&#039;t call it support. Mg is agnostic about the character set. If you give the command
917.  
918. M-x meta-key-mode
919.  
920. it will toggle (default on) whether it reads &quot;meta commands&quot;. When you press your meta key, it will add the &quot;8th bit&quot; to the character you press, which &quot;destroys&quot; the ability to handle other character sets than plain 7-bit ASCII. Normally mg will interpret that as &quot;the 8th bit is set --&#062; the user pressed meta --&#062; this is a command, not a character&quot;. If you turn off meta-key mode, mg will put the characters in the buffer exactly as typed, so whatever non-ASCII characters you enter, they will end up in the buffer. The drawback is that your meta key no longer works a modifier key. It will only put strange characters in your buffer. You will have to resort to using ESC- for meta commands instead. It&#039;s a trade-off.]]></description>
921. <content:encoded><![CDATA[<p>Well, it actually _has_ UTF-8 capabilities, even if I wouldn't call it support. Mg is agnostic about the character set. If you give the command</p>
922. <p>M-x meta-key-mode</p>
923. <p>it will toggle (default on) whether it reads "meta commands". When you press your meta key, it will add the "8th bit" to the character you press, which "destroys" the ability to handle other character sets than plain 7-bit ASCII. Normally mg will interpret that as "the 8th bit is set --&gt; the user pressed meta --&gt; this is a command, not a character". If you turn off meta-key mode, mg will put the characters in the buffer exactly as typed, so whatever non-ASCII characters you enter, they will end up in the buffer. The drawback is that your meta key no longer works a modifier key. It will only put strange characters in your buffer. You will have to resort to using ESC- for meta commands instead. It's a trade-off.</p>
924. ]]></content:encoded>
926. </item>
927. <item>
928. <title>
929. Comment on AirPods Live Translation Blocked for EU Users by Sander van Dragt </title>
930. <link>https://mjtsai.com/blog/2025/09/12/airpods-live-translation-blocked-for-eu-users/#comment-4306055</link>
931.  
932. <dc:creator><![CDATA[Sander van Dragt]]></dc:creator>
933. <pubDate>Sat, 13 Sep 2025 09:06:07 +0000</pubDate>
934. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49270#comment-4306055</guid>
935.  
936. <description><![CDATA[So Apple admits it’s not a feature that preserves privacy?]]></description>
937. <content:encoded><![CDATA[<p>So Apple admits it’s not a feature that preserves privacy?</p>
938. ]]></content:encoded>
940. </item>
941. <item>
942. <title>
943. Comment on AirPods Live Translation Blocked for EU Users by someone </title>
944. <link>https://mjtsai.com/blog/2025/09/12/airpods-live-translation-blocked-for-eu-users/#comment-4306038</link>
945.  
946. <dc:creator><![CDATA[someone]]></dc:creator>
947. <pubDate>Sat, 13 Sep 2025 07:58:43 +0000</pubDate>
948. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49270#comment-4306038</guid>
949.  
950. <description><![CDATA[Apple Intelligence: Live Translations in Phone and FaceTime -&#062; French (France) (no &quot;- not available in the EU)
951.  
952. Apple Intelligence: Live Translation with AirPods -> French (France) - not available in the EU
953.  
954.  
955. Apple, the art of consistency.]]></description>
956. <content:encoded><![CDATA[<p>Apple Intelligence: Live Translations in Phone and FaceTime -&gt; French (France) (no "- not available in the EU)</p>
957. <p>Apple Intelligence: Live Translation with AirPods -&gt; French (France) - not available in the EU</p>
958. <p>Apple, the art of consistency.</p>
959. ]]></content:encoded>
961. </item>
962. <item>
963. <title>
964. Comment on AirPods Live Translation Blocked for EU Users by Léo Natan </title>
965. <link>https://mjtsai.com/blog/2025/09/12/airpods-live-translation-blocked-for-eu-users/#comment-4305932</link>
966.  
967. <dc:creator><![CDATA[Léo Natan]]></dc:creator>
968. <pubDate>Sat, 13 Sep 2025 02:43:33 +0000</pubDate>
969. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49270#comment-4305932</guid>
970.  
971. <description><![CDATA[How can these pesky European commies expect a god-tier feature such as live translate (that has been available on the competition for years) to work with lowly third party headphones???? Fucking communist fascists [/gruber]]]></description>
972. <content:encoded><![CDATA[<p>How can these pesky European commies expect a god-tier feature such as live translate (that has been available on the competition for years) to work with lowly third party headphones???? Fucking communist fascists [/gruber]</p>
973. ]]></content:encoded>
975. </item>
976. <item>
977. <title>
978. Comment on Apple Watch Series 11 by Ben G </title>
979. <link>https://mjtsai.com/blog/2025/09/09/apple-watch-series-11/#comment-4305890</link>
980.  
981. <dc:creator><![CDATA[Ben G]]></dc:creator>
982. <pubDate>Sat, 13 Sep 2025 00:04:00 +0000</pubDate>
983. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49200#comment-4305890</guid>
984.  
985. <description><![CDATA[Snooze. I have an AW7 and I still don&#039;t see a compelling reason to upgrade.]]></description>
986. <content:encoded><![CDATA[<p>Snooze. I have an AW7 and I still don't see a compelling reason to upgrade.</p>
987. ]]></content:encoded>
989. </item>
990. <item>
991. <title>
992. Comment on Windows 11 Install to Require Internet and Microsoft Account by Craig </title>
993. <link>https://mjtsai.com/blog/2025/04/04/windows-11-install-to-require-internet-and-microsoft-account/#comment-4305782</link>
994.  
995. <dc:creator><![CDATA[Craig]]></dc:creator>
996. <pubDate>Fri, 12 Sep 2025 18:21:46 +0000</pubDate>
997. <guid isPermaLink="false">https://mjtsai.com/blog/?p=47314#comment-4305782</guid>
998.  
999. <description><![CDATA[You sir are a god!  Installing fresh Windows 11 and the NRO switch no longer seems to work but I was able to use the command above to install on a standalone PC I use for running utilities and testing.]]></description>
1000. <content:encoded><![CDATA[<p>You sir are a god!  Installing fresh Windows 11 and the NRO switch no longer seems to work but I was able to use the command above to install on a standalone PC I use for running utilities and testing.</p>
1001. ]]></content:encoded>
1003. </item>
1004. <item>
1005. <title>
1006. Comment on iPhone Air by Torrington </title>
1007. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4305748</link>
1008.  
1009. <dc:creator><![CDATA[Torrington]]></dc:creator>
1010. <pubDate>Fri, 12 Sep 2025 17:09:10 +0000</pubDate>
1011. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4305748</guid>
1012.  
1013. <description><![CDATA[@Scott
1014.  
1015. > Give me back my mini!
1016.  
1017. Pretty much this.
1018.  
1019. I&#039;d half-expected they&#039;d roll out SE 4 out of 12/13 mini parts or something. Minis were alright. Sadly, that never transpired.]]></description>
1020. <content:encoded><![CDATA[<p>@Scott</p>
1021. <p>&gt; Give me back my mini!</p>
1022. <p>Pretty much this.</p>
1023. <p>I'd half-expected they'd roll out SE 4 out of 12/13 mini parts or something. Minis were alright. Sadly, that never transpired.</p>
1024. ]]></content:encoded>
1026. </item>
1027. <item>
1028. <title>
1029. Comment on Design Is How It Works by Bart </title>
1030. <link>https://mjtsai.com/blog/2025/09/10/design-is-how-it-works-2/#comment-4305716</link>
1031.  
1032. <dc:creator><![CDATA[Bart]]></dc:creator>
1033. <pubDate>Fri, 12 Sep 2025 16:05:21 +0000</pubDate>
1034. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49230#comment-4305716</guid>
1035.  
1036. <description><![CDATA[The software will continue to rot until CFed is replaced.
1037.  
1038. As charismatic as he is, cool nice guy, all that, he’s responsible for all software. And that has been everyone’s number one complaint basically since the first releases under his command.]]></description>
1039. <content:encoded><![CDATA[<p>The software will continue to rot until CFed is replaced. </p>
1040. <p>As charismatic as he is, cool nice guy, all that, he’s responsible for all software. And that has been everyone’s number one complaint basically since the first releases under his command.</p>
1041. ]]></content:encoded>
1043. </item>
1044. <item>
1045. <title>
1046. Comment on macOS Tahoe 26 RC by Bart </title>
1047. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305714</link>
1048.  
1049. <dc:creator><![CDATA[Bart]]></dc:creator>
1050. <pubDate>Fri, 12 Sep 2025 16:03:28 +0000</pubDate>
1051. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305714</guid>
1052.  
1053. <description><![CDATA[I can see how people who genuinely care about crafting good software are fucking livid at this release.
1054.  
1055. It does remind me a lot of Vista. Remembering that Vista laid the foundation for Windows 7, everyone’s favorite version ever.
1056.  
1057. Some of these design decisions were dumb and clearly meant to draw attention to the interface. I’ve never had my phone screen so cluttered with shit until they decided to “let my content shine through.”
1058.  
1059. Which apparently means TikTok has succeeded in getting people used to having buttons everywhere all over what they’re trying to see.
1060.  
1061. But, none of my apps broke. Aside from obvious visual interface bugs they’ll fix, it feels snappier and works fine. I just hope this does turn into another Vista and next year’s release is really fine tuned and what users want.
1062.  
1063. At least that keeps hope alive.]]></description>
1064. <content:encoded><![CDATA[<p>I can see how people who genuinely care about crafting good software are fucking livid at this release. </p>
1065. <p>It does remind me a lot of Vista. Remembering that Vista laid the foundation for Windows 7, everyone’s favorite version ever. </p>
1066. <p>Some of these design decisions were dumb and clearly meant to draw attention to the interface. I’ve never had my phone screen so cluttered with shit until they decided to “let my content shine through.” </p>
1067. <p>Which apparently means TikTok has succeeded in getting people used to having buttons everywhere all over what they’re trying to see. </p>
1068. <p>But, none of my apps broke. Aside from obvious visual interface bugs they’ll fix, it feels snappier and works fine. I just hope this does turn into another Vista and next year’s release is really fine tuned and what users want. </p>
1069. <p>At least that keeps hope alive.</p>
1070. ]]></content:encoded>
1072. </item>
1073. <item>
1074. <title>
1075. Comment on Campfire Now Open Source by Bernd von Fintel </title>
1076. <link>https://mjtsai.com/blog/2025/09/11/campfire-now-open-source/#comment-4305614</link>
1077.  
1078. <dc:creator><![CDATA[Bernd von Fintel]]></dc:creator>
1079. <pubDate>Fri, 12 Sep 2025 11:13:03 +0000</pubDate>
1080. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49252#comment-4305614</guid>
1081.  
1082. <description><![CDATA[If you watch the Railsworld keynote, DHH says they made it free in exchange for someone from the community extracting the action web push logic.]]></description>
1083. <content:encoded><![CDATA[<p>If you watch the Railsworld keynote, DHH says they made it free in exchange for someone from the community extracting the action web push logic.</p>
1084. ]]></content:encoded>
1086. </item>
1087. <item>
1088. <title>
1089. Comment on macOS Tahoe 26 RC by Hammer </title>
1090. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305525</link>
1091.  
1092. <dc:creator><![CDATA[Hammer]]></dc:creator>
1093. <pubDate>Fri, 12 Sep 2025 05:58:48 +0000</pubDate>
1094. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305525</guid>
1095.  
1096. <description><![CDATA[@Sparky Context matters.
1097.  
1098. Mac OS X 10.0 was rough, but critical to ship because it followed high-profile failures as Apple neared bankruptcy. Users talked Apple off the ledge from their stupider ideas in the RCs (the giant Apple logo where the notch is now in the menubar and I believe Apple wanted to ship a Finder without Desktop files). The following macOS updates introduced meaningful features and fixes.
1099.  
1100. Compare to today where Apple has tens of billions in cash but only cares about share price and PR. Where Apple puts money into *any* project except their core OSes. Where macOS is now an iOS accessory and revolves around its release schedule.
1101.  
1102. Nobody asked for Liquid Ass or most of the other dumb features and changes, esp recently. Most devs and users just want shit to work. We've been clamoring for it for years now.
1103.  
1104. You're right that they've shipped many show-stopping bugs and that continues to be a problem. They don't learn or care.
1105.  
1106. Apple's process of "your only slight chance to fix a bug is to report it during WWDC or wait another year" gets more retarded by the year. They act like they have 0 resources or time, but it's 0 care or competency. Apple has pipelines for collecting bugs and user feedback and ignores it all.
1107.  
1108. macOS Tahoe is Vista in its purest form (yet).]]></description>
1109. <content:encoded><![CDATA[<p>@Sparky Context matters.</p>
1110. <p>Mac OS X 10.0 was rough, but critical to ship because it followed high-profile failures as Apple neared bankruptcy. Users talked Apple off the ledge from their stupider ideas in the RCs (the giant Apple logo where the notch is now in the menubar and I believe Apple wanted to ship a Finder without Desktop files). The following macOS updates introduced meaningful features and fixes.</p>
1111. <p>Compare to today where Apple has tens of billions in cash but only cares about share price and PR. Where Apple puts money into *any* project except their core OSes. Where macOS is now an iOS accessory and revolves around its release schedule.</p>
1112. <p>Nobody asked for Liquid Ass or most of the other dumb features and changes, esp recently. Most devs and users just want shit to work. We've been clamoring for it for years now.</p>
1113. <p>You're right that they've shipped many show-stopping bugs and that continues to be a problem. They don't learn or care.</p>
1114. <p>Apple's process of "your only slight chance to fix a bug is to report it during WWDC or wait another year" gets more retarded by the year. They act like they have 0 resources or time, but it's 0 care or competency. Apple has pipelines for collecting bugs and user feedback and ignores it all.</p>
1115. <p>macOS Tahoe is Vista in its purest form (yet).</p>
1116. ]]></content:encoded>
1118. </item>
1119. <item>
1120. <title>
1121. Comment on iPhone Air by Bri </title>
1122. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4305467</link>
1123.  
1124. <dc:creator><![CDATA[Bri]]></dc:creator>
1125. <pubDate>Fri, 12 Sep 2025 02:51:57 +0000</pubDate>
1126. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4305467</guid>
1127.  
1128. <description><![CDATA[@Plume Avoid eSIMs like the plague, got it.]]></description>
1129. <content:encoded><![CDATA[<p>@Plume Avoid eSIMs like the plague, got it.</p>
1130. ]]></content:encoded>
1132. </item>
1133. <item>
1134. <title>
1135. Comment on macOS Tahoe 26 RC by Sparky </title>
1136. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305450</link>
1137.  
1138. <dc:creator><![CDATA[Sparky]]></dc:creator>
1139. <pubDate>Fri, 12 Sep 2025 01:11:28 +0000</pubDate>
1140. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305450</guid>
1141.  
1142. <description><![CDATA[@Felipe Pait Multiple things can be true at once.
1143.  
1144. Yes, the influencer-dev crowd shouting from their podcast and social media soapboxes are being overly dramatic.
1145.  
1146. And yes, this release is rough. It probably needed another couple of months in the oven, and Liquid Glass on the Mac in particular feels like it needs a fundamental rethink.
1147.  
1148. But none of this is new. It’s the same story we’ve lived through since Mac OS X 10.0—Cheetah was nowhere near ready for prime time, and Aqua was a disaster zone. Even earlier: I’ve got hazy memories of the chaos around Open Transport. This is just the latest lap in a very old cycle.
1149.  
1150. I can rattle off multiple 2000s and 2010s releases that shipped with show-stopping bugs we’d already reported months earlier, only to see them finally patched in the inevitable .1 update. Back then we’d haul a PowerBook to WWDC, install the new OS Developer Preview on day one from the DVD, and then go track down the engineer responsible to beg for confirmation that the fix was coming.
1151.  
1152. What’s changed isn’t Apple—it’s the noise. Back then, if you wanted to vent, you had developer mailing lists or a WWDC feedback session. It was kept behind closed doors. Now everyone has Mastodon, Threads, Twitter, or whatever, and apparently every single one of them has a podcast where they can sit around congratulating themselves and smelling their own farts.]]></description>
1153. <content:encoded><![CDATA[<p>@Felipe Pait Multiple things can be true at once.</p>
1154. <p>Yes, the influencer-dev crowd shouting from their podcast and social media soapboxes are being overly dramatic.</p>
1155. <p>And yes, this release is rough. It probably needed another couple of months in the oven, and Liquid Glass on the Mac in particular feels like it needs a fundamental rethink.</p>
1156. <p>But none of this is new. It’s the same story we’ve lived through since Mac OS X 10.0—Cheetah was nowhere near ready for prime time, and Aqua was a disaster zone. Even earlier: I’ve got hazy memories of the chaos around Open Transport. This is just the latest lap in a very old cycle.</p>
1157. <p>I can rattle off multiple 2000s and 2010s releases that shipped with show-stopping bugs we’d already reported months earlier, only to see them finally patched in the inevitable .1 update. Back then we’d haul a PowerBook to WWDC, install the new OS Developer Preview on day one from the DVD, and then go track down the engineer responsible to beg for confirmation that the fix was coming.</p>
1158. <p>What’s changed isn’t Apple—it’s the noise. Back then, if you wanted to vent, you had developer mailing lists or a WWDC feedback session. It was kept behind closed doors. Now everyone has Mastodon, Threads, Twitter, or whatever, and apparently every single one of them has a podcast where they can sit around congratulating themselves and smelling their own farts.</p>
1159. ]]></content:encoded>
1161. </item>
1162. <item>
1163. <title>
1164. Comment on macOS Tahoe 26 RC by Hammer </title>
1165. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305443</link>
1166.  
1167. <dc:creator><![CDATA[Hammer]]></dc:creator>
1168. <pubDate>Fri, 12 Sep 2025 00:49:23 +0000</pubDate>
1169. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305443</guid>
1170.  
1171. <description><![CDATA[@ObjC4Life I wish. Compare and contrast how quickly Obj-C Garbage Collection was tried and killed to SwiftUI. They&#039;re sunk-cost fallacied on all things Swift.
1172.  
1173. @Léo Apple's software development and management is deeply broken. How many years has it been where Beta 1 -> RC 1 basically fixes a few obvious bugs, but they built and pushed the wrong solution? How many things do they ship that end up performing exactly for a WWDC demo and quickly fall apart beyond that? They ship it anyway, promote it as great, push a year of multiple +0.1 OS updates, but foundational problems remain. Then next year, onto a new feature rolled out the same way.
1174.  
1175. Software dev has gone from caring and craftsmanship to punching tickets and shipping quickly (even if it&#039;s crap).]]></description>
1176. <content:encoded><![CDATA[<p>@ObjC4Life I wish. Compare and contrast how quickly Obj-C Garbage Collection was tried and killed to SwiftUI. They're sunk-cost fallacied on all things Swift.</p>
1177. <p>@Léo Apple's software development and management is deeply broken. How many years has it been where Beta 1 -&gt; RC 1 basically fixes a few obvious bugs, but they built and pushed the wrong solution? How many things do they ship that end up performing exactly for a WWDC demo and quickly fall apart beyond that? They ship it anyway, promote it as great, push a year of multiple +0.1 OS updates, but foundational problems remain. Then next year, onto a new feature rolled out the same way.</p>
1178. <p>Software dev has gone from caring and craftsmanship to punching tickets and shipping quickly (even if it's crap).</p>
1179. ]]></content:encoded>
1181. </item>
1182. <item>
1183. <title>
1184. Comment on macOS Tahoe 26 RC by Felipe Pait </title>
1185. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305395</link>
1186.  
1187. <dc:creator><![CDATA[Felipe Pait]]></dc:creator>
1188. <pubDate>Thu, 11 Sep 2025 20:48:05 +0000</pubDate>
1189. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305395</guid>
1190.  
1191. <description><![CDATA[Is this specially bad, or do people talk like this every new release?
1192.  
1193. Well, I&#039;m just a user, and year in, year out, the new OS releases just work. Is this time going to be different?]]></description>
1194. <content:encoded><![CDATA[<p>Is this specially bad, or do people talk like this every new release? </p>
1195. <p>Well, I'm just a user, and year in, year out, the new OS releases just work. Is this time going to be different?</p>
1196. ]]></content:encoded>
1198. </item>
1199. <item>
1200. <title>
1201. Comment on Memory Integrity Enforcement by bob </title>
1202. <link>https://mjtsai.com/blog/2025/09/11/memory-integrity-enforcement/#comment-4305394</link>
1203.  
1204. <dc:creator><![CDATA[bob]]></dc:creator>
1205. <pubDate>Thu, 11 Sep 2025 20:48:02 +0000</pubDate>
1206. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49256#comment-4305394</guid>
1207.  
1208. <description><![CDATA[The GrapheneOS team deserve credit for advancing device security state-of-the-art, especially on Android.
1209.  
1210. > Unlike iPhone users, GrapheneOS users have been well protected by attacks from Cellebrite and other exploit development companies.
1211.  
1212. But this current assertion really deserves a citation that uses data newer than July 2024 and covering iOS after 17.5.1. They describe implementing USB connectivity restrictions that iOS has had for a while, and then detail Android-specific vulnerability fixes. What’s the evidence to support declaring that iOS users are vulnerable?]]></description>
1213. <content:encoded><![CDATA[<p>The GrapheneOS team deserve credit for advancing device security state-of-the-art, especially on Android. </p>
1214. <p>&gt; Unlike iPhone users, GrapheneOS users have been well protected by attacks from Cellebrite and other exploit development companies.</p>
1215. <p>But this current assertion really deserves a citation that uses data newer than July 2024 and covering iOS after 17.5.1. They describe implementing USB connectivity restrictions that iOS has had for a while, and then detail Android-specific vulnerability fixes. What’s the evidence to support declaring that iOS users are vulnerable?</p>
1216. ]]></content:encoded>
1218. </item>
1219. <item>
1220. <title>
1221. Comment on macOS Tahoe 26 RC by Kirk McElhearn </title>
1222. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305373</link>
1223.  
1224. <dc:creator><![CDATA[Kirk McElhearn]]></dc:creator>
1225. <pubDate>Thu, 11 Sep 2025 19:16:29 +0000</pubDate>
1226. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305373</guid>
1227.  
1228. <description><![CDATA[I think the worst thing for me - as someone who uses the Music app a lot, and has written books about iTunes and Apple&#039;s media apps - is the playbar at the bottom of the screen. It&#039;s a bad location; it&#039;s not where you expect it to be, it&#039;s too small, if you don&#039;t have Reduce Transparency on it can be hard to see, and it totally unbalances the app&#039;s window, which, on Apple Music pages, for example, has content that scrolls to the very top border of the window.
1229.  
1230. It&#039;s probably the worst interface element ever in iTunes/Music. The previous play header - which Apple has called internally the iTunes LCD - was separated from the rest of the content, making it an easy place to see what was happening. This interface element isn&#039;t as bad on iPhone or iPad, but it certainly is not ideal on the desktop. And the idea that Apple is trying to make it so that everything matches on the three devices is proven terribly wrong by this.]]></description>
1231. <content:encoded><![CDATA[<p>I think the worst thing for me - as someone who uses the Music app a lot, and has written books about iTunes and Apple's media apps - is the playbar at the bottom of the screen. It's a bad location; it's not where you expect it to be, it's too small, if you don't have Reduce Transparency on it can be hard to see, and it totally unbalances the app's window, which, on Apple Music pages, for example, has content that scrolls to the very top border of the window. </p>
1232. <p>It's probably the worst interface element ever in iTunes/Music. The previous play header - which Apple has called internally the iTunes LCD - was separated from the rest of the content, making it an easy place to see what was happening. This interface element isn't as bad on iPhone or iPad, but it certainly is not ideal on the desktop. And the idea that Apple is trying to make it so that everything matches on the three devices is proven terribly wrong by this.</p>
1233. ]]></content:encoded>
1235. </item>
1236. <item>
1237. <title>
1238. Comment on Design Is How It Works by ghill </title>
1239. <link>https://mjtsai.com/blog/2025/09/10/design-is-how-it-works-2/#comment-4305358</link>
1240.  
1241. <dc:creator><![CDATA[ghill]]></dc:creator>
1242. <pubDate>Thu, 11 Sep 2025 18:10:00 +0000</pubDate>
1243. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49230#comment-4305358</guid>
1244.  
1245. <description><![CDATA[@Alexandre Dieulot
1246.  
1247. I know the point of your message is that the quote was there to confront the general sentiment.
1248.  
1249. I also want to point out they had been saying they loved the Mac for years before the Big Sur video when the prevailing public view was that Apple had abandoned the Mac. Every WWDC from 2017 to 2020 had some mention of how much they loved the Mac.
1250.  
1251. The Apple Silicon Mac hardware somehow made everyone stop calling Apple out, and so they don&#039;t feel the need to say that anymore. Yet at the same time the software continues to be left to rot.]]></description>
1252. <content:encoded><![CDATA[<p>@Alexandre Dieulot</p>
1253. <p>I know the point of your message is that the quote was there to confront the general sentiment.</p>
1254. <p>I also want to point out they had been saying they loved the Mac for years before the Big Sur video when the prevailing public view was that Apple had abandoned the Mac. Every WWDC from 2017 to 2020 had some mention of how much they loved the Mac.</p>
1255. <p>The Apple Silicon Mac hardware somehow made everyone stop calling Apple out, and so they don't feel the need to say that anymore. Yet at the same time the software continues to be left to rot.</p>
1256. ]]></content:encoded>
1258. </item>
1259. <item>
1260. <title>
1261. Comment on iPhone Air by Plume </title>
1262. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4305259</link>
1263.  
1264. <dc:creator><![CDATA[Plume]]></dc:creator>
1265. <pubDate>Thu, 11 Sep 2025 12:04:55 +0000</pubDate>
1266. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4305259</guid>
1267.  
1268. <description><![CDATA[As an aside, I absolutely hate eSIMs. I recently picked up a Pixel Fold, and it prompted me to convert my SIM to an eSIM. Stupidly (and curious what would happen), I did so. This disabled my SIM card.
1269.  
1270. Then, the Fold died. Usually, I could just take the SIM out of the phone and move it to another phone, but with an eSIM, this only works if your phone works. So I went to one of my provider's stores, thinking they could give me a new SIM, but no. They could not. I had to order a new one online, which was difficult because the website's 2FA system required me to be able to receive text messages under my original number.
1271.  
1272. In the end, what should have been ten seconds of SIM switching ended up being a week without cell service.]]></description>
1273. <content:encoded><![CDATA[<p>As an aside, I absolutely hate eSIMs. I recently picked up a Pixel Fold, and it prompted me to convert my SIM to an eSIM. Stupidly (and curious what would happen), I did so. This disabled my SIM card.</p>
1274. <p>Then, the Fold died. Usually, I could just take the SIM out of the phone and move it to another phone, but with an eSIM, this only works if your phone works. So I went to one of my provider's stores, thinking they could give me a new SIM, but no. They could not. I had to order a new one online, which was difficult because the website's 2FA system required me to be able to receive text messages under my original number.</p>
1275. <p>In the end, what should have been ten seconds of SIM switching ended up being a week without cell service.</p>
1276. ]]></content:encoded>
1278. </item>
1279. <item>
1280. <title>
1281. Comment on iPhone Air by Plume </title>
1282. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4305255</link>
1283.  
1284. <dc:creator><![CDATA[Plume]]></dc:creator>
1285. <pubDate>Thu, 11 Sep 2025 11:51:11 +0000</pubDate>
1286. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4305255</guid>
1287.  
1288. <description><![CDATA[An unfolded Mate XT is 4mm.]]></description>
1289. <content:encoded><![CDATA[<p>An unfolded Mate XT is 4mm.</p>
1290. ]]></content:encoded>
1292. </item>
1293. <item>
1294. <title>
1295. Comment on macOS Tahoe 26 RC by Duncan </title>
1296. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305206</link>
1297.  
1298. <dc:creator><![CDATA[Duncan]]></dc:creator>
1299. <pubDate>Thu, 11 Sep 2025 09:22:36 +0000</pubDate>
1300. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305206</guid>
1301.  
1302. <description><![CDATA[The approach to release notes shows a lack of respect. If Apple had respect for developers then writing proper release notes would be a blocker in the process of putting out a beta/RC.]]></description>
1303. <content:encoded><![CDATA[<p>The approach to release notes shows a lack of respect. If Apple had respect for developers then writing proper release notes would be a blocker in the process of putting out a beta/RC.</p>
1304. ]]></content:encoded>
1306. </item>
1307. <item>
1308. <title>
1309. Comment on Design Is How It Works by Steve H </title>
1310. <link>https://mjtsai.com/blog/2025/09/10/design-is-how-it-works-2/#comment-4305173</link>
1311.  
1312. <dc:creator><![CDATA[Steve H]]></dc:creator>
1313. <pubDate>Thu, 11 Sep 2025 08:17:39 +0000</pubDate>
1314. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49230#comment-4305173</guid>
1315.  
1316. <description><![CDATA[I saw that opening gambit more like a child who runs into the room to proclaim they did not scribble all over their bedroom wall.
1317.  
1318. Hardware event or not, it was striking that Liquid Glass only got mentioned in passing. Last year they spent months running ads about Apple Intelligence features that hadn’t even shipped, and perhaps some that never will. Liquid Glass, on the other hand, sadly does exist, and I’m sure most of them realise it’s a steaming pile of crap.
1319.  
1320. Redesign your user interface, wrong answers only. Should the sidebar and toolbar buttons appear raised and cast shadows on the content below? Yes! Should Mac app icons be forced into uniform shapes whether they like it or not? The nail that sticks out will be hammered down. Should menus become cluttered with tiny icons, with seemingly broken alignment for those that resist? Serves them right. Should we fade out the last vestiges of window chrome so that mostly textual content can “shine through” our otherwise bland buttons? The refraction is worth the cost. How big should those window corners be? Bigger? Bigger again? How about now? Yes, that’s truly impractical.
1321.  
1322. Apple has changed the way it works, from design and engineering working in tandem to misnomered “creative technologists” and “producers” handing down diktats from above. Management by self-important bozos. It doesn’t work. Sack the lot and get back to reality.]]></description>
1323. <content:encoded><![CDATA[<p>I saw that opening gambit more like a child who runs into the room to proclaim they did not scribble all over their bedroom wall.</p>
1324. <p>Hardware event or not, it was striking that Liquid Glass only got mentioned in passing. Last year they spent months running ads about Apple Intelligence features that hadn’t even shipped, and perhaps some that never will. Liquid Glass, on the other hand, sadly does exist, and I’m sure most of them realise it’s a steaming pile of crap.</p>
1325. <p>Redesign your user interface, wrong answers only. Should the sidebar and toolbar buttons appear raised and cast shadows on the content below? Yes! Should Mac app icons be forced into uniform shapes whether they like it or not? The nail that sticks out will be hammered down. Should menus become cluttered with tiny icons, with seemingly broken alignment for those that resist? Serves them right. Should we fade out the last vestiges of window chrome so that mostly textual content can “shine through” our otherwise bland buttons? The refraction is worth the cost. How big should those window corners be? Bigger? Bigger again? How about now? Yes, that’s truly impractical.</p>
1326. <p>Apple has changed the way it works, from design and engineering working in tandem to misnomered “creative technologists” and “producers” handing down diktats from above. Management by self-important bozos. It doesn’t work. Sack the lot and get back to reality.</p>
1327. ]]></content:encoded>
1329. </item>
1330. <item>
1331. <title>
1332. Comment on Design Is How It Works by Alexandre Dieulot </title>
1333. <link>https://mjtsai.com/blog/2025/09/10/design-is-how-it-works-2/#comment-4305158</link>
1334.  
1335. <dc:creator><![CDATA[Alexandre Dieulot]]></dc:creator>
1336. <pubDate>Thu, 11 Sep 2025 07:38:00 +0000</pubDate>
1337. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49230#comment-4305158</guid>
1338.  
1339. <description><![CDATA[Alan Dye similarly said &quot;We love the Mac&quot; in Big Sur&#039;s introduction video, which normally wouldn&#039;t need saying. It flew naturally with the rest of his speech so it didn&#039;t raise eyebrows.
1340.  
1341. That quote is spin to counteract the public&#039;s view that their redesign is too much about looks. That public view is relatively loud, so they spinned loudly.]]></description>
1342. <content:encoded><![CDATA[<p>Alan Dye similarly said "We love the Mac" in Big Sur's introduction video, which normally wouldn't need saying. It flew naturally with the rest of his speech so it didn't raise eyebrows.</p>
1343. <p>That quote is spin to counteract the public's view that their redesign is too much about looks. That public view is relatively loud, so they spinned loudly.</p>
1344. ]]></content:encoded>
1346. </item>
1347. <item>
1348. <title>
1349. Comment on uBlock Origin Lite for Safari by Alexandre Dieulot </title>
1350. <link>https://mjtsai.com/blog/2025/08/06/ublock-origin-lite-for-safari/#comment-4305145</link>
1351.  
1352. <dc:creator><![CDATA[Alexandre Dieulot]]></dc:creator>
1353. <pubDate>Thu, 11 Sep 2025 06:17:26 +0000</pubDate>
1354. <guid isPermaLink="false">https://mjtsai.com/blog/?p=48800#comment-4305145</guid>
1355.  
1356. <description><![CDATA[It never works in private navigation on my Mac, even though that option is checked. Unbelievable.]]></description>
1357. <content:encoded><![CDATA[<p>It never works in private navigation on my Mac, even though that option is checked. Unbelievable.</p>
1358. ]]></content:encoded>
1360. </item>
1361. <item>
1362. <title>
1363. Comment on Design Is How It Works by josehill </title>
1364. <link>https://mjtsai.com/blog/2025/09/10/design-is-how-it-works-2/#comment-4305119</link>
1365.  
1366. <dc:creator><![CDATA[josehill]]></dc:creator>
1367. <pubDate>Thu, 11 Sep 2025 05:00:54 +0000</pubDate>
1368. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49230#comment-4305119</guid>
1369.  
1370. <description><![CDATA[I think the only explanation for that opening quote is, as the British say, that someone is &quot;taking the piss&quot;. The question is who is the target?]]></description>
1371. <content:encoded><![CDATA[<p>I think the only explanation for that opening quote is, as the British say, that someone is "taking the piss". The question is who is the target?</p>
1372. ]]></content:encoded>
1374. </item>
1375. <item>
1376. <title>
1377. Comment on Design Is How It Works by Mayson Lancaster </title>
1378. <link>https://mjtsai.com/blog/2025/09/10/design-is-how-it-works-2/#comment-4305112</link>
1379.  
1380. <dc:creator><![CDATA[Mayson Lancaster]]></dc:creator>
1381. <pubDate>Thu, 11 Sep 2025 04:33:21 +0000</pubDate>
1382. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49230#comment-4305112</guid>
1383.  
1384. <description><![CDATA[Was that the first public shot fired in an internecine struggle between Alan Dye and those who understand that quote? One can hope.]]></description>
1385. <content:encoded><![CDATA[<p>Was that the first public shot fired in an internecine struggle between Alan Dye and those who understand that quote? One can hope.</p>
1386. ]]></content:encoded>
1388. </item>
1389. <item>
1390. <title>
1391. Comment on Apple Watch SE 3 by Bri </title>
1392. <link>https://mjtsai.com/blog/2025/09/09/apple-watch-se-3/#comment-4305092</link>
1393.  
1394. <dc:creator><![CDATA[Bri]]></dc:creator>
1395. <pubDate>Thu, 11 Sep 2025 03:41:21 +0000</pubDate>
1396. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49202#comment-4305092</guid>
1397.  
1398. <description><![CDATA[Still twenty seven more models to go before we finally get the Apple Watch SE/30.]]></description>
1399. <content:encoded><![CDATA[<p>Still twenty seven more models to go before we finally get the Apple Watch SE/30.</p>
1400. ]]></content:encoded>
1402. </item>
1403. <item>
1404. <title>
1405. Comment on macOS Tahoe 26 RC by Léo Natan </title>
1406. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305065</link>
1407.  
1408. <dc:creator><![CDATA[Léo Natan]]></dc:creator>
1409. <pubDate>Thu, 11 Sep 2025 01:52:02 +0000</pubDate>
1410. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305065</guid>
1411.  
1412. <description><![CDATA[@ObjC4Life I laugh at people using SwiftUI and getting surprised every year how bad it is, then double down because *THIS YEAR IT’S FINALLY GETTING GREAT BABY* <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;" />
1413.  
1414. The sad thing is, that, at least on UIKit, they seem to have filled the old framework with Swift and SwiftUI now, and, you guessed it, the parts they touched are the hottest of messes. It’s like a vicious cycle (more like a maelstrom turning into a cyclone by the year); terrible language + terrible framework + terrible tooling + incompetent engineering + incompetent and apathetic management + rabid fanboys that will buy anything Apple regardless of quality. There is no turning this shitshow around anymore.]]></description>
1415. <content:encoded><![CDATA[<p>@ObjC4Life I laugh at people using SwiftUI and getting surprised every year how bad it is, then double down because *THIS YEAR IT’S FINALLY GETTING GREAT BABY* 🤦‍♂️</p>
1416. <p>The sad thing is, that, at least on UIKit, they seem to have filled the old framework with Swift and SwiftUI now, and, you guessed it, the parts they touched are the hottest of messes. It’s like a vicious cycle (more like a maelstrom turning into a cyclone by the year); terrible language + terrible framework + terrible tooling + incompetent engineering + incompetent and apathetic management + rabid fanboys that will buy anything Apple regardless of quality. There is no turning this shitshow around anymore.</p>
1417. ]]></content:encoded>
1419. </item>
1420. <item>
1421. <title>
1422. Comment on Mac Layout Guidelines by ObjC4Life </title>
1423. <link>https://mjtsai.com/blog/2025/09/08/mac-layout-guidelines/#comment-4305051</link>
1424.  
1425. <dc:creator><![CDATA[ObjC4Life]]></dc:creator>
1426. <pubDate>Wed, 10 Sep 2025 23:52:15 +0000</pubDate>
1427. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49184#comment-4305051</guid>
1428.  
1429. <description><![CDATA[Good post. Nice to see windows without an absurd amount of padding.]]></description>
1430. <content:encoded><![CDATA[<p>Good post. Nice to see windows without an absurd amount of padding.</p>
1431. ]]></content:encoded>
1433. </item>
1434. <item>
1435. <title>
1436. Comment on macOS Tahoe 26 RC by ObjC4Life </title>
1437. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305040</link>
1438.  
1439. <dc:creator><![CDATA[ObjC4Life]]></dc:creator>
1440. <pubDate>Wed, 10 Sep 2025 22:49:52 +0000</pubDate>
1441. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305040</guid>
1442.  
1443. <description><![CDATA[&#062; just yesterday, I had a laugh at how SwiftUI layout is broken on macOS 26, in entirely new ways. But I assumed they still have few months to fix it.
1444.  
1445.  
1446. I heard this story last year…and the year before…and the year before…and the year before.
1447.  
1448. Maybe they’ll nail it down next year though right? How many more years are we going to give them? How about everyone just use Appkit and tell Apple no? SwiftUI should be deprecated. It’s a failed experiment, stop the fucking bleeding already]]></description>
1449. <content:encoded><![CDATA[<p>&gt; just yesterday, I had a laugh at how SwiftUI layout is broken on macOS 26, in entirely new ways. But I assumed they still have few months to fix it.</p>
1450. <p>I heard this story last year…and the year before…and the year before…and the year before.</p>
1451. <p>Maybe they’ll nail it down next year though right? How many more years are we going to give them? How about everyone just use Appkit and tell Apple no? SwiftUI should be deprecated. It’s a failed experiment, stop the fucking bleeding already</p>
1452. ]]></content:encoded>
1454. </item>
1455. <item>
1456. <title>
1457. Comment on Design Is How It Works by Bart </title>
1458. <link>https://mjtsai.com/blog/2025/09/10/design-is-how-it-works-2/#comment-4305035</link>
1459.  
1460. <dc:creator><![CDATA[Bart]]></dc:creator>
1461. <pubDate>Wed, 10 Sep 2025 22:18:29 +0000</pubDate>
1462. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49230#comment-4305035</guid>
1463.  
1464. <description><![CDATA[I did laugh bitterly at reading that. Glad I’m not the only one who thought that it was a bold and tasteless move.
1465.  
1466. The thing is, right after the quote they showed many physical items that are actually pretty good. So in that sense it was appropriate.
1467.  
1468. But of course we all know the problem with the iPhone and Mac anymore, it’s the software. That, and Apple’s complete tone deafness. So in that way it was ironically appropriate.]]></description>
1469. <content:encoded><![CDATA[<p>I did laugh bitterly at reading that. Glad I’m not the only one who thought that it was a bold and tasteless move. </p>
1470. <p>The thing is, right after the quote they showed many physical items that are actually pretty good. So in that sense it was appropriate. </p>
1471. <p>But of course we all know the problem with the iPhone and Mac anymore, it’s the software. That, and Apple’s complete tone deafness. So in that way it was ironically appropriate.</p>
1472. ]]></content:encoded>
1474. </item>
1475. <item>
1476. <title>
1477. Comment on macOS Tahoe 26 RC by Bart </title>
1478. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305021</link>
1479.  
1480. <dc:creator><![CDATA[Bart]]></dc:creator>
1481. <pubDate>Wed, 10 Sep 2025 21:32:47 +0000</pubDate>
1482. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305021</guid>
1483.  
1484. <description><![CDATA[Unpopular opinion. I gotta say, despite my reluctance I took the plunge and I don’t hate it.
1485.  
1486. Thing is, the bar was already pretty low. I’ve gotten used to weird behavior and inconsistency and bugs just like on Windows, so it’s not like what I had was perfect.
1487.  
1488. None of my apps broke, in fact a lot of the most important ones RC day one updates specifically to support it, even some that hadn’t been updated in a while.
1489.  
1490. It probably was not fun for developers but they seem to have managed to ship something that works at least as well as macOS does.
1491.  
1492. It’s about as buggy as any RC/.0 release, actually made some improvements, didn’t break anything. It’s a lot more annoying on the phone actually.]]></description>
1493. <content:encoded><![CDATA[<p>Unpopular opinion. I gotta say, despite my reluctance I took the plunge and I don’t hate it. </p>
1494. <p>Thing is, the bar was already pretty low. I’ve gotten used to weird behavior and inconsistency and bugs just like on Windows, so it’s not like what I had was perfect. </p>
1495. <p>None of my apps broke, in fact a lot of the most important ones RC day one updates specifically to support it, even some that hadn’t been updated in a while. </p>
1496. <p>It probably was not fun for developers but they seem to have managed to ship something that works at least as well as macOS does. </p>
1497. <p>It’s about as buggy as any RC/.0 release, actually made some improvements, didn’t break anything. It’s a lot more annoying on the phone actually.</p>
1498. ]]></content:encoded>
1500. </item>
1501. <item>
1502. <title>
1503. Comment on macOS Tahoe 26 RC by bob </title>
1504. <link>https://mjtsai.com/blog/2025/09/10/macos-tahoe-26-rc/#comment-4305010</link>
1505.  
1506. <dc:creator><![CDATA[bob]]></dc:creator>
1507. <pubDate>Wed, 10 Sep 2025 20:56:26 +0000</pubDate>
1508. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49236#comment-4305010</guid>
1509.  
1510. <description><![CDATA[Guzmán’s approach is correct: stop developing for Apple’s platforms. Develop for the open web or linux/bsd.]]></description>
1511. <content:encoded><![CDATA[<p>Guzmán’s approach is correct: stop developing for Apple’s platforms. Develop for the open web or linux/bsd.</p>
1512. ]]></content:encoded>
1514. </item>
1515. <item>
1516. <title>
1517. Comment on Design Is How It Works by Tarsier </title>
1518. <link>https://mjtsai.com/blog/2025/09/10/design-is-how-it-works-2/#comment-4304999</link>
1519.  
1520. <dc:creator><![CDATA[Tarsier]]></dc:creator>
1521. <pubDate>Wed, 10 Sep 2025 20:09:05 +0000</pubDate>
1522. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49230#comment-4304999</guid>
1523.  
1524. <description><![CDATA[The event was without a doubt cut short: there were at least a couple of rough cuts during which the speakers’ pacing and intonation implied that more was coming.
1525.  
1526. I doubt they would have cut half an hour of UI demos, but I do feel some of the Watch and eSIM feature presentations were shortened at the eleventh hour, with no time to re-record the speakers, or even dub them.]]></description>
1527. <content:encoded><![CDATA[<p>The event was without a doubt cut short: there were at least a couple of rough cuts during which the speakers’ pacing and intonation implied that more was coming.</p>
1528. <p>I doubt they would have cut half an hour of UI demos, but I do feel some of the Watch and eSIM feature presentations were shortened at the eleventh hour, with no time to re-record the speakers, or even dub them.</p>
1529. ]]></content:encoded>
1531. </item>
1532. <item>
1533. <title>
1534. Comment on iPhone 17 Pro and iPhone 17 Pro Max by nilrog </title>
1535. <link>https://mjtsai.com/blog/2025/09/09/iphone-17-pro-and-iphone-17-pro-max/#comment-4304991</link>
1536.  
1537. <dc:creator><![CDATA[nilrog]]></dc:creator>
1538. <pubDate>Wed, 10 Sep 2025 19:47:16 +0000</pubDate>
1539. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49214#comment-4304991</guid>
1540.  
1541. <description><![CDATA[The new iPhone 17 Pro looks amazing in orange. And it would be a nice upgrade from my 13 Pro. But the whole iOS 26 &quot;liquid glass&quot; saga that I have been following is putting me off from buying one. I am not a developer anymore, and I do not run beta&#039;s on my iPhone, so I have no first hand experience. I only go by what I have read everywhere about the state of the iOS 26 beta&#039;s. But if Apple cannot even spend a lot of time showing it and convincing us how it will also be great for accessibility etc., then it is a no-go for me for now. If/when they can shape it up like they did with iOS 7 after its &quot;bleak&quot; launch, then I might opt to buy one. But I fear that iPhone 18 will be (near) release by then.]]></description>
1542. <content:encoded><![CDATA[<p>The new iPhone 17 Pro looks amazing in orange. And it would be a nice upgrade from my 13 Pro. But the whole iOS 26 "liquid glass" saga that I have been following is putting me off from buying one. I am not a developer anymore, and I do not run beta's on my iPhone, so I have no first hand experience. I only go by what I have read everywhere about the state of the iOS 26 beta's. But if Apple cannot even spend a lot of time showing it and convincing us how it will also be great for accessibility etc., then it is a no-go for me for now. If/when they can shape it up like they did with iOS 7 after its "bleak" launch, then I might opt to buy one. But I fear that iPhone 18 will be (near) release by then.</p>
1543. ]]></content:encoded>
1545. </item>
1546. <item>
1547. <title>
1548. Comment on Design Is How It Works by Marcos </title>
1549. <link>https://mjtsai.com/blog/2025/09/10/design-is-how-it-works-2/#comment-4304986</link>
1550.  
1551. <dc:creator><![CDATA[Marcos]]></dc:creator>
1552. <pubDate>Wed, 10 Sep 2025 19:25:21 +0000</pubDate>
1553. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49230#comment-4304986</guid>
1554.  
1555. <description><![CDATA[LOL, they really really aren&#039;t reading the room.]]></description>
1556. <content:encoded><![CDATA[<p>LOL, they really really aren't reading the room.</p>
1557. ]]></content:encoded>
1559. </item>
1560. <item>
1561. <title>
1562. Comment on One Size Does Not Fit All by gildarts </title>
1563. <link>https://mjtsai.com/blog/2025/09/05/one-size-does-not-fit-all/#comment-4304953</link>
1564.  
1565. <dc:creator><![CDATA[gildarts]]></dc:creator>
1566. <pubDate>Wed, 10 Sep 2025 17:08:15 +0000</pubDate>
1567. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49167#comment-4304953</guid>
1568.  
1569. <description><![CDATA[@Bri: have you looked at dhh’s Omarchy project? It is a highly opinionated Linux setup that is really nice. Not sure it is for me, it uses a tiling window manager, but it worth checking out.]]></description>
1570. <content:encoded><![CDATA[<p>@Bri: have you looked at dhh’s Omarchy project? It is a highly opinionated Linux setup that is really nice. Not sure it is for me, it uses a tiling window manager, but it worth checking out.</p>
1571. ]]></content:encoded>
1573. </item>
1574. <item>
1575. <title>
1576. Comment on iPhone 17 Pro and iPhone 17 Pro Max by gildarts </title>
1577. <link>https://mjtsai.com/blog/2025/09/09/iphone-17-pro-and-iphone-17-pro-max/#comment-4304951</link>
1578.  
1579. <dc:creator><![CDATA[gildarts]]></dc:creator>
1580. <pubDate>Wed, 10 Sep 2025 17:04:02 +0000</pubDate>
1581. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49214#comment-4304951</guid>
1582.  
1583. <description><![CDATA[As much as I’d like to get the better cooling and cameras, iOS 26 is a total no go at this point.]]></description>
1584. <content:encoded><![CDATA[<p>As much as I’d like to get the better cooling and cameras, iOS 26 is a total no go at this point.</p>
1585. ]]></content:encoded>
1587. </item>
1588. <item>
1589. <title>
1590. Comment on iPhone Air by Doodpants </title>
1591. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4304943</link>
1592.  
1593. <dc:creator><![CDATA[Doodpants]]></dc:creator>
1594. <pubDate>Wed, 10 Sep 2025 16:37:15 +0000</pubDate>
1595. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4304943</guid>
1596.  
1597. <description><![CDATA[They introduced the &quot;camera plateau&quot; after already having the &quot;dynamic island&quot;; I wonder how many more geographical features future iPhones will have?]]></description>
1598. <content:encoded><![CDATA[<p>They introduced the "camera plateau" after already having the "dynamic island"; I wonder how many more geographical features future iPhones will have?</p>
1599. ]]></content:encoded>
1601. </item>
1602. <item>
1603. <title>
1604. Comment on iPhone Air by vintner </title>
1605. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4304900</link>
1606.  
1607. <dc:creator><![CDATA[vintner]]></dc:creator>
1608. <pubDate>Wed, 10 Sep 2025 14:37:51 +0000</pubDate>
1609. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4304900</guid>
1610.  
1611. <description><![CDATA[Other phones have &quot;camera bumps,&quot; but only Apple could make the &quot;camera plateau.&quot;]]></description>
1612. <content:encoded><![CDATA[<p>Other phones have "camera bumps," but only Apple could make the "camera plateau."</p>
1613. ]]></content:encoded>
1615. </item>
1616. <item>
1617. <title>
1618. Comment on iPhone Air by Hardik Panjwani </title>
1619. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4304883</link>
1620.  
1621. <dc:creator><![CDATA[Hardik Panjwani]]></dc:creator>
1622. <pubDate>Wed, 10 Sep 2025 13:24:06 +0000</pubDate>
1623. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4304883</guid>
1624.  
1625. <description><![CDATA[Another thought. To make the Air stand out even more, it should have been port less. Maybe that will happen in a future version.]]></description>
1626. <content:encoded><![CDATA[<p>Another thought. To make the Air stand out even more, it should have been port less. Maybe that will happen in a future version.</p>
1627. ]]></content:encoded>
1629. </item>
1630. <item>
1631. <title>
1632. Comment on Apple Watch SE 3 by Léo Natan </title>
1633. <link>https://mjtsai.com/blog/2025/09/09/apple-watch-se-3/#comment-4304877</link>
1634.  
1635. <dc:creator><![CDATA[Léo Natan]]></dc:creator>
1636. <pubDate>Wed, 10 Sep 2025 13:04:31 +0000</pubDate>
1637. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49202#comment-4304877</guid>
1638.  
1639. <description><![CDATA[Unfortunately, they require iOS 26 to set up, so not compelling at all.]]></description>
1640. <content:encoded><![CDATA[<p>Unfortunately, they require iOS 26 to set up, so not compelling at all.</p>
1641. ]]></content:encoded>
1643. </item>
1644. <item>
1645. <title>
1646. Comment on iPhone 17 Pro and iPhone 17 Pro Max by Léo Natan </title>
1647. <link>https://mjtsai.com/blog/2025/09/09/iphone-17-pro-and-iphone-17-pro-max/#comment-4304875</link>
1648.  
1649. <dc:creator><![CDATA[Léo Natan]]></dc:creator>
1650. <pubDate>Wed, 10 Sep 2025 12:57:17 +0000</pubDate>
1651. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49214#comment-4304875</guid>
1652.  
1653. <description><![CDATA[@foobat I did the same on the iPad, and two days later, I reverted back. The smaller the screen, the more tolerable it is. The watch has almost no change; the phone is bad but tolerable, iPad is hilariously bad, especially the new windowing stuff; macOS is an atrocity. I’m not updating either. For my open sources, I have an old iPhone 14 Pro Max, which will serve as the dev device. I am seriously considering Android at this point.]]></description>
1654. <content:encoded><![CDATA[<p>@foobat I did the same on the iPad, and two days later, I reverted back. The smaller the screen, the more tolerable it is. The watch has almost no change; the phone is bad but tolerable, iPad is hilariously bad, especially the new windowing stuff; macOS is an atrocity. I’m not updating either. For my open sources, I have an old iPhone 14 Pro Max, which will serve as the dev device. I am seriously considering Android at this point.</p>
1655. ]]></content:encoded>
1657. </item>
1658. <item>
1659. <title>
1660. Comment on iPhone Air by Michael Tsai </title>
1661. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4304871</link>
1662.  
1663. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
1664. <pubDate>Wed, 10 Sep 2025 12:49:37 +0000</pubDate>
1665. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4304871</guid>
1666.  
1667. <description><![CDATA[It seems to me that Apple’s official measurements are &lt;a href=&quot;https://www.apple.com/iphone-air/specs/&quot; rel=&quot;nofollow ugc&quot;&gt;5.64mm for the iPhone Air&lt;/a&gt; and &lt;a href=&quot;https://support.apple.com/en-us/111954&quot; rel=&quot;nofollow ugc&quot;&gt;6.9mm for the iPhone 6&lt;/a&gt; but that for the iPhone 6 they are &lt;em&gt;including&lt;/em&gt; the protruding camera (which is quite small) and for the iPhone Air they are measuring the thinnest part (even though the plateau is rather large).]]></description>
1668. <content:encoded><![CDATA[<p>It seems to me that Apple’s official measurements are <a href="https://www.apple.com/iphone-air/specs/" rel="nofollow ugc">5.64mm for the iPhone Air</a> and <a href="https://support.apple.com/en-us/111954" rel="nofollow ugc">6.9mm for the iPhone 6</a> but that for the iPhone 6 they are <em>including</em> the protruding camera (which is quite small) and for the iPhone Air they are measuring the thinnest part (even though the plateau is rather large).</p>
1669. ]]></content:encoded>
1671. </item>
1672. <item>
1673. <title>
1674. Comment on iPhone Air by Hardik Panjwani </title>
1675. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4304868</link>
1676.  
1677. <dc:creator><![CDATA[Hardik Panjwani]]></dc:creator>
1678. <pubDate>Wed, 10 Sep 2025 12:42:39 +0000</pubDate>
1679. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4304868</guid>
1680.  
1681. <description><![CDATA[Given how tightly packed its components are, I imagine the Air is an experiment to improve future devices, including the Vision Pro. Selling it is just an attempt to recover some of the research cost.
1682.  
1683. As people on social media have noted (and Scott above too), the body of the Air is as thin as years old iPhone 6. This is only possible as everything expect the battery is packed into the plateau. I expect the plateau to become smaller as time goes on and components are miniaturised further. Eventually this knowledge will improve other devices, especially the Vision Pro.
1684.  
1685. Apple being Apple, will market the hell out of the thinness as if it’s a new breakthrough. But the actual breakthrough is the plateau.]]></description>
1686. <content:encoded><![CDATA[<p>Given how tightly packed its components are, I imagine the Air is an experiment to improve future devices, including the Vision Pro. Selling it is just an attempt to recover some of the research cost.</p>
1687. <p>As people on social media have noted (and Scott above too), the body of the Air is as thin as years old iPhone 6. This is only possible as everything expect the battery is packed into the plateau. I expect the plateau to become smaller as time goes on and components are miniaturised further. Eventually this knowledge will improve other devices, especially the Vision Pro.</p>
1688. <p>Apple being Apple, will market the hell out of the thinness as if it’s a new breakthrough. But the actual breakthrough is the plateau.</p>
1689. ]]></content:encoded>
1691. </item>
1692. <item>
1693. <title>
1694. Comment on iPhone Air by Scott </title>
1695. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4304849</link>
1696.  
1697. <dc:creator><![CDATA[Scott]]></dc:creator>
1698. <pubDate>Wed, 10 Sep 2025 10:56:25 +0000</pubDate>
1699. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4304849</guid>
1700.  
1701. <description><![CDATA[Not that any of them care, but I’m putting out there right now: I’m going to be harshly judging any Apple tech pundit who uncritically parrots Apple’s “5.6mm thin” nonsense. I saw a photo on X where somebody at the event slapped an iPhone 6 down next to the Air, Apple’s marketing is pretty obviously deceptive for anyone with more than 3 brain cells. Attempting a Jedi mind trick over the camera ‘plateau’ on a device supposed to easily slip into a front pocket is asinine. Give me back my mini! I am wanting to buy a phone with a camera not a camera that can make calls.]]></description>
1702. <content:encoded><![CDATA[<p>Not that any of them care, but I’m putting out there right now: I’m going to be harshly judging any Apple tech pundit who uncritically parrots Apple’s “5.6mm thin” nonsense. I saw a photo on X where somebody at the event slapped an iPhone 6 down next to the Air, Apple’s marketing is pretty obviously deceptive for anyone with more than 3 brain cells. Attempting a Jedi mind trick over the camera ‘plateau’ on a device supposed to easily slip into a front pocket is asinine. Give me back my mini! I am wanting to buy a phone with a camera not a camera that can make calls.</p>
1703. ]]></content:encoded>
1705. </item>
1706. <item>
1707. <title>
1708. Comment on Apple Watch SE 3 by Hardik Panjwani </title>
1709. <link>https://mjtsai.com/blog/2025/09/09/apple-watch-se-3/#comment-4304805</link>
1710.  
1711. <dc:creator><![CDATA[Hardik Panjwani]]></dc:creator>
1712. <pubDate>Wed, 10 Sep 2025 08:26:38 +0000</pubDate>
1713. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49202#comment-4304805</guid>
1714.  
1715. <description><![CDATA[Yup, this seemed the only compelling purchase. I can live without the rest for now.]]></description>
1716. <content:encoded><![CDATA[<p>Yup, this seemed the only compelling purchase. I can live without the rest for now.</p>
1717. ]]></content:encoded>
1719. </item>
1720. <item>
1721. <title>
1722. Comment on macOS Tahoe Beta Forces Sharing FileVault Key by Saagar Jha </title>
1723. <link>https://mjtsai.com/blog/2025/06/24/macos-tahoe-beta-forces-sharing-filevault-key/#comment-4304787</link>
1724.  
1725. <dc:creator><![CDATA[Saagar Jha]]></dc:creator>
1726. <pubDate>Wed, 10 Sep 2025 07:15:57 +0000</pubDate>
1727. <guid isPermaLink="false">https://mjtsai.com/blog/?p=48214#comment-4304787</guid>
1728.  
1729. <description><![CDATA[You can, actually. See https://bsky.app/profile/alex.zenla.io/post/3lwpuw7zvws2k]]></description>
1730. <content:encoded><![CDATA[<p>You can, actually. See <a href="https://bsky.app/profile/alex.zenla.io/post/3lwpuw7zvws2k" rel="nofollow ugc">https://bsky.app/profile/alex.zenla.io/post/3lwpuw7zvws2k</a></p>
1731. ]]></content:encoded>
1733. </item>
1734. <item>
1735. <title>
1736. Comment on iPhone 17 Pro and iPhone 17 Pro Max by foobat </title>
1737. <link>https://mjtsai.com/blog/2025/09/09/iphone-17-pro-and-iphone-17-pro-max/#comment-4304736</link>
1738.  
1739. <dc:creator><![CDATA[foobat]]></dc:creator>
1740. <pubDate>Wed, 10 Sep 2025 03:29:18 +0000</pubDate>
1741. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49214#comment-4304736</guid>
1742.  
1743. <description><![CDATA[@someone
1744.  
1745. Exactly. I have an 11 Pro ... it drags, the battery has aged, etc. Time for an upgrade! Look at the orange phone! The plateau! Insane cameras (remember, mine is an  11 Pro ... from 2019)!
1746.  
1747. Alas, fuck Liquid Glass. Hard pass. No new devices until that garbage can be turned off without sacrificing &quot;cool&quot;. I tried the beta and hated it instantly and deeply. I wrote a feedback with two home screen screenshots: one from iOS 18 and one from iOS 26. I use  dark mode exclusively with hidden labels and widgets that have a black image in the stack. Once I&#039;m at home, this is the focus mode. Only a few folders of essentials present, the widgets are there but with the black image, the disappear, literally faded into the background. Dark, plain, unobtrusive, simple, dare I say elegant. Except Liquid Glass adds a highlight tweak wrapping all app icons and widgets. It cannot be turned off. It is not dark enough for dark mode, and there are outlines on the widgets ... I lasted less than 48 hours before I wiped my phone and installed the back up. Almost all of the press shot and reviews deal with liquid glass in light mode. Maybe it looks cool, but it it not functional. Liquid glass makes things harder to read. It feels like cool won over accessibility, again (hello fugly Settings). If someone tried to give me a free iPhone 17 in exchange for my 11, I wouldn&#039;t do it, the OS is that bad, that frustrating to use.]]></description>
1748. <content:encoded><![CDATA[<p>@someone</p>
1749. <p>Exactly. I have an 11 Pro ... it drags, the battery has aged, etc. Time for an upgrade! Look at the orange phone! The plateau! Insane cameras (remember, mine is an  11 Pro ... from 2019)! </p>
1750. <p>Alas, fuck Liquid Glass. Hard pass. No new devices until that garbage can be turned off without sacrificing "cool". I tried the beta and hated it instantly and deeply. I wrote a feedback with two home screen screenshots: one from iOS 18 and one from iOS 26. I use  dark mode exclusively with hidden labels and widgets that have a black image in the stack. Once I'm at home, this is the focus mode. Only a few folders of essentials present, the widgets are there but with the black image, the disappear, literally faded into the background. Dark, plain, unobtrusive, simple, dare I say elegant. Except Liquid Glass adds a highlight tweak wrapping all app icons and widgets. It cannot be turned off. It is not dark enough for dark mode, and there are outlines on the widgets ... I lasted less than 48 hours before I wiped my phone and installed the back up. Almost all of the press shot and reviews deal with liquid glass in light mode. Maybe it looks cool, but it it not functional. Liquid glass makes things harder to read. It feels like cool won over accessibility, again (hello fugly Settings). If someone tried to give me a free iPhone 17 in exchange for my 11, I wouldn't do it, the OS is that bad, that frustrating to use.</p>
1751. ]]></content:encoded>
1753. </item>
1754. <item>
1755. <title>
1756. Comment on iPhone Air by Bart </title>
1757. <link>https://mjtsai.com/blog/2025/09/09/iphone-air/#comment-4304717</link>
1758.  
1759. <dc:creator><![CDATA[Bart]]></dc:creator>
1760. <pubDate>Wed, 10 Sep 2025 02:28:33 +0000</pubDate>
1761. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49212#comment-4304717</guid>
1762.  
1763. <description><![CDATA[I gotta say I am way more impressed by this than I expected to be. I still think heat might be a problem but I really like what they are going for.]]></description>
1764. <content:encoded><![CDATA[<p>I gotta say I am way more impressed by this than I expected to be. I still think heat might be a problem but I really like what they are going for.</p>
1765. ]]></content:encoded>
1767. </item>
1768. <item>
1769. <title>
1770. Comment on iPhone 17 Pro and iPhone 17 Pro Max by modulusshift </title>
1771. <link>https://mjtsai.com/blog/2025/09/09/iphone-17-pro-and-iphone-17-pro-max/#comment-4304631</link>
1772.  
1773. <dc:creator><![CDATA[modulusshift]]></dc:creator>
1774. <pubDate>Tue, 09 Sep 2025 22:00:48 +0000</pubDate>
1775. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49214#comment-4304631</guid>
1776.  
1777. <description><![CDATA[I wonder if the A19 Pro in the Air is underclocked compared to the Pros. A very effective power-saving technique is to run a big chip slow rather than a small chip fast. though maybe that only makes sense for sustained workloads and not bursty ones like on the phones. I am fascinated by the Air&#039;s potential gaming performance though, and whether it will eat through the entire battery in like an hour running at 120Hz]]></description>
1778. <content:encoded><![CDATA[<p>I wonder if the A19 Pro in the Air is underclocked compared to the Pros. A very effective power-saving technique is to run a big chip slow rather than a small chip fast. though maybe that only makes sense for sustained workloads and not bursty ones like on the phones. I am fascinated by the Air's potential gaming performance though, and whether it will eat through the entire battery in like an hour running at 120Hz</p>
1779. ]]></content:encoded>
1781. </item>
1782. <item>
1783. <title>
1784. Comment on One Size Does Not Fit All by Michael Tsai </title>
1785. <link>https://mjtsai.com/blog/2025/09/05/one-size-does-not-fit-all/#comment-4304627</link>
1786.  
1787. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
1788. <pubDate>Tue, 09 Sep 2025 21:55:53 +0000</pubDate>
1789. <guid isPermaLink="false">https://mjtsai.com/blog/?p=49167#comment-4304627</guid>
1790.  
1791. <description><![CDATA[@ObjC4Life Sounds like a reasonable plan. FYI, snatching it out of DerivedData is not good because Xcode only generates it up to 256px.]]></description>
1792. <content:encoded><![CDATA[<p>@ObjC4Life Sounds like a reasonable plan. FYI, snatching it out of DerivedData is not good because Xcode only generates it up to 256px.</p>
1793. ]]></content:encoded>
1795. </item>
1796. </channel>
1797. </rss>
1798.  

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):

   <a href="http://www.feedvalidator.org/check.cgi?url=http%3A//mjtsai.com/blog/comments/feed/"><img src="valid-rss-rogers.png" alt="[Valid RSS]" title="Validate my RSS feed" /></a>

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/

Home · About · News · Docs · Terms