Comment by jbstack
1 day ago
No insult intended. I genuinely wasn't aware of what advantages macOS offers for a power user (by which I mean someone who wants to do tasks more advanced than browsing, email, etc.). From quickly skimming the replies the common theme seems to be a mixture of battery efficiency, hardware compatibility, and Mac-only software.
> Been there done that. I have too many other things that need to get done to build up a distro.
Yes, but my comment wasn't made in isolation or directed at people with your objectives. The OP's article is about doing exactly this, but in the opposite direction (expending large amounts of effort to remove unneeded processes). See for example: "if we assume that we need to identify just 500 candidates, and each takes an average of one week to research, that would take over 10 person-years".
Starting with that as the baseline (as opposed to starting from your position which is that you're not interested in spending time on this issue), building up from zero is a lot more straightforward. And, if you use something like NixOS, you generally only have to do it once since the idea of "reinstalling" the OS (e.g. for new versions) largely goes away: subsequent effort is just about changing your mind about what software you want, or what version you want (as with any OS).
> what advantages macOS offers for a power user
The serious answer is that you get an "it-just-works"⁺ Unix-like operating system that gives you a development experience on-par with Linux.
If you are doing sysadmin stuff: you will not like macOS.
If you care about configuration for your window manager, desktop environment, or systemd services: you will not like macOS.
If you are a graphics engineer or a kernel engineer: you will (probably) not like macOS.
If you are a C++/Rust/Python/JavaScript/Java/mobile/desktop engineer who wants a rock-solid developer environment and doesn't care about the above: you will like macOS.
You get all the Unix tools you could ever want, whatever shell you want to use (Zsh, Fish, even PowerShell), clang/LLVM, etc.
Does that answer your question?
⁺: caveat being "it just works" is getting less and less true with every macOS release.
This would be my answer, though I also do sysadmin stuff from macOS just fine. I've used OSX/macOS for a long time, I understand how it works and how to move around, and the ecosystem integration is nice. Adobe products, MS products also all work without any hassle along with any software development I want to do. Then there's the hardware which Apple Silicon has been great for. I bought an M1 Max 64gb laptop on release and it still never feels slow. Battery life is great, trackpad works great, etc...
And I say all this knowing that someone can likely get similar use out of a MS or Linux laptop. At this point, just pick what you know and get on with it.
> I also do sysadmin stuff from macOS
MacOS is fine as a client/dispatch node for SSH/Ansible/Terraform/whatnot; I think they meant that you cannot sysadmin MacOS itself as a target with many of the same tools/techniques you would sysadmin a Linux server.
I wish that weren't true, as someone who struggles with a lot of cross-platform Puppet tooling that I wish behaved better on Mac. No, Nix doesn't help; not when the goal is "configure other people's machines to a baseline but don't otherwise prescribe how they should use them".
1 reply →
> If you are doing sysadmin stuff: you will not like macOS.
Even then, that's debatable. Should say if you like doing sysadmin stuff on your own machine.
I am a sysadmin, and my daily driver is an M4 macbook pro and I wouldn't have it any other way. I admin other machines, I don't want to play sysadmin for my own. But its mostly for the hardware more than any other reason.
I think a surprising number of kernel engineers like Macs
[dead]
> I genuinely wasn't aware of what advantages macOS offers
It's been out for a while.. why are you interested in the debate if you've come this far, have no idea, but want to lead with a counter-assertion?
Again, my comment wasn't isolated. It was a response to the article. In that article, the person was concerned with tracking down 500+ potentially unneeded processes, and lamenting the difficulty and time consuming nature of doing so.
Perhaps I could have phrased my question better, but what I'm really asking is: for that type of user, why would you pick macOS over Linux when such things are trivial (relatively speaking) in Linux by comparison. Note that I didn't ask "what advantages does macOS have?" I qualified it with: "which makes it worth sacrificing the ability to run your machine the way you want?". I wasn't suggesting that there are no advantages at all. Nuance matters here.
> which makes it worth sacrificing the ability to run your machine the way you want?
I’ve never felt like I couldn’t run my machine the way I want. When I leave macOS is when I start to miss all integrations and ease of use affordances.
One of the times I made a big push to try Linux again on the client I was fighting with getting HiDPI working well, and the most common response was “you don’t need that”. Huh? Speaking of running the machine how I want.
Every decision is a trade off, even Linux. You feel like you can do anything you want, but it’s just a set of different things you can do. We’re long past the days where someone can buy hardware and write every piece of software from scratch for themselves. We all depend on others to make decisions for us, and some of those decisions will limit us in some way.
That "which makes it worth sacrificing the ability to run your machine the way you want" is utterly superfluous.
The way I want to run my machine is by running macOS and using its features, app ecosystem, and so on.
Not once have I ever felt I've had to make a sacrifice to do so.
1 reply →
Why are we making personal attacks, instead of simply listing all of the unique system-selling features in macOS?