| ▲ | Networking changes coming in macOS 27(eclecticlight.co) |
| 149 points by pvtmert 5 hours ago | 124 comments |
| |
|
| ▲ | ndisn 3 hours ago | parent | next [-] |
| On an unrelated note, I use Time Machine and I’m surprised at how unpolished, not to say downright buggy, all the animations are. They used to look magical, but now they are a mess of elements popping on and off and things moving and then vanishing the next frame and so on. It looks like they kept changing Finder and Time Machine didn’t keep up; they kept fixing the bare minimum to have it compile and nothing more. |
| |
| ▲ | enaaem an hour ago | parent | next [-] | | Even the new app launcher. It takes 1-2 seconds to draw a bunch of icons. Scrolling is also choppy. This even happens on their newest machines. How this possible in 2026? | | |
| ▲ | cevn 25 minutes ago | parent [-] | | It isn't even centered on my monitor, looks like an intern wrote it. |
| |
| ▲ | amluto 3 hours ago | parent | prev | next [-] | | Even ignoring the lack of polish, the animations make it very hard to actually use Time Machine. | | |
| ▲ | adjejmxbdjdn 2 hours ago | parent | next [-] | | A couple of revisions in Time Machine was just fine. The UI was cute and fun if you wanted an older revision of a single file (especially since you could see previews of the file as you warped backwards). However, importantly, the snapshots were available in Finder itself so you could browse through the files you wanted and retrieve them. | |
| ▲ | Hamuko 2 hours ago | parent | prev [-] | | The worst feature of Time Machine is how it takes over every single display you have. Even though it only shows content on one screen, it feels the need to completely black out the others. | | |
| ▲ | xattt an hour ago | parent [-] | | I don’t know what kind of time machines you’ve been using, but typically everything changes outside all the portholes when you time travel. | | |
|
| |
| ▲ | jshier 3 hours ago | parent | prev | next [-] | | Classic Apple engineering. I would there is technically a "single responsible individual" assigned to Time Machine, but it covers the whole product, so the UI component falls by the wayside as the work on other products or the low level portion. | |
| ▲ | reaperducer an hour ago | parent | prev | next [-] | | On an unrelated note If you know it's unrelated, why try to derail this discussion? Why not start another? What's the point? Could it be that you only posted this in an active thread so it would get the most eyeballs, instead of being judged on its own merits? | | |
| ▲ | pnw_throwaway an hour ago | parent [-] | | It’s more tangential than unrelated. It’s how conversation naturally flows, and this is a discussion board. No need to fire up a new post. On another tangential note: you’re insufferable. If you’re like this in the real world, I can’t imagine you’ve got many people wanting to hold a conversation for very long. |
| |
| ▲ | giwook 3 hours ago | parent | prev [-] | | Makes sense since it hasn't been supported since 2018 lol | | |
| ▲ | kjuice1 3 hours ago | parent [-] | | Are you thinking of Time Capsule? Time Machine is fully supported and I use it every day on Tahoe. | | |
|
|
|
| ▲ | red_admiral 2 hours ago | parent | prev | next [-] |
| > will require connections to certain servers to be made using at least TLS 1.2 Seriously, no-one should still be using 1.1 since ... 5 years ago? It's not even the 1.2 -> 1.3 previous upgrade problems we're talking about. |
| |
| ▲ | ifwinterco an hour ago | parent [-] | | Yes this one seems unambiguously a good idea | | |
| ▲ | reaperducer an hour ago | parent [-] | | So I should have to e-waste my printer, scanner, and wireless card reader that only exist on my LAN, and that I connect to via a web interface just because… reasons? | | |
|
|
|
| ▲ | throw0101c 5 hours ago | parent | prev | next [-] |
| Time Capsule has been unsupported since 2018 (last shipped 2013): * https://en.wikipedia.org/wiki/AirPort_Time_Capsule I think there's some population of folks that have been doing NAS TM backups over AFP, and they'll now have to switch to SMB. |
| |
| ▲ | TimTheTinker 5 hours ago | parent | next [-] | | They discontinued sales in 2018, but continued to support Time Capsule backup over AFP through macOS 26 (Tahoe). | | |
| ▲ | GeekyBear 3 hours ago | parent [-] | | It's been more than a decade since they replaced AFP with SMB as the default protocol for file sharing, and they've been warning that AFP would be going away for years. |
| |
| ▲ | giantrobot 4 hours ago | parent | prev [-] | | Time Machine support is also dropping support over SMB1 so whatever new solution needs to support SMB2/3. | | |
| ▲ | stackskipton 4 hours ago | parent | next [-] | | SMB2 came out with Vista and SMB3 was Win8 so they are not new protocols either. | | |
| ▲ | winocm 4 hours ago | parent [-] | | That just ended up inadvertently reminding me, Windows Vista is actually almost old enough to be at the minimum legal drinking age in the US. Windows 8 is nearly a decade and a half old as well. Time really does fly. |
| |
| ▲ | Melatonic 4 hours ago | parent | prev | next [-] | | SMB1 has major security issues but even those ignored (which a lot of people on private home networks shouldn't be too worried about) it's also slow as hell on MacOS | | |
| ▲ | riffic 3 hours ago | parent [-] | | > people on private home networks shouldn't be too worried about philosophically I would beg to differ about any premise assuming we can trust the castle and moat model. Even on home networks. |
| |
| ▲ | wtallis 4 hours ago | parent | prev [-] | | Where "new" in this case could be a NAS running Samba from 2011? Samba added official support for Time Machine much later, but I think it was possible on earlier versions with some extra steps. | | |
|
|
|
| ▲ | pvtmert 5 hours ago | parent | prev | next [-] |
| Although TimeCapsule is more than decade old, it serves nicely with TimeMachine (automatic backups). Sad to see that going away permanently for Apple Silicon. |
| |
| ▲ | ryandrake 4 hours ago | parent | next [-] | | "Dropping support for things just because they are old" is typical commercial software behavior. I can run the latest Linux kernel and still have access to an internal floppy disk drive if I wanted to, yet billion dollar companies can't seem to manage to support 10 year old stuff. I still am sore from when I "upgraded" macOS and suddenly support for my 1080i TV was gone. Yesterday it worked fine, today it's gone. All because they can't be bothered to maintain a code path. | | |
| ▲ | _verandaguy 4 hours ago | parent | next [-] | | The economics make the reasoning obvious, though. With closed source IP, every bit of support, from bug fixes, to feature requests, to compatibility fixes to integrate with newer mainline/foundational tooling, costs money. With open source projects (and in particular ones like Linux where there's a huge number of contributors and interested parties), support for would-be niche facilities can keep going as long as there's someone with the knowledge and spare time to do it. | | |
| ▲ | TheJoeMan 2 hours ago | parent | next [-] | | There's somewhere in the ballpark of 166,000 employees at Apple, just unfathomable scale [1]. It is not unreasonable to ask that someone specific is responsible for each particular small feature and ensuring it keeps working. Trying to apply an economic analysis to such a "free as in beer" operating system does not seem to work well. Consider the question of "how many small holes can you have in your wooden sailing ship"? [1] https://stockanalysis.com/stocks/aapl/employees/ | | |
| ▲ | laserlight an hour ago | parent | next [-] | | Not that it impacts your argument significantly, but for the sake of completeness, Apple employs a huge number of retail employees. | |
| ▲ | akerl_ an hour ago | parent | prev [-] | | It’s not unreasonable to ask but they can and are saying “no”. |
| |
| ▲ | lenerdenator 31 minutes ago | parent | prev | next [-] | | Ideally, at a certain point, you'd have some sort of upstream FLOSS project where you could let John Q. Public do that sort of low-level, maintenance-only stuff, while the proprietary "value adds" are closed source, until it becomes financially attractive to FLOSS them. IIRC, that could exist for MacOS in the form of Darwin. | |
| ▲ | reaperducer an hour ago | parent | prev [-] | | The economics make the reasoning obvious, though These arguments fall apart when you remember that Apple has several trillion dollars at hand. It's not some shoestring startup. |
| |
| ▲ | tracker1 2 hours ago | parent | prev | next [-] | | Ironic, considering Linux is dropping a LOT of old devices from 7.1 | | |
| ▲ | yjftsjthsd-h 2 hours ago | parent [-] | | It's my understanding that those are (mostly?) devices where they legitimately have reason to believe there are zero users. In particular, there's a pattern where someone will discover that Linux has a driver that hasn't actually worked for a long time, and nobody's complained, so then they remove it. | | |
| ▲ | tracker1 2 hours ago | parent [-] | | I'm not suggesting they keep it all... just ironic as a statement considering Linux is literally removing a bit lately... <= 486, the bus drivers for mice, etc. I'm mostly okay cleaning out a lot of legacy and unsupported devices. In some ways, and for people who want to support really old hardware it may not be great, but they're most likely stuck on older versions for other reasons. | | |
| ▲ | yjftsjthsd-h 30 minutes ago | parent | next [-] | | I don't think it is ironic, though; Linux isn't "Dropping support for things just because they are old", it's dropping unused things when they cause code quality problems. That's rather different than features being dropped because the vendor doesn't want to bother supporting them even though they still worked and have active users. | |
| ▲ | ryandrake an hour ago | parent | prev [-] | | Absolutely--Linux is by no means perfect. |
|
|
| |
| ▲ | Ar-Curunir 3 hours ago | parent | prev | next [-] | | Just this week we've seen Linux talking about dropping support for some older hardware precisely because attacks against it were becoming easier with LLMs. | | |
| ▲ | joe_mamba a few seconds ago | parent [-] | | Do you have a source? I want to read more about it. Because I noticed my old Core 2 Quad PC with Nvidia 8600GT doesn't boot with any linux newer than Kernel 6.1 even though I can get Windows 11 to boot on it. So the myth around "Linux is great for old PCs", highly depends on what HW you have. |
| |
| ▲ | retired 3 hours ago | parent | prev | next [-] | | macOS Tahoe still has floppy drive support. | | |
| ▲ | ryandrake 2 hours ago | parent [-] | | Really? Like actual internal floppy drives, and not just USB floppy drives (which even Windows still supports)? I actually wouldn't expect macOS to support actual floppy drives since the OS's list of supported devices doesn't include any that shipped with floppy drives. The fact that I cannot install the latest macOS on any devices older than 2019 is a related, but separate problem. | | |
| ▲ | nxobject an hour ago | parent | next [-] | | In this case, what would internal floppy drive mean? The last Macs with floppy drives (I think Old World G3s?) used a custom Apple controller, integrated into the chipset, with a bespoke 20-pin cable. | |
| ▲ | retired an hour ago | parent | prev [-] | | USB floppy drives indeed. |
|
| |
| ▲ | wang_li 3 hours ago | parent | prev [-] | | > "Dropping support for things just because they are old" is typical commercial software behavior. You are deluding yourself if you think open source folks are better. You can't compile and run a modern version of GCC on Solaris 10 on SPARC, for example. And we just had a story here last week about removal of bus mouse support. It's only a mild exaggeration to say that lots of folks will check the commit activity on github and of a project doesn't have commits this week it should be banned from the internet and the universe. Then you have the problem that many dev tools are not forward compatible. CMake is a huge issue. An ubuntu system from 2020 has CMake on it, but it won't compile anything that uses CMake that was released in recent years because the cmakefiles are incompatible. | | |
| ▲ | a1o an hour ago | parent | next [-] | | CMake is a bad example, you can build latest CMake and run it on Debian Jessie. It will work perfectly. CMake is the thing you can build on really old compilers. | |
| ▲ | realusername 3 hours ago | parent | prev [-] | | Open source is better because as long as you have a single developer caring to maintain the device, it will still be there. Bus mouse support isn't removed because it's old but because it's been broken since 2015 and nobody noticed. |
|
| |
| ▲ | goalieca 5 hours ago | parent | prev | next [-] | | Given the mtbf of disks, I wouldn’t risk doing backups on a device discontinued in 2018. | | |
| ▲ | swiftcoder 5 hours ago | parent | next [-] | | It may not be the easiest surgery in the world, but you can replace the hard drive in a Time Capsule. You'll probably want to replace the power supply too after this much time | |
| ▲ | kgwgk 5 hours ago | parent | prev [-] | | Disks can be replaced. |
| |
| ▲ | sleepybrett 5 hours ago | parent | prev [-] | | wasn't it capped at 3tb? is the drive swappable to something bigger? They discontinues them in 2018, the wifi in them is old, single disk (no raid).. better to just pick up a multidrive nas or use cloud backups. What we should be asking for is timemachine backends for cloud providers. | | |
| ▲ | TimTheTinker 5 hours ago | parent [-] | | It's not "officially" supported, but iFixit has a guide for swapping the drive on a time capsule. I used mine with a 4TB drive for years with no trouble. | | |
| ▲ | sleepybrett 4 hours ago | parent [-] | | Sure, but still just a single drive. My old trusty readynas should still work i think.. probalby. Supports smd for time machine and smb3 generally. If it doesn't I might finally be pushed onto a nas that isn't discontinued. | | |
| ▲ | bananamogul 4 hours ago | parent | next [-] | | I had an early ReadyNAS that was a champ for years. I wonder if the fact that it was based on SPARC had anything to do with its longevity. | |
| ▲ | iAMkenough 3 hours ago | parent | prev [-] | | From a risk assessment standpoint, I’ve seen my Time Machine backups corrupted much more frequently than I’ve experienced drive failure. Happened with both my Time Capsule and then my Synology RAID. It’s a “nice to have” automatic backup, but not a primary backup destination for me. |
|
|
|
|
|
| ▲ | JumpCrisscross 5 hours ago | parent | prev | next [-] |
| "...if you have an Apple silicon Mac and AFP support is dropped from macOS 27, that would leave you unable to upgrade without replacing your network storage." How big is this market? I'm not saying vibe code a product, but... |
| |
| ▲ | bayindirh 5 hours ago | parent [-] | | That "replacement" is not always full-on hardware. I have colleagues who are running AFP on BSD for continuous backups on their systems, and they have to reconfigure something new to be able to continue backing up their systems. | | |
| ▲ | trillic 4 hours ago | parent | next [-] | | I use this for networked Time Machine backups for multiple Macs in my household. Works just as well over tailscale VPN. https://wiki.archlinux.org/title/Netatalk | | |
| ▲ | snapetom 15 minutes ago | parent | next [-] | | One of my COVID projects was to set up a networked Time Machine backup on Raspberry Pi. Every single one of the blogspam sites (lifehacker, howtogeek, etc.) told you to use AFP/HFS+/Netatalk. I had so many problems with this. Time Machine would work well the first few times and then slow to a crawl. If there was a power outage, look out. The whole thing would be corrupted. It wasn't the network. FTP and scp worked just fine. Eventually I found one blog that told you how to do it with SMB and ext4. It was that site that I learned about the much malignment of AFP and HFS+. SMB/ext4 worked like a charm. Six years later and not a single hiccup. | |
| ▲ | wang_li 3 hours ago | parent | prev [-] | | Also works for System 7 based Macintoshes. In case you got frozen in a glacier in 1991. | | |
| ▲ | jshier 3 hours ago | parent [-] | | Nah, classic Macintosh OSes aren't compatible with modern AFP. | | |
| ▲ | wang_li 2 hours ago | parent [-] | | They are compatible with netatalk though. The project split between version 2 and 3, but in recent releases they folded them back into a single thing. Current netatalk releases support all versions of AFP. |
|
|
| |
| ▲ | JumpCrisscross 5 hours ago | parent | prev [-] | | > That "replacement" is not always full-on hardware Oh, I was thinking only of software. Apple dropping AFP in the OS doesn't mean it can't work at all. | | |
|
|
|
| ▲ | post-it 3 hours ago | parent | prev | next [-] |
| Why is it that Apple products attract blogspam titles? > Networking changes coming in macOS 27 And yet: > This year, with just over six weeks to go before that first beta of macOS 27, we already have two warnings of what might be coming. > It repeated those warnings with macOS Sequoia 15.5, but still hasn’t confirmed when AFP will be lost. > Although Apple carefully avoids being too specific, it warns that this change could come “as early as the next major software release”, |
| |
| ▲ | pvtmert 2 hours ago | parent [-] | | I originally added a different title: Apple is dropping AFP/TimeMachine support in macOS 27. It seems like somehow got overwritten to the original title of the post. Nevertheless, knowing Apple so far, unless _some_ large-enterprise~y customer comes and objects, they will drop the support. We already know Intel support is dropping. Why not clean up rest of the things from the kernel and the userspace? | | |
|
|
| ▲ | TimTheTinker 4 hours ago | parent | prev | next [-] |
| Ubiquiti is really taking up the slack in some areas Apple has abandoned. I bought a UNAS-2 (and a couple of 12 TB IronWolf Pro drives) a few months ago when the "time capsule will not be supported in a future version of macOS" warning first appeared. It has been outstanding alongside the rest of my UniFi setup, and perfectly supports Time Machine backups. The UniFi Identity macOS app means my family's computers always stay authenticated/connected and my wife & kids don't have to do anything to make Time Machine just work. If you're a power user who loves the Apple aesthetic and you already have a UniFi setup at home, you'll feel right at home switching from Time Capsule to a UNAS. |
| |
| ▲ | jshier 3 hours ago | parent | next [-] | | What format is the destination drive? My ideal is APFS clone backups to a remote drive, but I don't know if there are any network setups that support that, even though you can do it to a local drive. | | |
| ▲ | nijave an hour ago | parent [-] | | I was under the impression that's how SMB TimeMachine backups work currently |
| |
| ▲ | Melatonic 4 hours ago | parent | prev [-] | | Have you tried it also working to backup files from Linux and windows machines ? Was hoping for a good mixed backup solution and I'm getting Ubiquiti would deliver here. Also why the 12TB ironwolf drives specifically ? Personally I always was a fan of buying true enterprise (the ones designed for "online" or near line storage) but sometimes specific models and sizes of random drives do very well in Backblaze testing | | |
| ▲ | TimTheTinker 2 hours ago | parent [-] | | I don't have any Linux/Windows machines, but I've seen nothing that would dissuade me from using it when I eventually migrate my current laptop to Asahi Linux. As for IronWolf Pro drives, I chose them because they seem to have similar longevity to enterprise drives with less noise (my equipment is in a closet under the stairs). |
|
|
|
| ▲ | amelius 3 hours ago | parent | prev | next [-] |
| Can't they hire an extra dev per abandoned project to not abandon it? |
| |
| ▲ | Someone1234 3 hours ago | parent [-] | | You greatly under-estimate how much work it is to maintain old code, particularly to maintain in securely. AFP and Time Capsules add attack vectors to the OS, which can be targeted even when few users actively using them. One dev could keep both basically functional, but to what end? User counts are already small, and people that aren't using them are still exposed by their mere existence. Shrinking or removing code, in my experience, is one of the biggest single wins you can have in software development. Less to test, less to update, less to secure. | | |
| ▲ | applfanboysbgon 2 hours ago | parent | next [-] | | Yes, writing and maintaining less code is great for a developer. We can follow this to the logical extreme and marvel at how easy it is to write and maintain a program whose only function is to print "hello, world" to the console. Nevermind the users, what do they matter? | | |
| ▲ | Someone1234 3 minutes ago | parent [-] | | By the very nature of assigning development time to these antiquated features, you're assigning them away from other features, bug fixes, or requests that may have a larger user reach. Development is a finite resource, the argument here is to allocate them to hard-to-secure, outmoded, replaced, technology instead of anything future relevant. It doesn't make sense. |
| |
| ▲ | zimpenfish 3 hours ago | parent | prev [-] | | > You greatly under-estimate how much work it is to maintain old code, particularly to maintain in securely. cf Linux removing old network drivers this week for the same reason (without the hand-wringing that this Apple announcement is getting!) | | |
| ▲ | saghm 2 hours ago | parent [-] | | Is the code that Apple is removing support for open source? The Linux drivers could at least plausibly be picked up and used by someone who really wants to, so it doesn't seem to be a fair comparison |
|
|
|
|
| ▲ | shantara 4 hours ago | parent | prev | next [-] |
| >Apple made SMB its primary file-sharing protocol in OS X 10.9 Mavericks, over 12 years ago… …and yet SMB support in macOS remains slow and buggy to this day. I tried all combinations of server-side settings and obscure plist tweaks to make SMB navigation and search work as fast as they do on my Linux machine out of box before giving up. It is very obviously not a priority for their services revenue, so there’s no incentive for fixing any of the long standing problems. |
| |
| ▲ | somat 6 minutes ago | parent | next [-] | | How is nfs on mac? Not really equivalent, I know, but if smb is that bad I am curious about alternatives. | |
| ▲ | yobert 4 hours ago | parent | prev | next [-] | | I found something fun last week--- Apparently if you use Adobe tools, there is a sync plugin they install for finder that can cause big issues with SMB shares. Might help you if you have that! | | |
| ▲ | catoc 2 hours ago | parent [-] | | Would you have any more info?
I have both: adobe synctool + issues with smb shares |
| |
| ▲ | realityfactchex 4 hours ago | parent | prev | next [-] | | > SMB support in macOS remains slow and buggy to this day. I tried all combinations of server-side settings and obscure plist tweaks to make SMB navigation and search work as fast as they do on my Linux machine out of box before giving up. It is very obviously not a priority for their services revenue That's where my thoughts went, too. I can make SMB "better" but not "great" usually, but it's annoying to have to look up and apply, and still have things not optimal. Just in case, IIRC I find this the most useful: defaults read com.apple.desktopservices DSDontWriteNetworkStores
defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool TRUE
But surely some of the other tweaks that LLMs suggest may help, too. | |
| ▲ | p_ing 3 hours ago | parent | prev | next [-] | | Apple has their own implementation of SMB in macOS and it's one of the worst out there. Dropping connections, can't re-establish connections automatically after sleep, and performance issues. Why they didn't keep Samba (licensing, probably) is beyond me. | |
| ▲ | traderj0e 3 hours ago | parent | prev | next [-] | | Yeah, can't remember the last time I even bothered with SMB because it's so buggy. Usually I don't need filesystem behavior, I'll just push/pull files over SSH. | | |
| ▲ | eastbound 2 hours ago | parent [-] | | I regret the difficulty of mounting an SSH connection as a filesystem. It requires Fuse and giving permissions to the kernel. | | |
| ▲ | traderj0e 2 hours ago | parent [-] | | I used to do that a lot in some old versions of OS X, but then MacFUSE got abandoned and picked up as osxfuse, then that broke then got fixed repeatedly with several Mac updates, and I gave up. |
|
| |
| ▲ | kstrauser 4 hours ago | parent | prev [-] | | I can pull about 700MB/s off my NAS over a 10Gb link. I wouldn’t exactly call it slow. | | |
| ▲ | Melatonic 4 hours ago | parent | next [-] | | In a corporate environment SMB3 on MacOS was lagging Windows and Linux big time (at least a few years ago when I tested). How's the latest to your NAS? Are those single large files or many small files ? | |
| ▲ | j16sdiz 4 hours ago | parent | prev [-] | | I think SMB is quite chatty -- if you have lots of small files, you can get quite slow. | | |
| ▲ | p_ing 3 hours ago | parent | next [-] | | That was SMBv1. Not SMB of today. | | |
| ▲ | brigade 3 hours ago | parent [-] | | Still true for extended attributes, which Finder and Spotlight love to query. |
| |
| ▲ | WorldPeas 4 hours ago | parent | prev [-] | | ...and don't even get me started on locking, if many people write to one file you're on borrowed time |
|
|
|
|
| ▲ | mushufasa 4 hours ago | parent | prev | next [-] |
| Wouldn't the TimeCapsules still work over wired connections, just like any other hard drive, even if the networking AFP protocol support is dropped? |
| |
| ▲ | ibejoeb 3 hours ago | parent [-] | | No, afp is application layer. It doesn't matter how the device is connected at layers 1 or 2. You could shuck the disk and use it directly, though. Then it's just a disk, not a time capsule. |
|
|
| ▲ | apparatur 5 hours ago | parent | prev | next [-] |
| Next: macOS iCloud backups and the eventual deprecation of local Time Machine backups altogether. More services revenue! |
| |
| ▲ | GeekyBear 5 hours ago | parent | next [-] | | Changing out the network protocol used for local network backups isn't the same thing as getting rid of local network backups. TFA: > Apple made SMB its primary file-sharing protocol in OS X 10.9 Mavericks, over 12 years ago, and has repeatedly told us that support for its predecessor AFP will be removed in the future. | | | |
| ▲ | angott 4 hours ago | parent | prev | next [-] | | I don’t think they’re going to drop support for local backups any time soon. There are lots of enterprise customers relying on Time Machine who will never switch to iCloud. TM can also be configured via MDM settings and is a really common solution for Mac IT administrators, so it would take ages to deprecate it. | | |
| ▲ | apparatur 4 hours ago | parent [-] | | "There are a lot of enterprise customers using Xcode server". And poof, it's gone and there's now only the Xcode cloud service. It would not take ages. It would take a single release which no longer supports it. Complaints? Keep using the old one or subscribe. | | |
| ▲ | plorkyeran 4 hours ago | parent | next [-] | | I am fairly confident in saying that approximately zero enterprise customers used Xcode server. It was extremely limited and targeted at small shops which didn't see the need for a proper CI setup but had an extra machine sitting around to run builds on. | |
| ▲ | pvtmert 2 hours ago | parent | prev [-] | | I think they switched to cloud because; - BigCo already is a zero-sum deal, they use Xcode-cloud as a service, which runs back on their servers anyway... (Google, Amazon, Azure, etc) - It was not a long-standing product. Introduced somewhere around 2016~ish if I remember correctly. Only lasted a few major releases. Easier to kill than an established one (ie. TimeMachine) |
|
| |
| ▲ | Aurornis 4 hours ago | parent | prev | next [-] | | They switched the default protocol from AFP to SMB a long time ago. They aren’t deprecating Time Machine. The old protocol is being removed. The old protocol hasn’t worked well for a long time, at least in my experience | |
| ▲ | bananamogul 3 hours ago | parent | prev | next [-] | | People have been asking for iCloud macOS backups since iCloud was introduced. It would be very popular. I'm not sure why Apple doesn't offer this, because it's easy revenue. | | |
| ▲ | post-it 3 hours ago | parent [-] | | Because people will fill their iClouds. An important value proposition of iCloud is that customers pay for more space than they need. Time Machine grows to fill all available space. | | |
| ▲ | pmontra an hour ago | parent [-] | | They could sell a separate service for Time Machine backups. I'm not an Apple customers so I don't know if it makes sense, but they could make customers pay X times the last N days in the backup plus Y times a number M of snapshots in the past. |
|
| |
| ▲ | bayindirh 5 hours ago | parent | prev | next [-] | | As long as you can migrate/recover your Mac from your TM backup, I guess that this scenario won't happen. | |
| ▲ | latchkey 3 hours ago | parent | prev | next [-] | | I like having control over my backups. I've been working on improving an open source menubar that wraps restic. Right now it is a bit rough around the edges, but my plan is to have a simple onboarding experience for various backend services like B2. Over the weekend, I added a "Smart backups" feature that uses all the same directories that the backblaze menubar app and timemachine excludes. This was the primary missing feature for me. It even generates and backups your Brewfile... https://github.com/lookfirst/ResticScheduler | |
| ▲ | AlexandrB 5 hours ago | parent | prev | next [-] | | The story of TimeMachine is a tragedy: a revolutionary feature that made backups accessible for normal people allowed to lie fallow for a decade or more until it's as annoying and unreliable as anything else. I now use Carbon Copy Cloner to avoid the TM headaches. | | |
| ▲ | FireBeyond 5 hours ago | parent [-] | | I never found it to be overly reliable. It was reliable... for a while. Then would silently fail/stop working, or just tell you that it had stopped working and that whatever you had in it was no longer accessible. And then I went to Acronis True Image backing up to my Synology NAS, but that became unreliable too - oftentimes when I'd go to do a restore, the client would crash trying to read the catalog. So, like you... CCC nightly to my Synology, with a Snapshot rotation on it - snapshot the previous night's backup at 8pm, and then kick off that night's backup at 11pm. | | |
| ▲ | tonyedgecombe an hour ago | parent | next [-] | | It was unreliable over SMB. Not surprising when you look at what it was doing. It would create a virtual drive on the share, map that and backup to it. There was too much going on for that to be reliable. | |
| ▲ | apparatur 4 hours ago | parent | prev | next [-] | | For me it was a key DB file inside the Photo library which Time Machine omitted from all backups and prevented me from restoring the library. Not fun. | |
| ▲ | AlexandrB 3 hours ago | parent | prev [-] | | Yeah, you may be right. I have fond memories of it from around 2008, but those might be from the initial experience and not all the "you need to recreate your back from scratch" errors that would crop up after a while. |
|
| |
| ▲ | semiquaver 4 hours ago | parent | prev | next [-] | | This is reflexive and ill-considered FUD. Be better. | | | |
| ▲ | walrus01 5 hours ago | parent | prev [-] | | > Next: macOS iCloud backups and the eventual deprecation of local Time Machine backups altogether. More services revenue! The "new computer" out of box account creation and first sign in experience on both Windows 11 and MacOS are clearly designed to drive end users towards perpetual for life monthly recurring subscriptions for (Microsoft 365 Personal, OneDrive, iCloud storage, etc). Imagine the difficulty for the ordinary non technical person (absolutely not a stereotypical HN reader) ever being able to stop paying for iCloud when they have 600GB+ of their family photos and videos and stuff backed up to it. | | |
| ▲ | AlexandrB 3 hours ago | parent [-] | | > Imagine the difficulty for the ordinary non technical person (absolutely not a stereotypical HN reader) ever being able to stop paying for iCloud when they have 600GB+ of their family photos and videos and stuff backed up to it. To be fair, non technical folks get a lot of value from this scheme too. I can't imagine many of my relatives successfully juggling backups and external media in a way that would actually keep their content safe in case their phone is lost/stolen/destroyed. Right now the monthly fees for this stuff are rather modest, but I could see a future where the dominant players lock out competitors and use their market position to raise prices significantly. |
|
|
|
| ▲ | StillBored 4 hours ago | parent | prev [-] |
| Does the mac still lack a SMB/CIFS browser? I was shocked years ago that the mac, famous for its early network peer discovery and zeroconf and all, couldn't present a list of SMB servers and shares despite that kind of function being around forever on every other platform in existence. |
| |
| ▲ | zdw 4 hours ago | parent | next [-] | | macOS has a Network location in the sidebar that will show other SMB devices discovered on the network. | |
| ▲ | hamdingers 4 hours ago | parent | prev | next [-] | | Must have been a lot of years ago since Samba was introduced in Jaguar (2002), and SMB replaced AFP as the default for file sharing as of Mavericks (2013). | |
| ▲ | slackfan 4 hours ago | parent | prev [-] | | It's had it since before version 10.4, though it wasn't fantastic, I'll give you that. |
|