> and have enough Linux know how to fix the occasional hick up
> but it can sometimes "just work" for a long time without any issues
These are defining qualities of something that does not "just work"
> but it can sometimes "just work" for a long time without any issues
These are defining qualities of something that does not "just work"
I also find Apple's choice to just continually create 1G swap files until the system locks absolutely baffling.
I've been regularly plugging/unplugging my usb-c docking connected to ethernet while being on teams video call without issues on both linux and windows but ultimately it depends on the protocol. Web/https stuff is usually more forgiving thanks to sessions being maintained "externally" from the protocol itself. Copying files via sftp be a different experience I reckon because you usually use a different source ip address when you switch and need to initiate a new connection.
Idk. about desktop Linux, but my phone does the (WLAN -> Mobile) switch just fine.
If it's about _not reconnecting_ (e.g. which for many apps might require some manual pause/resume of streamed data or similar), then things are more complex as you can't keep your IP, so it then depends on weather the application uses HTTP3/Quick or similar protocols in implementations which are designed to be able to freely roll over to different IP addresses.
So both yes and no :)
macOS has a 'service (priority) order':
* https://sixcolors.com/post/2025/05/service-please-manage-mul...
It's no different that having multiple default gateways in Linux (with different metric/priorities):
* https://superuser.com/questions/1600190/change-order-of-rout...
And when your default route changes so will the TCP connection end-points. This is mostly an issue when you have a stateful session, like SSH, and less so with 'bursty' traffic like web surfing or e-mail.
By default wired connections are higher priority. I've been on Wifi with a MacBook and patched in with the Network Settings panel open and see the change, which is reflected in the output of "netstat -rn". Underneath the hood most of the macOS kernel is (Free)BSD/Unix.
Until we get SCTP multihoming popularized this will generally be an issue on any operating system. Though it would perhaps be nice to perhaps have a socket (TCP) API flag to tell the kernel "keep me on the initial interface as long as it exists" so sessions don't flip over.
I'm not talking about sessions dropping. It has the symptoms of an IP conflict, absolutely no traffic can pass until I disable Wi-Fi. Any other laptop I have ever used would just switch, maybe drop an SSH session, but not this.
>> > and have enough Linux know how to fix the occasional hick up
is for how how to have a reliable acceptable Linux experience and I have less issues with rare occasional hick ups then I had on Windows and Mac in the past. But that is long ago. Through just looking at all the AD/snooping issues, how often windows seem to have broken updates etc. this is way nicer on Linux and seem to be still not worse on Linux then Mac.
> > but it can sometimes "just work" for a long time without any issues
the example here with my gaming setup _doesn't_ require "have enough Linux know-how",
after the initial setup it so far just did works
The initial setup was just running a trivial install + ~2 simple to do and find through search, but should-be-unneeded initial tweaks (both Steam specific).
through I currently happen to only care about games both available on Steam and running on Linux without Linux specific manual setup/tweaks (like Silk Song, Nine Sols, Detroit Become Human (but all native 4k)). And it's all AMD and no "unusual" consumer hardware components.