Live data from Hacker News

Welcome (back) to Macintosh

take.surf

11–20 of 276 posts

Re: Welcome (back) to Macintosh

#12
Tahoe introduced some changes to the windowing code that badly disrupted my DisplayPort device that was rock solid on Sequoia. I ended up switching to a new device as a workaround. Window memory use (I have a lot of virtual desktops and extra screens) is much higher and there's a peristent bug where taking a screenshot with CleanShot somehow resets the DisplayPort driver and everything flips out for a minute and it has to rediscover the external monitors. Infuriating.

Re: Welcome (back) to Macintosh

#13

I've been running Tahoe since 26.2, after cowardly skipping 0 and 1. And... it's fine? Am I only using the happy path? Or are people just particularly confident about complaining about Tahoe after seeing everyone else do it. For sure it has glitches, but as far as I can tell, they're the same glitches that were in Sequoia. (If anyone at Apple is reading this, can you take a glance at your NFS client code? It does lik…

Yes I agree.

I have an M1 Max like the author of this piece and recently upgraded. It's fine.

I don't like the look of it much and the drag targets are annoying but other than that it's been completely normal.

Re: Welcome (back) to Macintosh

#14
post #9
post #3

Every time I see a comment on the state of Tahoe I look wearily at my current install of Sequoia. I'll have to update at some point. But I'll hold out as long as I can...

I did it today. It took me thirty minutes to fix the networking because I couldn't get Little Snitch to uninstall since it didn't seem to be compatible. Basically I had to reboot in recovery mode to disable security features (csr) to uninstall Little Snitch (via systemextensionsctl). This is the worst update I've ever gone through on Mac, and I started using a Macintosh SE.

It's a bit unfair to complain about your OS being broken by incompatible software that modifies the kernel.

Re: Welcome (back) to Macintosh

#16

I've been running Tahoe since 26.2, after cowardly skipping 0 and 1. And... it's fine? Am I only using the happy path? Or are people just particularly confident about complaining about Tahoe after seeing everyone else do it. For sure it has glitches, but as far as I can tell, they're the same glitches that were in Sequoia. (If anyone at Apple is reading this, can you take a glance at your NFS client code? It does lik…

I haven't ran into nearly as many bugs as I've seen from others, but there is definitely a performance hit for me. The UI in general feels sluggish compared to sequoia.

I have two M4 Pro's w/ 24GB of RAM (one work, one personal). Work is on Tahoe, personal on sequoia and there's a really noticeable difference in overall UI responsiveness. It becomes even more pronounced when I hook up to my external display (32" 4k).

In a way it reminds me of the olden days of running KDE or Compiz with every fancy effect enabled but on an underpowered GPU. Yeah, it technically works, but it's not necessarily a fluid or enjoyable experience.

I have my own other nitpicks about liquid glass & the design (there's tons of papercuts here), but that doesn't necessarily impact stability.

Re: Welcome (back) to Macintosh

#17
post #9

Earlier quoted context omitted.

I did it today. It took me thirty minutes to fix the networking because I couldn't get Little Snitch to uninstall since it didn't seem to be compatible. Basically I had to reboot in recovery mode to disable security features (csr) to uninstall Little Snitch (via systemextensionsctl). This is the worst update I've ever gone through on Mac, and I started using a Macintosh SE.

It's a bit unfair to complain about your OS being broken by incompatible software that modifies the kernel.

It is a commonly used extension, which was restricted so that I could no longe remove it. What's more odd is that supposedly I was running the latest version.

Re: Welcome (back) to Macintosh

#19
post #8
post #3

Every time I see a comment on the state of Tahoe I look wearily at my current install of Sequoia. I'll have to update at some point. But I'll hold out as long as I can...

They've done something with the printer system in Tahoe. Brother removed support for native drivers on certain label printers on Tahoe (!!!) when you go searching you find other printer issues. Like, why. Why would you need to change the printer system? It works.. has worked for a very long time, there's no reasonable need to change it.

Oh man! I came here to complain about printing! I just discovered yesterday that you can no longer drag and drop print jobs from one printer to another. Apparently you can move a print job via some command line stuff but it just ended up deleting the jobs entirely. The only reasons I found this out is because the printer which had been working fine moments before just stopped working after replacing toner. No amount of deleting and re-padding the printer or power cycling either machine fixed it. One time the whole OS just froze and I had to force reboot. I spent a good chunk of the afternoon trying to get one 3 page document to print. To be fair, I haven’t had problems with this setup for 10+ years but when it went south it also went to the remote frigid corners of Antarctica.

Re: Welcome (back) to Macintosh

#20

I've been running Tahoe since 26.2, after cowardly skipping 0 and 1. And... it's fine? Am I only using the happy path? Or are people just particularly confident about complaining about Tahoe after seeing everyone else do it. For sure it has glitches, but as far as I can tell, they're the same glitches that were in Sequoia. (If anyone at Apple is reading this, can you take a glance at your NFS client code? It does lik…

I have a dirty confession to make too: I’ve been running Tahoe and Windows 11 on my devices, and both are working fine for the most part. If I ever switch to Linux desktop, it will be mostly out of boredom.
Post reply on HN