* 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.
1. When I benchmarked it, AFP was significantly faster than SMB. Both with SMB2 and SMB3. Even when transport encryption was turned off.
2. On SMB2+, symlinks created by the client are not real symlinks. They're "Minshall+French" links which only look like symlinks to other SMB2+ clients. To the server and NFS mounts they look like flat files with the target path encoded in them.
3. It exposes a different precision for certain timestamps. Software that uses this metadata to decide whether a file needs to be updated will see almost every file as needing a resync.
It's been a year or two since I checked the status of these. The situation may have improved since last I looked.
Windows 8 is nearly a decade and a half old as well.
Time really does fly.
* https://www.samba.org/samba/history/samba-4.8.0.html ("vfs_fruit")
* https://wiki.samba.org/index.php/Configure_Samba_to_Work_Bet...
philosophically I would beg to differ about any premise assuming we can trust the castle and moat model. Even on home networks.
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.
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.
With that said, kernel maintainers have recently indicated that some unused subsystems are likely to be removed soon, as AI is now finding (real) security vulnerabilities in them that nobody is willing to fix.
IIRC, that could exist for MacOS in the form of Darwin.
These arguments fall apart when you remember that Apple has several trillion dollars at hand. It's not some shoestring startup.
Because I noticed my old Core 2 Quad PC with Nvidia 8600GT that my parents use as their email and Facebook machine, 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.
> There are still some people who need to run 32-bit applications that cannot be updated; the solution he has been pushing people toward is to run a 32-bit user space on a 64-bit kernel. This is a good solution for memory-constrained systems; switching to 32-bit halves the memory usage of the system. Since, on most systems, almost all memory is used by user space, running a 64-bit kernel has a relatively small cost. Please, he asked, do not run 32-bit kernels on 64-bit processors.
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.
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.
Bus mouse support isn't removed because it's old but because it's been broken since 2015 and nobody noticed.
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.
How big is this market? I'm not saying vibe code a product, but...
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.
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.
Oh, I was thinking only of software. Apple dropping AFP in the OS doesn't mean it can't work at all.
Relevant to the discussion is that the project comes with an AFP client as well. I have no experience with the client but I've used the Netatalk server for more than 15 years.
This runs Samba 4 on the Apple Time Capsule.
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.
(Yes, this article is about an extension of the deadline. I don't remember what happened after that.)
I got Samba 4 working on Apple Time Capsules: https://github.com/jamesyc/TimeCapsuleSMB
If you have a legacy Time Capsule you'd rather not e-waste, you can try this out. Note that this is very much beta quality software, so don't expect it to work on all configurations.
Edit, but don't take this as me saying I like the current state of macOS. There are plenty of weird edge cases I wish they'd fix, but on the whole the OS works fine for me.
Enshittification. When you're an ecosystem monopoly, people are forced to buy your shit no matter how bad it gets.
I would (grudgingly) accept this argument for iOS, but for Mac OS it doesn't make any sense.
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.
It's like that because people are still buying. Even for the ridiculous prices Apple asks for.
So why would Apple actually care? They get away with this "quality", so from a business standpoint there is simply nothing that needs investments or even just attention.
It's a race to the bottom. Like everywhere else. That's simply how the system which people created works.
I've been paying for iCloud storage since I don't know when.
- Very slow, even on an M4.
- 3rd party devices are often unreliable. Not directly Apple's fault, but the lack of certification process hurts
- SMB extensions: In order for an SMB server to support Time Machine, it must support Apple's AAPL extensions to SMB (my understand of this my be a bit uncorrect)
- Network device connecting is separate from Time Machine device connecting. This causes an inconsistent UX.
- Not possible to browse a backup. You can only view file or folder's backup over time. In other words, you can scroll through time but you can't browse a single backup (point in time). This requires using 3rd party tools like BackupLoupe
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?
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.
How is this a criticism? Seems smart to me.
https://news.ycombinator.com/item?id=9026192
https://www.macrumors.com/2015/06/30/apple-releases-os-x-10-...
I just hope they won't break anything they don't need to break (which is more concerning usually) and that they won't drop other things that do make sense to keep until transitioned properly (eg. OpenGL as one example)
> 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”,
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?
The facts: Apple put a warning in macOS 15.5 that AFP support might be dropped in the future.
The claim: AFP support will be dropped in macOS 27.
I just do not see how you get from the facts to the claim. This is just complete speculation.
…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.
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
Why they didn't keep Samba (licensing, probably) is beyond me.
Correct, Apple has dropped everything that switched to GPLv3 which includes newer versions of bash, samba, etc.
Not really equivalent, I know, but if smb is that bad I am curious about alternatives.
The Finder is really an horrible piece of sh*t of software, slow as hell, doesn't provide the most basic information[1], and, of course, doesn't work properly when browsing network shares either SMB or NFS.
[1]virtually all common file browsers (Windows Explorer, Gnome Nautilus, KDE dolphin) displays at all times : the number of files in the current folder, their size, the number of files selected, their size; also all but the Finder have a "recent files" section that actually contains the latest files used, while the Finder displays a completely random selection of recent files, but never the most recently used ones.
How's the latest to your NAS? Are those single large files or many small files ?
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.
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.
cf Linux removing old network drivers this week for the same reason (without the hand-wringing that this Apple announcement is getting!)
I mean, it's basically just like a time machine backup plus, uh, a little bit of some older files that I don't want to keep on my main Mac.
seems like any NAS would take way more space than I would love to. I suppose one alternative would be actually getting some kind of like Beelink PC and then maybe setting up a proper home server, moving some of my side projects in there, running plex from it. The problem is that the current ram prices, it's a surprisingly expensive solution.
You could shuck the disk and use it directly, though. Then it's just a disk, not a time capsule.
Look, my setup works for me. Just add an option to re-enable AFP [2].
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.
- 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)
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
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...
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.
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.
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.
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.
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
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).
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.