<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sonoma on Melabit</title>
    <link>https://static.233.196.69.159.clients.your-server.de/en/tags/sonoma/</link>
    <description>Recent content in Sonoma on Melabit</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 04 Feb 2025 06:00:00 +0000</lastBuildDate>
    <atom:link href="https://static.233.196.69.159.clients.your-server.de/en/tags/sonoma/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Apple, we fixed some issues: from Sonoma to Sequoia</title>
      <link>https://static.233.196.69.159.clients.your-server.de/en/2025/02/04/apple-we-fixed-some-issues-from-sonoma-to-sequoia/</link>
      <pubDate>Tue, 04 Feb 2025 06:00:00 +0000</pubDate>
      <guid>https://static.233.196.69.159.clients.your-server.de/en/2025/02/04/apple-we-fixed-some-issues-from-sonoma-to-sequoia/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2025-02-04-apple-abbiamo-risolto-dei-problemi-da-sonoma-a-sequoia/bug-fix-in-sequoia.jpeg&#34; alt=&#34;&#34;&gt;&#xA;&amp;ndash; &lt;em&gt;Image generated by &lt;a href=&#34;https://designer.microsoft.com/image-creator&#34;&gt;Microsoft Designer&lt;/a&gt; AI.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;In the past few months, I have written four posts about macOS Sonoma bugs (a complete list is at the end of this post) because I found it unbelievable that this macOS version was released with such glaring issues in the Finder and in disk management.&lt;/p&gt;&#xA;&lt;p&gt;In the latest Sonoma versions, &lt;a href=&#34;https://melabit.com/en/2024/02/12/apple-we-have-a-problem-a-look-at-the-macos-sonoma-bugs/&#34;&gt;some reported bugs&lt;/a&gt; &amp;ndash; such as the erratic emptying of the Trash, the default file name when virtually printing a web page to PDF, or the failure to display a new file or folder in &lt;code&gt;Snap to Grid&lt;/code&gt; mode &amp;mdash; &lt;a href=&#34;https://melabit.com/en/2024/05/31/apple-we-have-a-problem-a-look-at-the-macos-sonoma-bugs-update/&#34;&gt;have been fixed&lt;/a&gt;, but the most annoying ones remained untouched.&lt;/p&gt;&#xA;&lt;p&gt;A couple of days ago, after testing macOS Sequoia on a spare machine, I decided to upgrade my home Mac Mini M1 to Sequoia 15.3. To my great satisfaction, I can say that all, or almost all, of the major bugs reported in my previous posts have disappeared.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;&lt;strong&gt;Bug #1&lt;/strong&gt;: If we have a folder full of files and drag icons below the bottom of the window while holding down the CMD (⌘) key, the bottom of the window now correctly expands to show the lower icons without making them look like they have disappeared.&#xA;The only exception is when the folder does not have an active scrollbar because it contains too few files. In this case, the icons still disappear, just like in Sonoma, but now you can simply click the &lt;code&gt;&amp;lt;&lt;/code&gt; icon in the upper left corner of the toolbar and return to the original folder to restore full file visibility.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Bug #2&lt;/strong&gt;: If we have two overlapping Finder windows in a Space and use the CTRL(⌃)-1, CTRL–2 (and so on) shortcuts to &lt;a href=&#34;https://youtu.be/lnCxG2AVfgI&#34;&gt;move the top window from one Space to another&lt;/a&gt;, upon returning to the original Space the &lt;em&gt;traveling&lt;/em&gt; window now appears on top of the one that stayed put, as it should. The same applies when more than two overlapping windows are present.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Bug #3&lt;/strong&gt;: The &lt;a href=&#34;https://youtu.be/nUBGoUJiW_A&#34;&gt;flickering issue&lt;/a&gt; that was highly visible in Sonoma when dragging a Finder window from one Space to another has now disappeared. Seeing such a thing was simply outrageous, not only because it was happening on machines powered by the powerful Apple Silicon processors, but also because before Sonoma such flickering had never been seen on much, much less powerful machines, like the Intel-based MacBook Air.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Bug #4&lt;/strong&gt;: Sequoia has also fixed the bug related to the &lt;a href=&#34;https://melabit.com/en/2024/11/14/apple-we-have-another-problem-a-new-macos-sonoma-bug/&#34;&gt;popup window that disappeared faster than a Formula 1 car&lt;/a&gt; when connecting a USB stick to a laptop, but I had already written about that.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Bug #5&lt;/strong&gt;: Finder has finally returned to normal when &lt;a href=&#34;https://melabit.wordpress.com/2024/05/31/apple-we-have-a-problem-a-look-at-the-macos-sonoma-bugs-update/&#34;&gt;displaying folders on an external USB drive containing hundreds of files&lt;/a&gt;. The sluggishness (to put it mildly) experienced in Sonoma was truly frustrating, and I was fed up with having to wait dozens of seconds every time I accessed a somewhat full external folder.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Bug #6&lt;/strong&gt;: But the real highlight of Sequoia, the one that earns it a solid B at the end of the first term, is that, for the first time in years, the macOS update did not &lt;a href=&#34;https://melabit.com/en/2024/02/22/apple-we-have-more-problems-a-look-at-macos-vintage-bugs/&#34;&gt;mess up the arrangement of icons&lt;/a&gt; in the &lt;code&gt;Applications&lt;/code&gt; folder.&#xA;There will be very few people, like me, who prefer to keep installed applications organized visually rather than alphabetically. But I still want to represent these few users and sincerely thank Apple developers for a fix we had been waiting for through countless macOS versions.&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;What else can I say? I am really pleased that Apple has managed to fix so many embarrassing Sonoma bugs with Sequoia. Especially because the ones I reported were not related to &lt;a href=&#34;https://eclecticlight.co/2023/12/14/serious-bugs-remain-in-macos-sonoma-14-2/&#34;&gt;exotic&lt;/a&gt; &lt;a href=&#34;https://eclecticlight.co/2024/01/24/serious-bugs-fixed-in-macos-sonoma-14-3&#34;&gt;features&lt;/a&gt; of the operating system or of the &lt;a href=&#34;https://eclecticlight.co/2024/03/18/serious-bug-in-sonoma-14-4-will-destroy-saved-versions-in-icloud-drive/&#34;&gt;file&lt;/a&gt; &lt;a href=&#34;https://eclecticlight.co/2024/03/19/sonomas-lost-versions-bug-what-it-is-and-how-to-safeguard-versions/&#34;&gt;system&lt;/a&gt;, but rather easily visible issues for anyone using the graphical user interface of macOS.&lt;/p&gt;&#xA;&lt;p&gt;I doubt that someone in Cupertino is avidly reading &lt;a href=&#34;https://melabit.com/posts/en&#34;&gt;Melabit&lt;/a&gt;. But this also means that the issues reported in my previous posts were real and evident to other users and Apple developers alike, not just the imaginary concerns of an overly meticulous user.&lt;/p&gt;&#xA;&lt;p&gt;The core problem remains: it makes no sense to continue with this policy of annual macOS (and iOS, iPadOS, watchOS, etc.) releases, each packed with shiny, but mostly useless new features that are inevitably under-tested and may introduce new bugs into the core of the system, without allowing enough time to fix existing bugs.&lt;/p&gt;&#xA;&lt;p&gt;An annual release cycle may be great for marketing, but is it really what users really need?&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;For those interested in my saga about macOS Sonoma’s bugs (and more), here are links to previous installments:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://melabit.com/en/2024/02/12/apple-we-have-a-problem-a-look-at-the-macos-sonoma-bugs/&#34;&gt;Apple, We Have a Problem: A Look at macOS Sonoma Bugs&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://melabit.com/en/2024/02/22/apple-we-have-more-problems-a-look-at-macos-vintage-bugs/&#34;&gt;Apple, We Have More Problems: A Look at macOS Vintage Bugs&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://melabit.com/en/2024/05/31/apple-we-have-a-problem-a-look-at-the-macos-sonoma-bugs-update/&#34;&gt;Apple, We Have a Problem: A Look at macOS Sonoma Bugs (Update)&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://melabit.com/en/2024/11/14/apple-we-have-another-problem-a-new-macos-sonoma-bug/&#34;&gt;Apple, We Have Another Problem: A New macOS Sonoma Bug&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;&#xA;&lt;hr&gt;&#xA;&lt;ol&gt;&#xA;&lt;li id=&#34;fn:1&#34;&gt;&#xA;&lt;p&gt;So much so that soon afterwards, I also updated the Mac Studio I use for work.&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:2&#34;&gt;&#xA;&lt;p&gt;It seems clear to me that there was no technical reason behind this issue (such as the strict separation between the default macOS applications and those installed by the user), but simply a lack of attention to a detail that may be minor, yet is quite annoying for those who rely on it.&amp;#160;&lt;a href=&#34;#fnref:2&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/div&gt;&#xA;</description>
    </item>
    <item>
      <title>Apple, we have a problem: a new macOS Sonoma bug</title>
      <link>https://static.233.196.69.159.clients.your-server.de/en/2024/11/14/apple-we-have-a-problem-a-new-macos-sonoma-bug/</link>
      <pubDate>Thu, 14 Nov 2024 06:00:00 +0000</pubDate>
      <guid>https://static.233.196.69.159.clients.your-server.de/en/2024/11/14/apple-we-have-a-problem-a-new-macos-sonoma-bug/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-11-14-apple-abbiamo-un-altro-problema-un-nuovo-baco-di-macos-sonoma/sonoma-new-bugs.jpeg&#34; alt=&#34;&#34;&gt;&#xA;&amp;ndash; &lt;em&gt;Image generated by &lt;a href=&#34;https://designer.microsoft.com/image-creator&#34;&gt;Microsoft Designer&lt;/a&gt; AI.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Sonoma’s bugs never fail to surprise, and here I describe a fresh one, which luckily has been fixed in Sequoia.&lt;/p&gt;&#xA;&lt;p&gt;Take a new MacBook Air or Pro, where you’ve just installed Sonoma, or a MacBook where you erased the startup disk before installing Sonoma (what happens when simply updating from a previous version might be different).&lt;/p&gt;&#xA;&lt;p&gt;Try inserting a USB stick or external USB drive (or even an SD card, when available). What you’ll see is this:&lt;/p&gt;&#xA;&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;&#xA;      &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; allowfullscreen=&#34;allowfullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/GvHlNf3Gtcc?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;&#xA;    &lt;/div&gt;&#xA;&#xA;&lt;p&gt;That is, you’ll see practically nothing, even in slow motion.&lt;/p&gt;&#xA;&lt;p&gt;In theory, macOS should display a pop-up window asking the user whether they want to allow the connection of the &lt;em&gt;USB accessory&lt;/em&gt; (as Apple calls it) to the Mac. The problem is, as shown in the video, the pop-up disappears faster than a Formula 1 car.&lt;/p&gt;&#xA;&lt;p&gt;I must say that the first few times this happened, I didn’t even see it. Only after several unsuccessful and increasingly frustrating attempts, a very quick shadow on the screen made me suspect an overly zealous disappearing window.&lt;/p&gt;&#xA;&lt;p&gt;This bug occurs with macOS Sonoma 14.6; I have no idea if previous versions are affected. To work around the issue, you need to go to &lt;strong&gt;System Settings&lt;/strong&gt; under &lt;strong&gt;Privacy &amp;amp; Security&lt;/strong&gt; and change the &lt;code&gt;Allow accessory connections&lt;/code&gt; option from &lt;code&gt;Ask Every Time&lt;/code&gt;, or &lt;code&gt;Ask for New Accessories&lt;/code&gt;, to &lt;code&gt;Always&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-11-14-apple-abbiamo-un-altro-problema-un-nuovo-baco-di-macos-sonoma/macos-sonoma-accessory-bug.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;Once the USB drive is connected, for added security, you can return to selecting the &lt;code&gt;Ask for New Accessories&lt;/code&gt; option—just remember to repeat the procedure every time you insert a new USB stick (or external drive).&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;At first glance, it seems strange that the consent request for connecting new accessories only appears on MacBooks and not on desktop Macs.&lt;/p&gt;&#xA;&lt;p&gt;But thinking about it, it makes sense. I don’t believe macOS developers want to prevent us from connecting our own USB drives or those of people we know. Instead, I think they want to prevent someone from surreptitiously inserting a &lt;a href=&#34;https://www.youtube.com/watch?v=e_f9p-_JWZw&#34;&gt;&lt;em&gt;malicious USB stick&lt;/em&gt;&lt;/a&gt; (also known as a &lt;a href=&#34;https://shop.hak5.org/products/usb-rubber-ducky?variant=353378649&#34;&gt;Rubber Ducky&lt;/a&gt;), which can now even be made at home with a low-cost &lt;a href=&#34;https://github.com/dbisu/pico-ducky&#34;&gt;Raspberry Pi Pico&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;These sticks are programmable and can cause serious damage to a computer, from automatically transferring sensitive files onto the stick,&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; to erasing—if the programmer has the admin account password—the entire system disk.&lt;/p&gt;&#xA;&lt;p&gt;It goes without saying that such an attack is more likely to happen on a MacBook, often left unattended, rather than on a desktop computer, which remains in more controlled environments like home or the office.&lt;/p&gt;&#xA;&lt;p&gt;Including this type of security check in the operating system is therefore a great idea; what’s terrible is how it’s implemented in macOS Sonoma.&lt;/p&gt;&#xA;&lt;p&gt;The good news is that in macOS Sequoia, the bug has been fixed, and the pop-up remains clearly visible on the screen until the user makes a choice.&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;For those interested in my saga on macOS Sonoma bugs (and more), here are links to previous posts:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://melabit.com/en/2024/02/12/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs/&#34;&gt;Apple abbiamo un problema: uno sguardo ai bachi di macOS Sonoma&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://melabit.com/en/2024/02/26/sonoma-there-is-some-good-around/&#34;&gt;Sonoma: c’è del buono&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://melabit.com/en/2024/05/31/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs-update/&#34;&gt;Apple abbiamo un problema: uno sguardo ai bachi di macOS Sonoma (aggiornamento)&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;&#xA;&lt;hr&gt;&#xA;&lt;ol&gt;&#xA;&lt;li id=&#34;fn:1&#34;&gt;&#xA;&lt;p&gt;It’s not just stealth aircraft designers at risk of this happening, as it could just as easily involve documents from a divorce case or a financial dispute.&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/div&gt;&#xA;</description>
    </item>
    <item>
      <title>Apple, we have a problem: a look at macOS Sonoma bugs (update)</title>
      <link>https://static.233.196.69.159.clients.your-server.de/en/2024/05/31/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs-update/</link>
      <pubDate>Fri, 31 May 2024 06:00:00 +0000</pubDate>
      <guid>https://static.233.196.69.159.clients.your-server.de/en/2024/05/31/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs-update/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-05-31-apple-abbiamo-un-problema-uno-sguardo-ai-bachi-di-macos-sonoma-aggiornamento/sonoma-bugs-update.jpeg&#34; alt=&#34;&#34;&gt;&#xA;&amp;ndash; &lt;em&gt;Image generated by &lt;a href=&#34;https://designer.microsoft.com/image-creator&#34;&gt;Microsoft Designer&lt;/a&gt; AI.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;A couple of months ago, I &lt;a href=&#34;https://melabit.com/en/2024/02/12/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs/&#34;&gt;listed some more or less serious bugs in Sonoma&lt;/a&gt; that I noticed while getting familiar with the latest version of macOS, first on the new &lt;a href=&#34;https://melabit.com/en/2024/02/04/mac-studio/&#34;&gt;Mac Studio M2 Ultra&lt;/a&gt; and then on the household &lt;a href=&#34;https://melabit.com/en/2024/03/11/from-intel-to-apple-silicon/&#34;&gt;Mac Mini M1&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;At that time, I was using macOS Sonoma 14.3, which I soon updated on the Mini to version 14.3.1. With this minor release, Apple fixed a couple of the bugs I described, specifically the one about emptying the Trash into a random Space and the issue that prevented giving decent names to PDF files generated by the &lt;code&gt;Print&lt;/code&gt; function.&lt;/p&gt;&#xA;&lt;p&gt;Since I primarily use the &lt;code&gt;Print&lt;/code&gt; (virtual) function for PDFs in Firefox, I suspected this bug might be tied to the browser rather than the operating system. But that’s not the case. On the updated Mini, the issue disappeared, but the Mac Studio, which stayed on version 14.3 longer, continued to bother me despite having the exact same browser as the Mini.&lt;/p&gt;&#xA;&lt;p&gt;Now both machines have macOS 14.5 installed, and the PDF naming issue has disappeared on the Mac Studio as well. However, all the &lt;a href=&#34;https://melabit.com/en/2024/02/12/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs/&#34;&gt;other bugs I reported&lt;/a&gt; still happily persist. In fact, with this post, I’m adding two new bugs, one of which immediately climbed to the top of my &lt;a href=&#34;https://www.facebook.com/share/v/6KYMsC2rCoHTYpsd/&#34;&gt;list of annoyances&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;The first bug was pointed out to me by &lt;a href=&#34;https://muloblog2.netlify.app&#34;&gt;Mimmo&lt;/a&gt; (thanks!) back in the days of Sonoma 14.3. It involved Safari occasionally hiding the text within a selection, as shown in the image below.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-05-31-apple-abbiamo-un-problema-uno-sguardo-ai-bachi-di-macos-sonoma-aggiornamento/sonoma-safari-bug-zoom.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;It’s not a major issue, I admit, but it’s surprising in a product from a company as detail-oriented as Apple. Apparently, Cupertino thought so too, as it seems to have been fixed in the transition from version 14.3 to 14.5. That’s better.&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;The other bug is so obvious that I can’t understand how I missed it before: every time I open a folder with a large number of files, Sonoma’s Finder takes an eternity to display them.&lt;/p&gt;&#xA;&lt;p&gt;For years, I’ve used an external USB drive to store everything I want to keep but don’t need daily. Some folders contain thousands and thousands of files, but until now, viewing their contents was always instantaneous, or nearly so. And this was even with a mechanical drive—high quality but still mechanical.&lt;/p&gt;&#xA;&lt;p&gt;With Sonoma, everything suddenly changed: every time I open a very full folder, I have to wait several dozen seconds before seeing its contents. And when I say dozens of seconds, I mean 40, 50, even 60 seconds for a folder with 1,000–2,000 items. That’s a lot, sure, but it’s not the end of the world.&lt;/p&gt;&#xA;&lt;p&gt;What’s strange is that until Monterey, &lt;strong&gt;with the same external drive&lt;/strong&gt;, viewing was practically instantaneous, so I don’t think it’s a disk or connection speed issue.&lt;/p&gt;&#xA;&lt;p&gt;To rule out doubts, I even purchased a 2 TB NVMe SSD, which I installed in an &lt;a href=&#34;https://www.amazon.it/dp/B0CK2292Z4&#34;&gt;external hub&lt;/a&gt; connected to the Mini via USB-C. Now folder contents load faster (as expected!) but still much slower than what would normally be expected. Roughly speaking, it takes half the time it did before, which for an NVMe SSD—even an external one—still seems unacceptable to me.&lt;/p&gt;&#xA;&lt;p&gt;I hope Apple has noticed the problem and will fix it with macOS 15. Otherwise, I might actually have to file a bug report, and I really don’t feel like doing that.&lt;/p&gt;&#xA;</description>
    </item>
    <item>
      <title>From Intel to Apple Silicon</title>
      <link>https://static.233.196.69.159.clients.your-server.de/en/2024/03/11/from-intel-to-apple-silicon/</link>
      <pubDate>Mon, 11 Mar 2024 06:00:00 +0000</pubDate>
      <guid>https://static.233.196.69.159.clients.your-server.de/en/2024/03/11/from-intel-to-apple-silicon/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-03-11-da-intel-ad-apple-silicon/viktor-forgacs-WZT4YzbXiMk-unsplash.jpg&#34; alt=&#34;&#34;&gt;&#xA;&amp;ndash; &lt;em&gt;Source: &lt;a href=&#34;https://unsplash.com/@sonance&#34;&gt;Viktor Forgacs&lt;/a&gt; on &lt;a href=&#34;https://unsplash.com&#34;&gt;Unsplash&lt;/a&gt;&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The transition is complete: since a few days, all the computers I use for work are running on Apple Silicon ARM processors. This includes a Mac Studio M2 Ultra, which I’ve already &lt;a href=&#34;https://melabit.com/en/2024/02/04/mac-studio/&#34;&gt;talked about extensively&lt;/a&gt; and which sits on my office desk; a Mac Mini M1 with 16 GB RAM and 1 TB SSD &amp;ndash; previously neglected on a shelf for reasons I won’t go into here &amp;ndash; now in my home office; and a very basic MacBook Air M1 (just 8 GB RAM and 256 GB SSD, half the specs of my wife’s) for light use and when I’m on the go.&lt;/p&gt;&#xA;&lt;p&gt;Oh, and let’s not forget: since last summer, I’ve also been using an 11&amp;quot; iPad Pro M1, which is an absolute gem and deserves a post of its own.&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;The Mac Studio and Mini are running Sonoma, which &lt;a href=&#34;https://melabit.com/en/2024/02/12/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs/&#34;&gt;I’m not thrilled about&lt;/a&gt;, but it’s here to stay. Meanwhile, the Air is still on Monterey. I’ll update it to Sonoma soon to ensure consistency across all my machines.&lt;/p&gt;&#xA;&lt;p&gt;Needless to say, compared to the Intel models I’ve used up until now, the performance is on another level. The benchmarks &lt;a href=&#34;https://melabit.com/en/2022/02/20/macbook-air-m1-la-non-recensione-prestazioni-con-geekbench-5/&#34;&gt;already&lt;/a&gt; &lt;a href=&#34;https://melabit.wordpress.com/2022/03/15/macbook-air-m1-la-non-recensione-prestazioni-con-performance-test/&#34;&gt;say a lot&lt;/a&gt;, but the daily experience speaks volumes more: programs that open instantly, the fluidity of even the most resource-hungry applications, Python or R scripts that used to take minutes now finishing almost before I can blink.&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;Another clear indication of the speed of these machines is the time it takes to install (as usual) the operating system and all the applications I need from scratch (and there are quite a few).&lt;/p&gt;&#xA;&lt;p&gt;With the Mini, I completed everything in a single day (around 100 applications to download, register, and configure one by one). I spent a second day on finer details, such as transferring files between Macs, tweaking system settings (a rather complicated process that, thankfully, most users can skip), and installing essential command-line tools like &lt;code&gt;homebrew&lt;/code&gt; and &lt;code&gt;conda&lt;/code&gt; for my work.&lt;/p&gt;&#xA;&lt;p&gt;Rosetta installed itself automatically the first time I opened an Intel-only application, and so far, all the apps I’ve installed run without issue &amp;ndash; even the more niche ones that require specialized libraries. After all, it’s been over three years since the introduction of the first M1 Macs, and the &lt;a href=&#34;https://developer.r-project.org/Blog/public/2020/11/02/will-r-work-on-apple-silicon/&#34;&gt;early&lt;/a&gt; &lt;a href=&#34;https://www.wafrat.com/installing-tensorflow-2-5-and-jupyter-lab-on-m1/&#34;&gt;challenges&lt;/a&gt; should have been resolved long ago.&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;In short, the transition from Intel to Apple Silicon has been smooth &amp;ndash; easier than I initially expected and perhaps even simpler than the previous switch from PowerPC to Intel. And in any case, much easier than &lt;a href=&#34;https://www.youtube.com/watch?v=WhvlomhAh3Q&#34;&gt;crossing a busy street in Rome&lt;/a&gt; in the 1960s.&lt;/p&gt;&#xA;&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;&#xA;      &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; allowfullscreen=&#34;allowfullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/WhvlomhAh3Q?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;&#xA;    &lt;/div&gt;&#xA;&#xA;&lt;p&gt;P.S. What about my old Macs? As I’ve &lt;a href=&#34;https://melabit.com/en/2024/02/04/mac-studio/&#34;&gt;mentioned elsewhere&lt;/a&gt;, I have a new project in mind to repurpose them effectively. The initial tests look very promising, but I’d rather be sure about certain details before writing about it. &lt;em&gt;Stay tuned!&lt;/em&gt;&lt;/p&gt;&#xA;</description>
    </item>
    <item>
      <title>Sonoma: there is some good around</title>
      <link>https://static.233.196.69.159.clients.your-server.de/en/2024/02/26/sonoma-there-is-some-good-around/</link>
      <pubDate>Mon, 26 Feb 2024 06:00:00 +0000</pubDate>
      <guid>https://static.233.196.69.159.clients.your-server.de/en/2024/02/26/sonoma-there-is-some-good-around/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-26-sonoma-ce-del-buono/sonoma-rainbow.jpeg&#34; alt=&#34;&#34;&gt;&#xA;&amp;ndash; &lt;em&gt;Image generated by &lt;a href=&#34;https://designer.microsoft.com/image-creator&#34;&gt;Microsoft Designer&lt;/a&gt; AI.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Sonoma is still raw and comes with a &lt;a href=&#34;https://melabit.com/en/2024/02/12/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs./&#34;&gt;fair number of bugs&lt;/a&gt;, but fortunately, there is something good here too.&lt;/p&gt;&#xA;&lt;p&gt;As far as I’m concerned, I like that &lt;code&gt;Screen Sharing&lt;/code&gt; has finally gained its rightful place on the Mac, taking its spot in the &lt;code&gt;Utilities&lt;/code&gt; folder within &lt;code&gt;Applications&lt;/code&gt;, instead of being relegated to &lt;code&gt;/System/Library/CoreServices/Applications&lt;/code&gt;, as it had been until now.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-26-sonoma-ce-del-buono/screen-sharing.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;I could be wrong, but I remember a similar application, &lt;code&gt;Apple Remote Desktop&lt;/code&gt;, was present in &lt;code&gt;Utilities&lt;/code&gt; several years ago (around the time of Tiger or Leopard, maybe among the optional tools you could choose during installation). However, Apple quickly reversed course, hiding the remote access application within macOS system services and accessing it through the Finder menu &lt;code&gt;Go &amp;gt; Connect to Server&lt;/code&gt; or via the &lt;code&gt;Locations&lt;/code&gt; section of the sidebar.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;But back to today and Sonoma: the most interesting thing about the new &lt;code&gt;Screen Sharing&lt;/code&gt; is that the application now shows a history of all past connections, making it easy to reconnect to frequently used computers and to create consistent groups of connections for the various machines we use.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-26-sonoma-ce-del-buono/screen-sharing-connections.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;Having a dedicated application also means being able to configure it according to personal preferences. This was technically possible even with the pre-Sonoma application, but I only realized it while writing these lines.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-26-sonoma-ce-del-buono/screen-sharing-settings.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;Why am I so enthusiastic about &lt;code&gt;Screen Sharing&lt;/code&gt;? Because I often work over the network, and I find it very interesting to have a native tool that offers more advanced functions than those previously available. It’s just a pity that Apple uses the &lt;code&gt;vnc&lt;/code&gt; protocol to connect to remote Macs—a protocol with numerous security issues, often blocked by firewalls, which effectively limits the use of &lt;code&gt;Screen Sharing&lt;/code&gt; to local networks only.&lt;/p&gt;&#xA;&lt;p&gt;A real shame, because after years of partial remote work, I can say that &lt;code&gt;Screen Sharing&lt;/code&gt; is much more efficient than &lt;code&gt;Teamviewer&lt;/code&gt; (which I stopped using a long time ago) or &lt;code&gt;Chrome Remote Desktop&lt;/code&gt;, which I currently use even though it doesn’t completely satisfy me.&lt;/p&gt;&#xA;&lt;p&gt;These last four years have taught us that remote work is possible, but it requires the right tools. So, after &lt;a href=&#34;https://melabit.com/en/2024/02/12/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs./&#34;&gt;many&lt;/a&gt; &lt;a href=&#34;https://melabit.com/en/2024/02/22/apple-we-have-other-problems-a-look-at-macos-vintage-bugs/&#34;&gt;criticisms&lt;/a&gt;, Apple deserves a well-done here.&lt;/p&gt;&#xA;&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;&#xA;&lt;hr&gt;&#xA;&lt;ol&gt;&#xA;&lt;li id=&#34;fn:1&#34;&gt;&#xA;&lt;p&gt;An &lt;a href=&#34;https://apps.apple.com/it/app/apple-remote-desktop/id409907375&#34;&gt;advanced version&lt;/a&gt; of &lt;code&gt;Apple Remote Desktop&lt;/code&gt; is also available on the App Store for €89.99. A price not exactly popular for those who only need it occasionally, but absolutely fair for professionals who rely on it.&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/div&gt;&#xA;</description>
    </item>
    <item>
      <title>Apple, we have other problems: a look at macOS vintage bugs</title>
      <link>https://static.233.196.69.159.clients.your-server.de/en/2024/02/22/apple-we-have-other-problems-a-look-at-macos-vintage-bugs/</link>
      <pubDate>Thu, 22 Feb 2024 06:00:00 +0000</pubDate>
      <guid>https://static.233.196.69.159.clients.your-server.de/en/2024/02/22/apple-we-have-other-problems-a-look-at-macos-vintage-bugs/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-22-apple-abbiamo-altri-problemi-uno-sguardo-ai-bachi-depoca-di-macos/macos-bugs.jpeg&#34; alt=&#34;&#34;&gt;&#xA;&amp;ndash; &lt;em&gt;Image generated by &lt;a href=&#34;https://designer.microsoft.com/image-creator&#34;&gt;Microsoft Designer&lt;/a&gt; AI.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;In the &lt;a href=&#34;https://melabit.com/en/2024/02/12/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs/&#34;&gt;last post&lt;/a&gt;, I described some very recent bugs present in Sonoma, the latest version of macOS.&lt;/p&gt;&#xA;&lt;p&gt;The bugs reported here, however, have persisted across several versions of macOS, and it seems that Apple has &lt;a href=&#34;https://tidbits.com/2019/10/21/six-reasons-why-ios-13-and-catalina-are-so-buggy/&#34;&gt;no intention of fixing them&lt;/a&gt; or doesn’t even consider them to be bugs. These issues, unlike &lt;a href=&#34;https://eclecticlight.co/2023/12/14/serious-bugs-remain-in-macos-sonoma-14-2/&#34;&gt;other reports&lt;/a&gt;, don’t occur under extreme conditions or after opening a zillion files but during completely normal use, which makes it even stranger that they’ve never been resolved.&lt;/p&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;The first two are more user interface inconsistencies, which are surprising given the &lt;a href=&#34;https://developer.apple.com/design/human-interface-guidelines&#34;&gt;almost obsessive attention&lt;/a&gt; Apple dedicates to the &lt;a href=&#34;https://developer.apple.com/design/&#34;&gt;design details&lt;/a&gt; of its products.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;The scrollbar for the list of purchased apps in the App Store is partially hidden by the window title and only appears after scrolling through a certain number of apps (the exact number depends on the total apps in the list—if there are many, you’ll have to scroll quite a bit to see the scrollbar).&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;The same thing happens on the App Store home page when you move the mouse to the top of the window, causing the title to appear. However, since this page contains fewer elements, part of the scrollbar remains visible.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;This one, however, is an old bug related to Terminal.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;I’ve configured &lt;code&gt;System Settings &amp;gt; Desktop &amp;amp; Dock&lt;/code&gt; so that the &lt;code&gt;Prefer tabs when opening documents&lt;/code&gt; option is always active. This way, every time I open a new window in applications that support this feature (including Terminal), macOS creates a new tab instead of a new window.&lt;/p&gt;&#xA;&lt;p&gt;But if I’m using Terminal with a custom configuration (e.g., mine is set to 120 columns x 40 rows) and I select the menu option &lt;code&gt;New Window&lt;/code&gt; with a profile of a different size (e.g., the default of 80 columns x 24 rows), a new tab is indeed created, but the entire Terminal changes size to match the profile just chosen.&lt;/p&gt;&#xA;&lt;p&gt;This might even be a deliberate design choice. However, it contrasts with what happens when the &lt;code&gt;Prefer tabs when opening documents&lt;/code&gt; option is only active in full-screen mode, where the new tab adopts the size of the existing one.&lt;/p&gt;&#xA;&lt;p&gt;To be fair, it was worse in High Sierra: every time a new tab was opened, Terminal would lose a row. Fortunately, this bug was fixed in the next version of macOS.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;For me, who always uses the &lt;code&gt;Align to Grid&lt;/code&gt; option in Finder windows, organizes file icons visually in a logical order (at least for me), and often leaves empty spaces, this next bug is a major nuisance.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Until El Capitan, if I moved icons in a folder below the bottom edge of the window, Finder kept their order intact, leaving a blank space where the icons were originally located. Starting with Sierra, however, the bottom edge of the Finder window became a sort of impenetrable barrier, causing icons dragged below it to “bounce” back to the top of the window, leaving the bottom empty.&lt;/p&gt;&#xA;&lt;p&gt;To avoid this, you have to drag the icons while holding the &lt;strong&gt;CMD&lt;/strong&gt; (⌘) key, which in theory bypasses the grid alignment, but then you’ll need to manually restore their order afterward.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;This final gem, undoubtedly my favorite macOS bug, isn’t just an annoyance, it’s a &lt;em&gt;royal pain in the neck&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Just like with documents, I organize applications visually, grouping them by type and usage frequency, aligning the icons to Finder’s virtual grid.&lt;/p&gt;&#xA;&lt;p&gt;As a result, I place all pre-installed Apple apps (Pages, Numbers, Keynote, Xcode, iMovie, GarageBand, etc.) at the top of the &lt;code&gt;Applications&lt;/code&gt; folder, followed by office tools (Office 365, LibreOffice, PDF managers), communication apps (Teams, Webex, Skype), browsers, and remote access apps. Further down are apps specific to my work—note-taking, code editing, image editing—and at the bottom, utilities for monitoring Mac temperature, managing the clipboard, unzipping files, recording the screen, and occasionally running an antivirus scan (MalwareBytes).&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;This organization allows me to quickly locate the app I need, as I know exactly where it should be even if I don’t remember its name.&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;Unfortunately, for several macOS versions now, every time I update the OS, app icons are always reordered alphabetically. Since alphabetical order is the default for the &lt;code&gt;Applications&lt;/code&gt; folder, most users don’t notice this. But for those like me, who prefer custom order, it means having to reorganize everything after every update.&lt;/p&gt;&#xA;&lt;p&gt;Why do I consider this a bug and not a feature? The reason is simple: Finder allows different sorting options for any folder—alphabetically, by date, by size, by type—and also lets you align items to a grid or leave them unordered. So why should the &lt;code&gt;Applications&lt;/code&gt; folder behave differently?&lt;/p&gt;&#xA;&lt;p&gt;Are there technical reasons for this decision? Under normal use, the &lt;code&gt;Applications&lt;/code&gt; folder can be customized like any other Finder folder, so why should Finder reset customizations after every OS update, even minor ones?&lt;/p&gt;&#xA;&lt;p&gt;In my humble opinion, this issue, along with the one mentioned above, is tied to a problem with the pesky &lt;code&gt;.DS_Store&lt;/code&gt; files that manage each Finder folder’s configuration. The &lt;a href=&#34;https://0day.work/parsing-the-ds_store-file-format/&#34;&gt;file format&lt;/a&gt; is more secretive than Area 51.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr style = &#34;border: none; &#xA;            border-top: 3px double #333; &#xA;            color: #333; &#xA;            overflow: visible; &#xA;            height: 5px; &#xA;            width: 50%; &#xA;            margin-left: auto; &#xA;            margin-right: auto;&#34;&#xA;&gt;&#xA;&#xA;&lt;p&gt;If anyone from Apple’s development team is reading this, could you spare an hour to fix these bugs? It shouldn’t be too difficult—please take a look, a loyal user would be grateful.&lt;/p&gt;&#xA;&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;&#xA;&lt;hr&gt;&#xA;&lt;ol&gt;&#xA;&lt;li id=&#34;fn:1&#34;&gt;&#xA;&lt;p&gt;The ability to organize apps and documents visually is one of macOS’s features that makes me prefer it over Linux or—horror!—Windows, where this workflow simply doesn’t exist.&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:2&#34;&gt;&#xA;&lt;p&gt;On the Mac I’m using to write this, I have 148 installed apps, which, for my habits, isn’t even that many. Remembering all their names isn’t for me, so I’ve never used alphabetical sorting or apps like Alfred and the like.&amp;#160;&lt;a href=&#34;#fnref:2&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/div&gt;&#xA;</description>
    </item>
    <item>
      <title>Apple, we have a problem: a look at macOS Sonoma bugs</title>
      <link>https://static.233.196.69.159.clients.your-server.de/en/2024/02/12/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs/</link>
      <pubDate>Mon, 12 Feb 2024 06:00:00 +0000</pubDate>
      <guid>https://static.233.196.69.159.clients.your-server.de/en/2024/02/12/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-12-apple-abbiamo-un-problema-uno-sguardo-ai-bachi-di-macos-sonoma/sonoma-bugs.jpeg&#34; alt=&#34;&#34;&gt;&lt;br&gt;&#xA;&amp;ndash; &lt;em&gt;Image generated by &lt;a href=&#34;https://designer.microsoft.com/image-creator&#34;&gt;Microsoft Designer&lt;/a&gt; AI.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;I use my Mac for work, so I&amp;rsquo;m always reluctant to update macOS too quickly. I usually prefer to wait until the current version matures, and sometimes I skip it entirely, maybe because I&amp;rsquo;ve read &lt;a href=&#34;https://mjtsai.com/blog/2022/12/27/ventura-issues/&#34;&gt;particularly negative reports&lt;/a&gt; or because I wasn&amp;rsquo;t convinced after using it on a friend&amp;rsquo;s or colleague&amp;rsquo;s computer (as I did with Sierra, Catalina, and Ventura).&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;Until now, all the Macs under my control—both the ones I personally use and those in my family—were running Monterey. I like it because it&amp;rsquo;s stable, fast, and compatible with all the applications I use daily (and there are quite a few).&lt;/p&gt;&#xA;&lt;p&gt;However, with my &lt;a href=&#34;https://melabit.com/en/2024/02/04/mac-studio/&#34;&gt;new Mac Studio&lt;/a&gt;, I had to make an exception because it came with Sonoma pre-installed and is likely not compatible with Monterey. It might work with Ventura, but Ventura is one of the versions on my blacklist, so what&amp;rsquo;s the point in using it?&lt;/p&gt;&#xA;&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;&#xA;&lt;p&gt;Sonoma irked me from the day I read that it would no longer natively allow conversion of PostScript or EPS (Encapsulated PostScript) files to PDF. I know that few people use PostScript today, and I can still use &lt;a href=&#34;https://eclecticlight.co/2023/09/27/how-to-convert-postscript-and-eps-files-in-sonoma-in-a-vm-apple-silicon/&#34;&gt;Ghostscript or an emulator&lt;/a&gt; to convert my old EPS files instead of relying on &lt;code&gt;Preview&lt;/code&gt;. But it&amp;rsquo;s almost a &lt;em&gt;philosophical&lt;/em&gt; matter: macOS is a very complex operating system made up of thousands upon thousands of interconnected components. Was there really no more room to maintain support for PostScript/EPS files? &lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;As soon as I started using Sonoma on the Mac Studio, I realized my initial skepticism was well-founded. Sonoma is plagued by quite a few baffling bugs that fail to do justice to the potential of the Mac Studio.&lt;/p&gt;&#xA;&lt;h4 id=&#34;sonoma-bugs&#34;&gt;Sonoma Bugs&lt;/h4&gt;&#xA;&lt;p&gt;Most of the Sonoma bugs I’ve noticed occur in the &lt;a href=&#34;https://support.apple.com/en-us/guide/mac-help/mchlp2605/14.0/mac/14.0&#34;&gt;Finder&lt;/a&gt; and &lt;a href=&#34;https://support.apple.com/en-us/guide/mac-help/mh14112/14.0/mac/14.0&#34;&gt;Spaces&lt;/a&gt;. The Finder is widely used by all macOS users, while Spaces is less popular among everyday users but presumably favored by the operating system&amp;rsquo;s developers. Some of these bugs are so obvious that I find it strange they weren’t fixed during the &lt;em&gt;beta testing&lt;/em&gt; phase or in the updates released over the past months. In any case, all these bugs are present in Sonoma 14.3, the version currently installed on my Mac Studio.&lt;/p&gt;&#xA;&lt;p&gt;The following list is roughly ordered by (personal) importance, starting with the more &lt;em&gt;minor&lt;/em&gt; bugs—small annoyances that don’t greatly impact the macOS Sonoma experience—and ending with the truly &lt;em&gt;critical&lt;/em&gt; and unjustifiable ones.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Right after installing Sonoma, when browsing the network from another Mac, the Mac Studio icon appears as a question mark, while icons for other pre-Sonoma Macs appear normal. After a few hours, the Mac Studio icon returns to normal.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Occasionally, the confirmation message for emptying the Trash appears in a Space different from the one where the command was executed. This also happens in Monterey, but in that version, the Finder automatically switches to the Space with the message, allowing the user to click the confirmation button. In Sonoma, this doesn’t happen, and since the message isn’t visible, users keep trying to empty the Trash unsuccessfully.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;When using the &lt;code&gt;Print&lt;/code&gt; function to generate a PDF of a document or a webpage, the PDF file no longer automatically inherits the name of the source document and is instead named &lt;code&gt;Untitled&lt;/code&gt;. This never happened before and is incredibly annoying. Is it possible that macOS developers never generate PDF files?&lt;/p&gt;&#xA;&lt;p&gt;I suspect the bug is related to the removal of PostScript support, but I’m not entirely sure.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;In a Finder window set to &lt;code&gt;Align to Grid&lt;/code&gt; mode, if we drag a group of files below the window’s bottom edge while holding the &lt;strong&gt;CMD&lt;/strong&gt; (⌘) key and then release the mouse, the lower icons disappear from view, giving the impression that the files are lost.&lt;sup id=&#34;fnref:3&#34;&gt;&lt;a href=&#34;#fn:3&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;3&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;To make them reappear, you must switch the view mode (e.g., use &lt;strong&gt;CMD&lt;/strong&gt; (⌘)-&lt;strong&gt;2&lt;/strong&gt; to switch to list view and then return to icon view with &lt;strong&gt;CMD&lt;/strong&gt; (⌘)-&lt;strong&gt;1&lt;/strong&gt;). Alternatively, you can navigate up one folder level and then back, or simply close the current window and reopen it, selecting the same folder again.&lt;/p&gt;&#xA;&lt;p&gt;The images below illustrate what happens. The first image shows a Finder folder containing a collection of documents and other folders.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-12-apple-abbiamo-un-problema-uno-sguardo-ai-bachi-di-macos-sonoma/sonoma-finder-drag-bug-1.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;Here, I selected some files and dragged them downward while holding the &lt;strong&gt;CMD&lt;/strong&gt; (⌘) key (if I didn’t, the lower files would move to the top of the window once they passed the bottom edge). This action should expand the Finder&amp;rsquo;s virtual window, causing a scroll bar to appear. However, in Sonoma, this doesn’t happen, and it seems as if the files have disappeared.&lt;sup id=&#34;fnref:4&#34;&gt;&lt;a href=&#34;#fn:4&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;4&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-12-apple-abbiamo-un-problema-uno-sguardo-ai-bachi-di-macos-sonoma/sonoma-finder-drag-bug-2.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;Switching to list view and back to icon view finally displays the scroll bar, revealing the files below the bottom edge.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-12-apple-abbiamo-un-problema-uno-sguardo-ai-bachi-di-macos-sonoma/sonoma-finder-drag-bug-3.png&#34; alt=&#34;&#34;&gt;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Closely related to the previous bug: if I open a Finder folder in &lt;code&gt;Align to Grid&lt;/code&gt; mode and add a new file, it sometimes isn’t visible until I perform one of the actions mentioned above. The same issue occurs when creating or copying a new folder. To make matters worse, this bug happens randomly—sometimes everything works fine, sometimes it doesn’t—causing even more confusion for users dealing with Sonoma&amp;rsquo;s Finder.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Suppose you have two overlapping windows in a Space, let’s say Space 1. If you click on the top window’s title bar, hold down the mouse button, and use the &lt;strong&gt;CTRL&lt;/strong&gt; (⌃) + &lt;strong&gt;2&lt;/strong&gt; and &lt;strong&gt;CTRL&lt;/strong&gt; + &lt;strong&gt;1&lt;/strong&gt; shortcuts to move to Space 2 and back, the &lt;em&gt;traveling&lt;/em&gt; window always ends up below the stationary one when you return to the original Space.&lt;/p&gt;&#xA;&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;&#xA;          &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; allowfullscreen=&#34;allowfullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/lnCxG2AVfgI?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;&#xA;        &lt;/div&gt;&#xA;&#xA;&lt;p&gt;If there are three or more partially overlapping windows, the window that moves between Spaces always ends up &lt;strong&gt;below&lt;/strong&gt; the window that had focus before the traveling window but &lt;strong&gt;above&lt;/strong&gt; all other Finder windows.&lt;/p&gt;&#xA;&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;&#xA;          &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; allowfullscreen=&#34;allowfullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/NZxeilBRUsI?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;&#xA;        &lt;/div&gt;&#xA;&#xA;&lt;p&gt;This behavior only affects Finder windows: if you overlap a Finder window with, say, a Safari window, the Finder window that moves between Spaces will reappear in the original Space always on top of Safari, as it should.&lt;/p&gt;&#xA;&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;&#xA;          &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; allowfullscreen=&#34;allowfullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/SVtTsi-NVa4?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;&#xA;        &lt;/div&gt;&#xA;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Those who watched the videos above may have noticed another very serious problem: every time any window is dragged between Spaces, there is a noticeable &lt;strong&gt;flickering&lt;/strong&gt; of the window’s background. This may be related to the code responsible for redrawing the window.&lt;/p&gt;&#xA;&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;&#xA;          &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; allowfullscreen=&#34;allowfullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/nUBGoUJiW_A?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;&#xA;        &lt;/div&gt;&#xA;&#xA;&lt;p&gt;This happens on the powerful Mac Studio as well as on less capable Macs (thanks, Mimmo!). It has never, ever happened in any previous macOS version.&lt;sup id=&#34;fnref:5&#34;&gt;&lt;a href=&#34;#fn:5&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;5&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;The strange thing is that this is a very common operation for regular Spaces users. It’s baffling that the developers didn’t notice it or, if they did, didn’t address it before releasing the operating system. Seriously, with today’s ultra-powerful computers, must we really wait half a second to redraw a window?&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h4 id=&#34;conclusions&#34;&gt;Conclusions&lt;/h4&gt;&#xA;&lt;p&gt;These are the Sonoma bugs I’ve personally noticed so far. The list is certainly not exhaustive but reflects my particular way of using macOS, including constant use of Spaces (which I find much more convenient than a multi-monitor setup), frequent drag-and-drop operations in the Finder, and reliance on keyboard shortcuts.&lt;/p&gt;&#xA;&lt;p&gt;As we’ve just seen, Sonoma introduced several bugs of varying severity. However, macOS also suffers from many &lt;em&gt;vintage bugs&lt;/em&gt;—issues that have existed for years and that Apple either refuses to fix or doesn’t consider problematic. But you’ll read about those in the &lt;a href=&#34;https://melabit.com/en/2024/02/22/apple-we-have-other-problems-a-look-at-macos-vintage-bugs/&#34;&gt;next post&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;&#xA;&lt;hr&gt;&#xA;&lt;ol&gt;&#xA;&lt;li id=&#34;fn:1&#34;&gt;&#xA;&lt;p&gt;I’m not &lt;a href=&#34;https://morrick.me/archives/9696&#34;&gt;as critical as Riccardo Mori&lt;/a&gt; regarding the more recent macOS versions, but I admit that what he writes strikes a nerve.&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:2&#34;&gt;&#xA;&lt;p&gt;At this point, I could launch into a long rant about how our digital documents risk becoming unreadable in just a few years unless we’ve printed hard copies, but I’ll spare you that since it’s not the main topic of this post.&amp;#160;&lt;a href=&#34;#fnref:2&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:3&#34;&gt;&#xA;&lt;p&gt;What’s the purpose of such an operation? For example, to make space for new files that, for some reason, you want to place before the existing ones while maintaining the order of the already-present icons, or to manually rearrange files.&amp;#160;&lt;a href=&#34;#fnref:3&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:4&#34;&gt;&#xA;&lt;p&gt;Needless to say, in &lt;code&gt;System Settings&lt;/code&gt;, I’ve chosen to keep the scroll bars always visible.&amp;#160;&lt;a href=&#34;#fnref:4&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:5&#34;&gt;&#xA;&lt;p&gt;I can&amp;rsquo;t speak for Ventura, which I&amp;rsquo;ve never tested thoroughly, but this certainly never happened in Monterey and earlier versions of macOS.&amp;#160;&lt;a href=&#34;#fnref:5&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/div&gt;&#xA;</description>
    </item>
    <item>
      <title>Mac Studio!</title>
      <link>https://static.233.196.69.159.clients.your-server.de/en/2024/02/04/mac-studio/</link>
      <pubDate>Sun, 04 Feb 2024 06:00:00 +0000</pubDate>
      <guid>https://static.233.196.69.159.clients.your-server.de/en/2024/02/04/mac-studio/</guid>
      <description>&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_2162.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;And here it is, the Mac Studio. I had to go through a long bureaucratic process to get it, but I finally managed, and now it’s right here in front of me.&lt;/p&gt;&#xA;&lt;p&gt;The first thing you notice is that the box is heavy, very heavy. The specs state that the Mac Studio is large and weighs about as much as three Mac Minis stacked on top of each other (19.7 x 19.7 x 9.5 cm^3 and 3.6 kg for the Mac Studio versus 19.7 x 19.7 x 3.6 cm^3 and 1.2 kg for the Mac Mini). I’ve never held three Mac Minis together, but the box gives a strong impression of solidity, which is definitely a positive for such an expensive device.&lt;/p&gt;&#xA;&lt;p&gt;The Mac Studio is indeed not cheap. The configuration I chose is almost top-of-the-line — M2 Ultra processor with a 24-core CPU, 60-core GPU, and 32-core Neural Engine, 128 GB of RAM, and a 1 TB SSD. The total cost was just under €7,000 — the price of two Vision Pros.&lt;/p&gt;&#xA;&lt;p&gt;But quality comes at a price, and for an equivalent workstation from HP, Dell, or Lenovo, you’d have to shell out €1,000 to €4,000 more.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; In this case, Apple is even competitive.&lt;/p&gt;&#xA;&lt;h4 id=&#34;unboxing&#34;&gt;Unboxing&lt;/h4&gt;&#xA;&lt;p&gt;I’m not a fan of unboxing rituals, but the Mac Studio deserves this initiation ceremony. The box is a tall, sturdy cardboard parallelepiped, more developed in height than width.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_2165.png&#34; alt=&#34;&#34;&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_2163.png&#34; alt=&#34;&#34;&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_2164.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Opening the box is incredibly easy: just pull the tab and fold one side of the box open, reminiscent of the &lt;a href=&#34;https://www.ifixit.com/Guide/Opening&amp;#43;PowerMac&amp;#43;G4&amp;#43;M5183&amp;#43;Case/2016&#34;&gt;opening mechanism of the Mac Pro G4&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_2166.png&#34; alt=&#34;&#34;&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_2167.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Seeing the Mac Studio lying on its side is a bit unsettling — it looks like it could fall at any moment. But the side flaps are much sturdier than they appear, and the Mac Studio is far too large to slip out of their grip.&lt;/p&gt;&#xA;&lt;p&gt;At this point, you need to lay the box on its side, spread the flaps in the direction of the arrows, remove the protective paper wrapping, and finally hold the Mac Studio in your hands.&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_2173.png&#34; alt=&#34;&#34;&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_2179.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;It really does look like a Mac Mini stretched in height, and now it seems appropriately weighted for its size. The additional weight is entirely due to the box, which is clearly designed to provide the best protection for the valuable item inside.&lt;/p&gt;&#xA;&lt;p&gt;Even the power cable is a piece of engineering — thick yet flexible, with a fabric sheath that reminds me of those on &lt;a href=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/ferro-da-stiro-anni-60.png&#34;&gt;old irons&lt;/a&gt;. This one, however, has a much tighter weave and is unquestionably more elegant. Too bad about the plug — I would have preferred a Schuko, but so be it.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_1884.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;Connecting the power cable and the USB-C cable for the monitor is a breeze. Even pairing my wireless keyboard and mouse (Logitech, both excellent) was simple: I just removed the USB dongle from my usual Mac and plugged it into one of the Mac Studio’s ports — no need to configure anything or &lt;a href=&#34;https://support.apple.com/it-it/guide/mac-help/mchl82829c17/14.0/mac/14.0&#34;&gt;fuss with Bluetooth&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_1889.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;Finding the power button was a bit trickier. It’s on the bottom-left corner, perfectly flush with the body of the device, and practically imperceptible to touch. But once pressed, badaboom! In a few seconds, the macOS welcome screen appears. A quick system configuration (since I’ll be reinstalling anyway), and the Sonoma desktop appears.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_1896.png&#34; alt=&#34;&#34;&gt;&lt;h4 id=&#34;reinstalling-macos&#34;&gt;Reinstalling macOS&lt;/h4&gt;&#xA;&lt;p&gt;Call me obsessive, but I always reinstall macOS from scratch on any new Mac I get my hands on. Maybe it’s a habit from the past, a fixation, or just a desire for control, but I’ve never used a Mac without personally installing macOS.&lt;/p&gt;&#xA;&lt;p&gt;On Apple Silicon Macs, you need to hold down the power button until the &lt;code&gt;Options&lt;/code&gt; icon (a gear symbol) appears, usually alongside one or more icons representing the Mac’s disks. Clicking on &lt;code&gt;Options&lt;/code&gt; and confirming loads the &lt;a href=&#34;https://support.apple.com/it-it/guide/mac-help/mchl82829c17/14.0/mac/14.0&#34;&gt;macOS Recovery utility&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_1897.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;Once Recovery loads, I first initialize the system disk with Disk Utility, giving it a more meaningful name than the default &lt;code&gt;Macintosh HD&lt;/code&gt; (usually the same name I use on the network for easy identification). Then, I reinstall macOS using the straightforward guided procedure.&lt;/p&gt;&#xA;&lt;p&gt;As always, the estimated installation time is wildly inaccurate: the three-plus hours initially shown turn out to be just about 40 minutes — not short, but not excessive for installing a complex OS like macOS.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_1910.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;It’s also curious that after the mandatory reboot, the screen resolution drops significantly, only to return to normal once the macOS welcome screen appears. I’ve never seen this happen with other macOS versions, but it’s worth noting that most of my (re)installations are done on MacBooks, which have more consistent hardware than desktop systems.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_1914.png&#34; alt=&#34;&#34;&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_1915.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;After carefully completing the initial macOS setup, I was back on the Sonoma desktop within minutes. Now, I could finally start experiencing how the Mac Studio performs.&lt;/p&gt;&#xA;&lt;h4 id=&#34;how-does-the-mac-studio-perform&#34;&gt;How Does the Mac Studio Perform?&lt;/h4&gt;&#xA;&lt;p&gt;The Mac Studio runs beautifully (but was there any doubt?). Everything is smooth, without the slightest hiccup. While this is true for all Apple Silicon Macs, it’s immediately clear that the Studio is a cut above — perhaps even two.&lt;/p&gt;&#xA;&lt;p&gt;Application installation is instantaneous: double-click the &lt;code&gt;.dmg&lt;/code&gt;, drag the icon to the &lt;code&gt;Applications&lt;/code&gt; folder, and&amp;hellip; done. Even with larger apps like GNU Emacs, GIMP, or Miniconda, the wait is just two or three seconds.&lt;/p&gt;&#xA;&lt;p&gt;The only app that put up some resistance was QGIS, whose installation took two and a half minutes on the Mac Studio. But that’s understandable for a 3 GB behemoth containing thousands of small files that need to be copied one by one.&lt;/p&gt;&#xA;&lt;p&gt;I didn’t bother with &lt;a href=&#34;https://www.geekbench.com/&#34;&gt;Geekbench&lt;/a&gt; or similar benchmarks to measure the Mac Studio’s performance. The web &lt;a href=&#34;https://browser.geekbench.com/search?utf8=%E2%9C%93&amp;amp;q=mac&amp;#43;studio&amp;#43;m2&amp;#43;ultra&#34;&gt;is already flooded with such data&lt;/a&gt;, and my results would only be redundant. Instead, I’m more interested in how the Mac Studio handles demanding applications — I have some early impressions but will wait to share more.&lt;/p&gt;&#xA;&lt;p&gt;Sonoma, however, is a drag. It’s clear from the start that this operating system is still full of bugs and inconsistencies (which I’ll showcase in the &lt;a href=&#34;https://melabit.com/en/2024/02/12/apple-we-have-a-problem-a-look-at-macos-sonoma-bugs/&#34;&gt;next post&lt;/a&gt;), and it doesn’t do justice to what the Mac Studio can really achieve.&lt;/p&gt;&#xA;&lt;p&gt;Apple has accustomed us to a tick-tock approach for its operating systems (similar to the one &lt;a href=&#34;https://en.wikipedia.org/wiki/Intel_Tick-Tock&#34;&gt;Intel followed for years&lt;/a&gt; with its processors): one year, they release an innovative but buggy and slow OS, followed by a version focusing almost exclusively on bug fixes and optimizations. This happened with Leopard and Snow Leopard, then with Lion and Mountain Lion. Later, the pattern continued with El Capitan, practically perfect after the horrendous Mavericks and Yosemite, and Mojave, following two mediocre releases like Sierra and High Sierra. Most recently, Monterey was excellent after the disaster of Catalina. Sonoma, theoretically the bug-fix version of Ventura, is a disappointment. Hopefully, Apple will fix things at the next WWDC in June — and big time.&lt;/p&gt;&#xA;&lt;h4 id=&#34;conclusion&#34;&gt;Conclusion&lt;/h4&gt;&#xA;&lt;p&gt;I did all the unboxing and setup of the Mac Studio at home, so I could work in peace away from the usual chaos at the institute. But after a week, the Mac Studio moved to my office, taking pride of place on my desk amid monitors, keyboards, mice, cables, and various gadgets.&lt;/p&gt;&#xA;&lt;img src=&#34;https://static.233.196.69.159.clients.your-server.de/img/2024-02-04-mac-studio/IMG_1970.png&#34; alt=&#34;&#34;&gt;&lt;p&gt;And my old High Sierra computer? That’s destined for a new project, and I’m really curious to see what comes of it. &lt;em&gt;Stay tuned!&lt;/em&gt;&lt;/p&gt;&#xA;&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;&#xA;&lt;hr&gt;&#xA;&lt;ol&gt;&#xA;&lt;li id=&#34;fn:1&#34;&gt;&#xA;&lt;p&gt;It’s worth noting that the aforementioned workstations are, at least theoretically, more expandable than the Mac Studio. However, expandability isn’t a critical factor for my specific needs.&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:2&#34;&gt;&#xA;&lt;p&gt;There’s not a single piece of plastic in the box. It may not be much from an environmental perspective, but it shows that it can be done.&amp;#160;&lt;a href=&#34;#fnref:2&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/div&gt;&#xA;</description>
    </item>
  </channel>
</rss>
