Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Welcome (back) to Macintosh

take.surf

Post reply on HN
Print view View original

31–40 of 276 posts

Re: Welcome (back) to Macintosh

#31

Post by card_zero »

nl wrote: post #13
LeoPanthera wrote: post #5

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.

So are you saying the long list of bugs don't actually happen?

Re: Welcome (back) to Macintosh

#32

Post by skibble »

dewey wrote: post #10
giobox wrote: post #2

I genuinely view Time Machine as abandonware at this stage, Apple haven't really invested in it for many years and I would recommend a lot of other third party backup solutions first.

It's really sad. When this was introduced (With Lion I believe?) it was such a cool feature to demo to people that didn't have much exposure to Macs yet at that time. Just deleting and restoring a file on the Desktop with the "Space UI" and backups just being there and working without buying complicated backup software was a genuine peak macOS moment. Now I'm barely using it as every few months I'm prompted to just d…

I have set up Time Machine backups for literally hundreds, if not thousands of people in a support role over many years and have hardly ever witnessed this happening. It's one thing to say you may have had to do this once or twice in a decade or the like, but every few months is ridiculous and speaks to some other underlying issue with your setup, like a quietly failing drive or bad cable, etc.

I'm not one of these 'it hasn't happened to me, ergo it's impossible people'. I completely think that many of the design elements of Tahoe are a horrendous regression versus even Sequoia, but I think asserting that Time Machine is completely broken in the shipping version of macOS is a bold statement that deserves a bit of pushback, even among the fire raging in a lot of other places in macOS!

Re: Welcome (back) to Macintosh

#33

Post by hedgehog »

freetonik wrote: post #28

My partner’s iMac recently died (seemingly the Radeon graphics card had failed, which is not uncommon on 2017 model). It was frustrating to find out that Time Machine was not operational for 8 last months. It was always connected. There were zero indications of any issues. It just stopped backing up at some point. The disk had enough space. In the past I had problems with network attached Time Machine destinations, b…

I don't know what's happened to Time Machine, with the capabilities available in APFS etc it should be much better if anything. But it's not. Thankfully the failure mode I've experienced didn't lead to data loss but I definitely don't trust it any more.

Re: Welcome (back) to Macintosh

#34

Post by hedgehog »

dewey wrote: post #10
giobox wrote: post #2

I genuinely view Time Machine as abandonware at this stage, Apple haven't really invested in it for many years and I would recommend a lot of other third party backup solutions first.

It's really sad. When this was introduced (With Lion I believe?) it was such a cool feature to demo to people that didn't have much exposure to Macs yet at that time. Just deleting and restoring a file on the Desktop with the "Space UI" and backups just being there and working without buying complicated backup software was a genuine peak macOS moment. Now I'm barely using it as every few months I'm prompted to just d…

Leopard, which means I've been using it for almost 20 years. The first ten were pretty good.

Re: Welcome (back) to Macintosh

#35

Post by nsbk »

ordinaryradical wrote: post #6

This is going to be remembered as a comical fumble, in my view. I was fully locked-in to the ecosystem, the phone, the services, the TV, and I am looking for the exits. I’m starting to parallelize to software which will play well on Linux, and when I’m feeling ready (or miserable enough) I will not be looking back. The macOS exodus will be like Hemingway’s line about bankruptcy: very slowly and then all at once.

I’m right where you are. Very happy Apple customer since my first PowerBook G4. Currently have an M1 Max, an iPhone 17 Pro, the iPad Pro, HomePod, Apple TV, and Watch Ultra.

All the _just works_ feeling and reliability seem to be gone. Tahoe is so unstable that I now restart the Mac every day, when in the past it happened on software updates only. Apple Music is another huge mess, I can’t comprehend how can it be so unreliable.

Looking for exits as well and kind of looking forward to migrating to Graphene OS, self-hosted Immich, and Navidrome

Re: Welcome (back) to Macintosh

#36

Post by temp0826 »

LeoPanthera wrote: post #5

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'm usually in linux on my (2019?) mbp but have had to use macos for some stuff lately (so I'm not exactly tuned in to it and using it hard all day), but I don't see what the problem is tbh and haven't run into anything slowing me down or inducing the rage that I read here.

Re: Welcome (back) to Macintosh

#37

Post by freetonik »

hedgehog wrote: post #33
freetonik wrote: post #28

My partner’s iMac recently died (seemingly the Radeon graphics card had failed, which is not uncommon on 2017 model). It was frustrating to find out that Time Machine was not operational for 8 last months. It was always connected. There were zero indications of any issues. It just stopped backing up at some point. The disk had enough space. In the past I had problems with network attached Time Machine destinations, b…

I don't know what's happened to Time Machine, with the capabilities available in APFS etc it should be much better if anything. But it's not. Thankfully the failure mode I've experienced didn't lead to data loss but I definitely don't trust it any more.

Luckily I had Backblaze backup set up on our machines. In addition, this older iMac can still be booted up in Target disk mode, i.e. acting like an external drive. So I could salvage all data.

Another funny thing is that Mac’s built in diagnostic mode, after running for good 20 minutes, proclaimed there were no issues with the system. Even though it was clearly failing in the graphics department, even when booting into an installer usb drive (or even a Linux live mode).

Re: Welcome (back) to Macintosh

#39

Post by dewey »

skibble wrote: post #32
dewey wrote: post #10

Earlier quoted context omitted.

It's really sad. When this was introduced (With Lion I believe?) it was such a cool feature to demo to people that didn't have much exposure to Macs yet at that time. Just deleting and restoring a file on the Desktop with the "Space UI" and backups just being there and working without buying complicated backup software was a genuine peak macOS moment. Now I'm barely using it as every few months I'm prompted to just d…

I have set up Time Machine backups for literally hundreds, if not thousands of people in a support role over many years and have hardly ever witnessed this happening. It's one thing to say you may have had to do this once or twice in a decade or the like, but every few months is ridiculous and speaks to some other underlying issue with your setup, like a quietly failing drive or bad cable, etc. I'm not one of these '…

This is a very common error case, more common with storing the backup on a network share (Wifi / Ethernet doesn't matter). If you look for "Time Machine must erase your existing backup history and start a new backup to correct this." you'll find a lot of references for this problem.

To be clear, I'm not saying it's Tahoe related, it has been there for many years.

Post reply on HN