4 ms·
TBH the only thing pushing me away from macOS is that there’s a bunch of stuff running on there by default that I don’t understand, and I don’t really trust App
by enneff 4y ago
TBH the only thing pushing me away from macOS is that there’s a bunch of stuff running on there by default that I don’t understand, and I don’t really trust Apple’s direction wrt respecting user privacy.
When I’ve been using Linux in other contexts lately it’s been awesome being able to fully understand exactly what each process is and why it’s running (and to be able to remove it if I want to). On my macOS (and windows) boxes I end up trusting Apple and Microsoft a lot more than I would actively choose to.
- kjellsbells 4y agoThat's quite amusing to me, because when I "ps ax" on my Linux machine I honestly could not swear that i know what half of them were doing. The names look plausible (dbus, systemd stuff, etc) but it would be easy to get one past me. OpenBSD is a bit of an ice cold shower, but it's the only OS I use regularly where I can point to every process and know exactly what it's doing.
- greyw 4y agoIt is just a matter of getting used to it by studying each process one by one. There is no magic behind it.
- NoPicklez 4y agoCould you not do the same for a standard MacOS install?
- enneff 4y agoNot easily. A lot of the processes don’t have man pages or any other documentation. And they’re closed source so you never really know what they do.
- macNchz 4y agoIn the past some of these were flaky and would hang using 100% cpu, I’d google “fspind 100% cpu” or whatever and find 20 other people with the same problem and zero info about what the process actually did.
- saagarjha 4y agoTry sampling the process next time, I find it to be far more useful at finding the root cause.
- nortonham 4y agosame with netbsd. Not much is running by default and you can quickly figure out what's what. I guess it's kind of true with linux as well....especially as it becomes gnu/linux/systemd......