Hacker News new | ask | show | jobs
by rafaelmn 108 days ago
I'm sorry but if your out is linux and windows because you're not happy how stuff doesn't "just work" in the Apple ecosystem boy are you in for a bad surprise.

However bad you think Apple is getting with MacOS - windows is getting worse. And Linux ? Good luck getting decent hardware that will run without having basic functionality issues. Queue the linux brigade "my PC works perfect, what linux issues are you having". Meanwhile I can't use bluetooth on my desktop (works perfectly fine on windows), and I was watching laptop reviews from justjosh recently where he's adding a segment where he is trying out linux on the device - and his experience on the two videos I've seen "sound does't work, wifi doesn't work, BT doesn't work ..."

All that said I am looking into leaving the Apple ecosystem as well because I just don't like how locked down and the devices are, but I'm fully aware that it's going to take significant effort for stuff that I'd get out of the box from Apple.

7 comments

The problem isn't that MacOS doesn't work, it's that MacOS doesn't work _and_ you can't fix the things that don't work.

You can anticipate "the linux brigade" because it works well for many of us.

This isn't to say there _aren't_ problems. Bluetooth, audio, etc. working all depend on having the luck that someone wrote good drivers for the device you want to install Linux on. When you do have a problem, you don't have the benefit of having many people on your same configuration like you do with Apple. You might find yourself troubleshooting as the only person with your specific combo of dongle, mobo, cpu, distro, and kernel.

I've been on Linux since 2009 and MacOS since 2021. I've never had a bluetooth problem with Linux but I've had a ton on MacOS (but that might just be airpods).

The nice thing about Linux is that you have control over all your problems. On MacOS, if you have a solvable problem, the solution is often either "Pray that Apple fixes it in the next release" or "The fix for that costs $10 per month and it'll clog up your app switcher". On Linux, if you have a solvable problem, the solution is often "go into the settings for your distribution" or "install this tweak tool" or "find someone who had it before on a support forum and follow their steps".

It's not unreasonable that someone who is fed up with unsolvable problems on MacOS would find Linux more appealing. It's not a naive mindset, it's just how things are.

Thanks for this very important point. It often gets lost in the discussion.

The big idea with Linux/BSD/fully-open-source is that you can fix whatever you don't like.

That was the breaking point for me with Tahoe. I never loved MacOS before that, but it never got in the way. Then with Tahoe, it got in the way, so I went to fix it, and found out that fixing it is actually impossible! That was the breakup moment.

Sophisticated LLMs make it even easier to fix or tweak any Linux/BSD/fully-open-source software to our liking.

> The big idea with Linux/BSD/fully-open-source is that you can fix whatever you don't like.

That's a great theory, and sometimes it's actually true, but in reality for most users most of the time, Linux is as "fixable" as Windows or macOS, because most people, even the technically savvy ones aren't driver developers. Heck most software developers probably aren't even C programmers anymore. And even if someone had the competency in the language and low level system programming, do they have the time and the inclination to re-write the audio stack so that it finally works correctly? Or to fix the fact that even in 2026, sleep and hibernate are hit and miss? And then to maintain their patch against future system updates or go through the process of getting it upstreamed?

Most Linux users, and especially most Linux users switching from something like macOS or Windows would be waiting and hoping that someone else decided to fix the thing for them because they either lack the skills, time or inclination to do it themselves. And we know this is true because if it weren't true, all the various "wars" over the years like systemd and pulse audio and wayland wouldn't have been a war at all because everyone who didn't like it would have easily patched it out and moved on. But a modern full fledged OS experience is a mess of intertwined and complex dependencies. So when a distro decides to switch a big chunk of the underlying stack like that, most people either have to go along with it, or hope that enough people feel strongly enough about it to fork everything and make their own distro, and then they have to hope the forkers have the passion and drive to maintain that for them.

Yes, you "can" fix whatever you don't like in linux. Just like you "can" find all the information you need to diagnose and treat whatever medical condition you might have online and at your local libraries. But most people are still going to pay a doctor, because most people don't have the time or skills to actually do it.

> but in reality for most users most of the time, Linux is as "fixable" as Windows or macOS,

I disagree with this. For most users, most of the time, Linux is significantly more fixable than Windows or MacOS.

In nearly 20 years, I've never had to write a line of C or touch the Linux kernel to fix issues I've had on Linux.

For example, one of my big peeves I've had lately on both PopOS and MacOS are the looooong animations to switch desktops.

On PopOS, I had two paths to fix this: Tweak the COSMIC desktop to fix the behavior, or the simple thing of simply installing GNOME (or KDE or any other DE of choice).

On MacOS, I'm SOL. There's no way to fix that on my Macbook (short of installing Asahi Linux, of course).

> Just like you "can" find all the information you need to diagnose and treat whatever medical condition you might have online and at your local libraries. But most people are still going to pay a doctor, because most people don't have the time or skills to actually do it.

This isn't a great analogy, but it's worth noting: Many conditions are expected to be self-diagnosed and self-treated. I don't go to the doctor for scrapes, bruises, colds, dry eyes, a stubbed toe, etc. By this analogy, Linux users are buying their own aspirin and applying their own band-aids, while MacOS users are waiting in line, dependent on someone else to fix these things.

I say this as someone who uses both MacOS and Linux daily.

> On PopOS, I had two paths to fix this: Tweak the COSMIC desktop to fix the behavior, or the simple thing of simply installing GNOME (or KDE or any other DE of choice).

So what did you do? Did you fix the DE? Again, this is effectively outside the skill of the sorts of people who would be "switching" to linux due to the issues with macOS or Windows.

And while installing a new DE is certainly easier than re-programming one, it's still dependent on someone else having written a DE that not only solves your problem, but doesn't introduce entirely new ones and isn't so fundamentally different to the user that they might as well have switched OSes in the first place. And if the user's primary issue was being forced into a major interface re-design like liquid glass, having to switch to a completely new DE is more of a lateral move than actually fixing the problem.

And to be clear, the fact that it's POSSIBLE for someone to fix a problem for you even if you can't, and it doesn't have to be the primary OS vendor is a benefit of using an open source OS. So I'm not saying it's not possible to benefit from this. I'm just saying that for most users, most of the time, the ability to "fix it themselves" is effectively as out of reach for them as it is using macOS or Windows because having access to the source code is only the tiniest part of actually fixing a problem for themselves.

Since my doctor analogy fell flat, let me try again with a traditional car analogy. A kit car is infinitely more open, customizable and user controllable than any car bought from an auto manufacturer. And yet, for the vast majority of drivers, buying a kit car, even if it was turn key and pre-built would do absolutely nothing to make it more likely that they will do their own repairs or modifications to the car. They will continue taking it to the same mechanics they always took their traditional cars to, they will continue to buy off the shelf parts if possible and do without if not.

> So what did you do? Did you fix the DE?

Nope, I swapped to GNOME. Forking the DE was something I was considering doing just to contribute back. It's not something I'd recommend someone to do. (That said, it's Rust and not C, so the barrier for entry is much lower.)

If someone can install Linux, they can install a new DE. It's easy peasy.

> if the user's primary issue was being forced into a major interface re-design like liquid glass, having to switch to a completely new DE is more of a lateral move than actually fixing the problem.

No, switching DEs fixes the problem. If MacOS were open source, then you'd have a community-run fork from before Liquid Glass. (If MacOS were open source, you'd also probably have an LTS branch anyways, and no dark patterns forcing you to update.)

Ubuntu users dismayed by Unity were able to stay on GNOME by installing GNOME. Ubuntu users dismayed when Unity went away were able to stay on Unity because someone forked it. GNOME users dismayed by GNOME 3 are able to stay on forks of GNOME 2.

And it's worth stressing that _none_ of these were so bad as Liquid Glass.

>for most users, most of the time, the ability to "fix it themselves" is effectively as out of reach for them

This is the thing I take contention with. This seems hard to square with the experience of someone using Linux. Is this an assertion you're making as someone who doesn't use it?

I think the most common experience on Linux is that people are able to fix the things that annoy them. It's a tangible and normal thing, not a hypothetical.

Does it matter? Generally Linux desktop distributions are made for the people who use them, who would tend towards people who will fix things. You mention distros but there obviously are a lot of passionate distro makers because right now it seems like there are more distros than ever.

There are often comments on threads like this that go along the lines of "If only the people making Linux desktop did X then they'd get more people". But there there isn't really anyone making Linux on the desktop. It's not a product. Even the products within it are built on the work of people with very disparate interests. It's kind of amazing that we get a cobbled together working experience at all.

Apple and Microsoft can focus on particular things, like getting more users, or supporting hardware they want to sell, or trying to get you to sign up to Office 365. No Linux desktop environment can have that kind of focus. So when you say it's not fixable to most users I think: well it's not supposed to be. It's not supposed to be anything, it just kind of is. Like coming across a mountain instead of a theme park - it's not a curated experience, it's not going to be for everyone, you might get hurt, but it's far far more beautiful.

> Does it matter?

It does matter if you're selling someone on the idea of switching away from their mac or windows machine that they're complaining about something the OS vendor has done by highlighting that with Linux they could "fix it themselves". It misses the point that most people don't want to "fix it themselves" and even if they had the inclination to that, for many problems they don't have the time or the skills. If someone is upset that Apple forced a move to Liquid Glass with Tahoe and all the bad UX that comes along with it, it's possible that they could also have the skills to fix their OS if they were equally upset that their chosen linux distro switched to Wayland. But it's more likely than not that they don't have those skills and so for that user, Linux is theoretically an OS they can fix, and practically just as likely to force them to accept the march of technology as any other OS they use.

I personally wouldn't try to sell Linux to anyone and get them to switch. It is a futile game and I see no real reason for it. People will move if they have reason to (in any direction) and the best one can do is show and tell. I will tell people what I like using if they ask. I'm more likely to tell folks not to switch because I don't want to be technical support for anyone outside my household.

I don't think anyone will switch from MacOS to Linux because of rounded corners. If they're really into theming it would make sense.

Being able to fix things is also a bit of a vague statement. You can fix things in many different ways, and you can fix some things in every OS. Fixing might be writing your own code, or switching a theme, or an application, or a distro, or the whole OS. The level of lockdown then matters. MacOS has the greatest lockdown because you can't just get a new Macbook and fix it by installing something other than MacOS.

Your comments really sound like you don't have experience with Linux. This sounds like you're repeating things others have heard.

> it's more likely than not that they don't have those skills

No, they absolutely do.

Even at the most basic level of interacting with the OS, Linux desktops usually offer more options in its Settings application than you'd get with MacOS.

If something annoys you on Linux, it probably annoyed someone else, and there's probably a toggle or switch for it.

If not, the barrier to fixing it is usually "sudo apt install cool_thing". Higher than "open the settings app", but it doesn't require compiling or coding. It only requires literacy (and, granted, not everyone is literate).

> Linux is ... practically just as likely to force them to accept the march of technology

For starters, let's not characterize Liquid Glass as "the march of technology". It's a symptom of dysfunction within Apple.

Second, no, this is just simply wrong. Many Linux distros offer LTS versions. Ubuntu 16.04 was released in 2016 and its support is ending this year, after a decade. (That's not counting the five more years of security maintenance.) Very importantly, these also don't have dark patterns to tick you to update like Apple did with Tahoe.

> > The big idea with Linux/BSD/fully-open-source is that you can fix whatever you don't like.

> That's a great theory, and sometimes it's actually true, but in reality for most users most of the time, Linux is as "fixable" as Windows or macOS, because most people, even the technically savvy ones aren't driver developers.

But there a whole lot more people who are happy to pay Claude $200/month now than there used to be. Claude isn’t a driver developer, but it’s taken a bunch of different open projects and modified for them for me in such a way that it’s made my life meaningfully better.

Things I couldn’t do for years, that I’ve wanted for years, got accomplished in 2 evenings: one to implement and deploy, one to optimise because the original deployment was a good POC but not good enough to keep running (e.g. doubling or tripling of CPU usage or RAM from prior to modification).

Sure, you could argue I’m paying a doctor, but there isn’t a doctor for the apple ecosystem. There’s just “suck it up, sunshine.”

(Written from my iPad, where I continue to suck it up)

You fix something then the next system update breaks everything. Depending on the machine mood and what I'm currently running slack/chrome will crash while attempting to screen share. Audio routing will get messed up randomly every time I need to use a DAW.

Sorry but the level of stuff that Apple users complain about when they say "not working" is not comparable to the level of unreliability of linux for me - it's not even in the same class of reliability - Apple users are just spoiled and rightfully mad about the platform quality deteriorating.

I'm not a Linux noob, I've been running linux desktop on and off for a long time (I remember ordering the free Ubuntu CD's and having to go to customs with my father at 14-15 so over 20 year probably - holly shit time flies). The last attempt was like a year ago for two months. Linux is still very much a hobby you pick up to run your computer for me and every colleague I see using it just confirms this even if they won't admit it (issues connecting to calls, unmuting, turning on camera, etc.). Like I'm annoyed that I can't use HDMI 2.1 via my USB 4 dock on Mac because it doesn't support some protocol, on Linux HDMI 2.1 on my AMD card is a no go from the start (unless I want to go with some random dude unofficial kernel driver patches).

I still use my desktop as SSH workstation and run arch on it, but my client is MacOS - I just need something that works reliably for everyday productivity tasks.

We seem to have a world where neither Linux, nor MacOS, nor Windows "just work". None of them have meaningful support channels for individuals. All of them have issues. They're very similar in these ways.

The first of these systems is actionable: When it doesn't work, it can generally be made to work. The whole journey may be an awful affair for the entire duration, but a person can usually (not always!) get there.

The other two systems are inactionable: When it doesn't work, there is no fixing it. There is no pathway, nor any journey. One can only accept that it is broken, that they are powerless to change it, and that this is the end of the road for that problem.

---

There are probably healthier ways to learn acceptance than this.

> The first of these systems is actionable: When it doesn't work, it can generally be made to work. The whole journey may be an awful affair for the entire duration, but a person can usually

It's also important to mention that it is more likely a person would get help along the way.

And - it should also be said that there are non-Linux free operating systems, like the BSD's, for which it can also "generally be made to work". And there's the more niche HaikuOS (where I don't know if what doesn't work can be made to work, but people do use it).

The category of things that don't "just work" on a Mac for me compared to Linux and even Windows is just a class apart. You can't compare shared buffers between phones being flaky or using face time on PC to answer calls from iphone being glitchy to my browser crashing when I try to screenshare, repeatedly, on linux.
I absolutely can compare these things. I don't even have to move any goalposts.

- shared buffers between phones being flaky: Can't fix. Acceptance-only.

- using face time on PC to answer calls from iphone being glitchy: Can't fix. Acceptance-only.

- my browser crashing when I try to screenshare, repeatedly, on linux: Can fix. I don't have to accept this.

1. and 2. are never even an options on linux - there's probably some way but the effort/payoff is basically a nogo. On apple I get those by default just by using the same apple id on the devices. It's not a principled comparison but a practical one between using these systems.

Again if you're coming from MacOS and expect Linux to be better at "just works" you're in for a bad surprise.

> On apple I get those by default just by using the same apple id on the devices. It's not a principled comparison but a practical one between using these systems.

Right. That's why you're complaining about how they don't work.

Anyway, I never suggested that Linux is better at "just works."

Instead, I suggested that -all- of them have issues and further posited that, on Linux, those issues are actionable.

I am disinclined to defend a position that I do not hold.

And phones are even worse!

I have come to hate Android, but every time I seriously look at switching to iOS, it seems Apple has chosen that time to make things even worse. Unfortunately, there's no Linux equivalent for phones. (Or at least, nothing that's easier than gentoo was in 2004. That was great for learning, but for daily use of a critical device, not so great.)

they have yet to invent a linux laptop with good battery life, quality keyboard & trackpad, sleep-then-suspend, bluetooth. as long as apple makes computers with those things, i can be content even if it means living inside my full screen linux vm
the macbooks are crazy for battery life compared to anything else.

But you can run Linux on an M2 Macbook.

And there is premium windows hardware on the market, where Linux actually works better than Windows (notably business laptops like the Thinkpad x1 and HP Elitebook).

unfortunately asahi linux bare metal cuts batty life by 40% or so and doesn’t support external displays via USB-C. worse battery seems a very common theme for linux-on-laptop.
Yeah MacOS is better with Battery life compared to Linux.

But, compared to W11?

I guess it depends a lot. My Precision 5520 got an extra hour of battery on the 9cell varient. Thats about a 20% uplift from W11; but thats an old Xeon laptop now.

Luck doesn't play a factor in getting your hardware to work with Linux. It's either supported or it's not, and since the code is Open Source you can Google/ChatGPT the answer in less than 2 minutes.

Your experience isn't uncommon, but it's largely the result of trying to force a square peg into a round hole. There are thousands of different smartphones, game consoles and set-top boxes that rely on Linux for all of their basic functionality. You only get problems trying to smash reverse-engineered drivers and hardware together expecting OEM-level support. If you want good Linux support, pay for good Linux support.

This. If you want Linux to be better, you need to use Linux. It's not any harder for OEMs to support it vs. Windows or MacOS. It's actually easier to support in many cases. There just isn't a business case. Use Linux, create a business case, get better software. Someone has to be the early adopter. Better nerds like us than grandma.
> I'm sorry but if your out is linux and windows because you're not happy how stuff doesn't "just work" in the Apple ecosystem boy are you in for a bad surprise.

I think you and GP agree more than you realise, their point seems to be that Apple was worth all the locked down walled garden stuff because at least it "just worked." Now it's a locked down walled garden which _also doesn't work._ Tahoe and iOS 26 are the worst of both worlds.

> Good luck getting decent hardware that will run without having basic functionality issues. Queue the linux brigade "my PC works perfect, what linux issues are you having". Meanwhile I can't use bluetooth on my desktop...

Ok, you're having Bluetooth issues. Fair enough. But using Bluetooth (on a desktop no less) is not so overwhelmingly common that one can justify a sweeping statement like yours on that basis. The "Linux brigade" says that stuff works for them because it does. My desktop "just works" for me and it has for like 5 years at this point. That doesn't mean everything is perfect, but neither is Linux the train wreck of incompatibility you describe.

> And Linux ? Good luck getting decent hardware that will run without having basic functionality issues.

I think that's probably a few years out of date. Certainly, it used to be completely true and was a major problem.

I'm just not finding that now. Drivers are better, and more widespread, and there are less odd hardware innovations in standard PC components that screw it up.

And, if you want a laptop that runs Linux perfectly, there are more than a few options out there that ship with Linux installed and supported now.

Get serious, none of them have a working fingerprint reader.
I prefer my MacBook, but the Thinkpad whatever I bought to have Windows and Linux available for some software I need occasionally has a fingerprint reader that worked out of the box on Ubuntu.
Since when is using a fingerprint reader on laptops at all common? If that's a requirement for you then fair enough, but not having a fingerprint reader doesn't make a laptop so niche that one would be justified in saying "get serious".
Um.. all MacBooks have had a fingerprint reader for years. Without it, I would be typing passwords a lot more.
My Thinkpad's fingerprint reader worked out of the box.
My framework 13 fingerprint scanner worked immediately out of the box.