Live data from Hacker News

Networking changes coming in macOS 27

eclecticlight.co

191–200 of 248 posts

Re: Networking changes coming in macOS 27

#191

I’m reminded of that time 10-years ago when Apple rewrote parts of its networking code (discovery/mDNSResponder), and it caused so many issues they had to revert the code. https://news.ycombinator.com/item?id=9026192 https://www.macrumors.com/2015/06/30/apple-releases-os-x-10-...

They’re possibly dropping a protocol they’ve been saying they’d drop for years, and tightening connection validation.

This is nothing like the mDNS stuff.

Re: Networking changes coming in macOS 27

#192

Earlier quoted context omitted.

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.

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.

Even on the old world G3s, Mac OS X never had floppy drive support. There was a driver someone had ported from BSD you could install.

Re: Networking changes coming in macOS 27

#193
post #76

Earlier quoted context omitted.

> 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.

philosophically, it depends on who you are. If you're Sam Altman or Vitalik Buterin, yeah, your private home network should be considered to be under attack by hostiles trying to steal from you, but for the rest of us, the NSA isn't going to make an international incident trying to get at your Plex server.

For the rest of us we have IoT devices and guests malware filled devices constantly probing the internal network.

Re: Networking changes coming in macOS 27

#194
post #57

>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 in…

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.

> licensing, probably

Correct, Apple has dropped everything that switched to GPLv3 which includes newer versions of bash, samba, etc.

Re: Networking changes coming in macOS 27

#195
post #28

Earlier quoted context omitted.

Time Machine support is also dropping support over SMB1 so whatever new solution needs to support SMB2/3.

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.

I only meant new as in someone currently owns a Time Capsule and has to replace it with something "new" that supports newer SMB versions.

Re: Networking changes coming in macOS 27

#196

Next: macOS iCloud backups and the eventual deprecation of local Time Machine backups altogether. More services revenue!

I would have agreed if they hadn't put in the engineering effort to upgrade the backup disk image to APFS instead of HFS+. They wouldn't have done that if the plan was to deprecate it soon. (IIRC the next version of macOS is also dropping HFS+ support)

Also it's honestly really weird that they don't have iCloud backups for Macs yet. It seems like a no-brainer feature. I know I would easily switch to Apple over Backblaze as Backblaze's client is just terrible.

Re: Networking changes coming in macOS 27

#197

Earlier quoted context omitted.

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.

I'm not suggesting they keep it all... just ironic as a statement considering Linux is literally removing a bit lately... 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.

What is the age of the 486SX code vs the code paths Apple is removing right now?

Re: Networking changes coming in macOS 27

#198

Earlier quoted context omitted.

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.

Do you have a detailed source for this? I want to read more about it. 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.

Sounds like an Nvidia driver module issue more than anything else. If I had to guess, simply removing the Nvidia module should fix that and still get you video through one of the various backup paths (opennuveau etc)

Re: Networking changes coming in macOS 27

#199

Earlier quoted context omitted.

"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…

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 the…

> The economics make the reasoning obvious, though.

Looking through Apple’s financial statements, they theoretically could support these old systems. I’m not saying a cut doesn’t make sense, but just that economics-wise they could keep one guy for it

Re: Networking changes coming in macOS 27

#200

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.

Did they ever work? No, seriously. I've had a couple of them and the few times I really could have used them I discovered that they represented the worst backup solution I've ever had the misfortune to deal with. Slow, very hard to use beyond their primary integration with the OS (which isn't good to begin with), there's really no good way to keep an eye on how they are doing (what's actually backed up, if it is still there) and the performance is worse than any hand rolled solution I've ever used.

They never supported it properly in the first place and then it just meh'ed out of existence.

I hope "the new Apple" is going to take software seriously.

Post reply on HN