Comment by jbstack
18 hours ago
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.
At the risk of sounding repetitive, my comments are in the context of the OP's article which is specifically about a scenario where you lack control in macOS. If you're someone who doesn't care about being able to do what the article wants to do, then your use case doesn't fall within the scope of what I'm referring to.