Can’t Wait to Get My Hands on OS26 and Tahoe

I am of that mindset. There seems to be some glitches that really should not be in a final release.

I’ve noticed this too. However, my experience tells me that people are more likely to share their dissatisfaction than their compliments. I believe most people are pleased or fine with the change but won’t post about it. Moreover, many people who initially react negatively will appreciate or tolerate the change over time. The new will become the new normal. I also expect that over the coming months, Apple will continue to monitor feedback and tweak the interface.

4 Likes

After the improvements on iOS, I decided to update my Mac to Tahoe. My previous complaints are no longer. YMMV.

3 Likes

Now that we are in November and macOS 26.1, what are y’all’s thoughts? Install now or wait until 26.2?

Still not a fan because some things in the MacOS UI I just can’t see (that’s mostly on me, but it is frustrating). The new Tinted setting in System Settings is less ugly than using Increase Contrast and Reduce Transparency settings.

I’d go ahead. Get it over with. I expect we will see more UI tweaking

2 Likes

That’s what I normally say about visiting the dentist.

8 Likes

I’m enjoing 26.1

26.0.1 had loads of delays/pauses/spinning beach balls on my M2 MacBook. The Spotlight clipboard had a strange bug where it didn’t save clips from Mail.app!

26.1 seems to have fixed all this. It runs smoothly and I’m now giving the Spotlight Clipboard a good run (I’ve turned off Copy 'em Paste to see how it goes).

I like Liquid Glass on the iPhone and iPad, so I’m just waiting for the stability issues to be worked out. Is 26.1 stable now?

Just one user. I have had no problems with my set of applications/uses.

1 Like

I have a new “problem” introduced to me with macOS 26.1:

When dealing with open or save dialog windows, both my Mac mini and my MacBook Pro feel sluggish. It takes one or a few seconds until the dialog appears and until it is getting populated.

I found this:

Same here: turning Desktop & Document sync off instantly fixed the delays, turning it on again, the sluggishness is back. :frowning:

Same thing with both of my Macs, no hanging sync with iCloud as far as I can tell, just an issue added with macOS 26.1. :frowning:

I have had no issues before.

2 Likes

Turning off Document & Desktop sync seems to be a good general solution, unfortunately. I disabled it in Mojave, I think, for slow file picking.

2 Likes

I have this turned on all the time and have yet to run into a problem. :crossed_fingers:t2:

2 Likes

That’s because us old guys think waiting a second or a few seconds is great compared to loading a program from a floppy and 5 minutes later being able to use it. :joy:

4 Likes

Now , now, you are assuming a lot about me. :wink::laughing:

I remember those waits! In fact, I remember using a small electric typewriter with whiteout to write college papers. Those were the days!

2 Likes

Expectations sure change over time, don’t they. :slight_smile:

I’m not surprised Desktop & Document sync work great for some. It’s just a common source of problems, when there are problems.

2 Likes

If somebody is experiencing the same: “we” are not alone:

Symptoms: In any app (TextEdit, Pages, Browsers, etc.), the Open/Save dialog lags for ~1s per folder navigation click. CPU spikes from fileproviderd, cloudd, bird, and siriactionsd. (…) Analysis: Based on process traces and container paths, this appears to originate in the FileProvider.framework subsystem (via fileproviderd), which mediates iCloud Drive. Early evidence suggests that folder enumeration of the iCloud Drive container root may be blocking UI threads in macOS 26.1. I believe this may be related to the recent internal migration of the file-provider backend (often referred to as “v3”), but I do not have direct confirmation from Apple of that exact change.

Via:
https://developer.apple.com/forums/thread/806709

Difference to my experience: turning off Desktop and Documents sync does fix the issue for me, apparently not for the developer.

Sorry that I continue on this matter over here. Maybe I should have started a different topic. I just wanted to follow up, just in case somebody else is experiencing the issue.

I’m starting to think I should wait for 26.2.

An Apple engineer has answered in the developer forums:

This is a known issue (r.161915582). While it isn’t fixed in the current seed (macOS 26.2 25C5031i), the issue is a high priority that’s being actively investigated.

:+1:

I still have a roll of Correctape even though I don’t have a typewriter anymore. :nerd_face:

2 Likes

Has anyone installed 26.2 yet? I’m still waiting to jump into the pool with Tahoe.