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

Networking changes coming in macOS 27

eclecticlight.co

Post reply on HN
Print view View original

101–110 of 248 posts

Re: Networking changes coming in macOS 27

#101

Post by tracker1 »

yjftsjthsd-h wrote: post #98
tracker1 wrote: post #90

Earlier quoted context omitted.

Ironic, considering Linux is dropping a LOT of old devices from 7.1

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.

Re: Networking changes coming in macOS 27

#102

Post by ryandrake »

retired wrote: post #84
ryandrake wrote: post #46

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…

macOS Tahoe still has floppy drive support.

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.

Re: Networking changes coming in macOS 27

#103

Post by ryandrake »

tracker1 wrote: post #101
yjftsjthsd-h wrote: post #98

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.

Absolutely--Linux is by no means perfect.

Re: Networking changes coming in macOS 27

#104

Post by ifwinterco »

red_admiral wrote: post #99

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

Yes this one seems unambiguously a good idea

Re: Networking changes coming in macOS 27

#105

Post by [deleted] »

[deleted] wrote: post #94
pvtmert wrote: post #88

Earlier quoted context omitted.

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?

[deleted]

[deleted]

Re: Networking changes coming in macOS 27

#106

Post by reaperducer »

ndisn wrote: post #64

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.

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?

Re: Networking changes coming in macOS 27

#107

Post by tonyedgecombe »

FireBeyond wrote: post #15
AlexandrB wrote: post #10

Earlier quoted context omitted.

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.

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…

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.

Re: Networking changes coming in macOS 27

#108

Post by xattt »

Hamuko wrote: post #95
amluto wrote: post #74

Earlier quoted context omitted.

Even ignoring the lack of polish, the animations make it very hard to actually use Time Machine.

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.

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.

Re: Networking changes coming in macOS 27

#109

Post by reaperducer »

ifwinterco wrote: post #104
red_admiral wrote: post #99

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

Yes this one seems unambiguously a good idea

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?

Re: Networking changes coming in macOS 27

#110

Post by akerl_ »

TheJoeMan wrote: post #100
_verandaguy wrote: post #53

Earlier quoted context omitted.

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…

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

It’s not unreasonable to ask but they can and are saying “no”.
Post reply on HN