> “just works”

if you use distros which ship the latest _stable_ release of software

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, something I haven't exactly had with either Windows or Mac

like my current gaming setup from a year ago(roughly) was setup once, I had to fiddle some minor tweaks during setup and since then it "just works tm". No issues, not know how needed, nothing. (At least for the Games I play.) But also not Nvidea which has in recent years increasingly more QA issues across _all_ OSes and _all_ hardware including their supper expensive AI cards... But that is more a Nvidea then a Linux Problem, by now, was different in the past.

▲

terminalbraid 2 hours ago | parent | next [-]

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

▲

Geezus_42 2 hours ago | parent | next [-]

I've never used a computer that didn't have occasional hiccups. The Mac I have for work has lots of weird bugs. One is that if it has been using WI-FI and I plug-in my dock with an Ethernet cable attached, I lose internet access because MacOS can't gracefully handle the new interface becoming available.

I also find Apple's choice to just continually create 1G swap files until the system locks absolutely baffling.

▲

throw0101a an hour ago | parent | next [-]

> One is that if it has been using WI-FI and I plug-in my dock with an Ethernet cable attached, I lose internet access because MacOS can't gracefully handle the new interface becoming available.

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.

▲

9 minutes ago | parent | prev | next [-]

[deleted]

▲

kavok an hour ago | parent | prev [-]

Can any OS gracefully handle switching between WiFi and Ethernet without at least a blip in connectivity?

	▲	Krutonium 35 minutes ago \| parent [-]
		In my experience Linux can yeah.

▲

jeltz 2 hours ago | parent | prev [-]

By those standards neither Mac nor Windows just work. No modern OS expect maybe ChromeOS just works.

▲

throw0101a an hour ago | parent | prev [-]

> if you use distros which ship the latest _stable_ release of software

> and have enough Linux know how to fix the occasional hick up

A Linux sysadmin teammate of mine has >10 years of running Linux servers, and chose to install Ubuntu on his work Dell laptop, and in the ~2 years he's been running that thing he's had regular (2-3/month) issues with audio during Zoom, Teams, and Google Meetings sessions. Both Bluetooth and wired headset connections.

At my last job (pre-COVID) I had a Linux workstation at my desk and a Windows laptop. At where I'm currently at we're hybrid and so we get laptops and I chose a MacBook because I knew I could both do my daily sysadmin chores through Terminal and also have access to 'business apps'.

	▲	fsflover 13 minutes ago \| parent [-]
		> issues with audio during Zoom, Teams, and Google Meetings sessions Could it be due to a poor support of Linux by these proprietary apps? Possibly even intentional.