6 ms·

Hah. Totally. I am no longer at Apple and free to improve other software. Just curious, what were some specific issues that caused your move?

smoldesu 4y ago
There's a plethora of reasons, especially today. I used to do the whole "Windows for gaming, Mac for productivity" thing, but as time went on I started to really hate macOS. The first pet peeve of mine was Spotlight and it's file indexing, which would always melt my computer whenever I cloned repos or did anything outside of a blacklisted folder. Eventually I just disabled the file search altogether. Finder was also never my favorite file manager, but a lot of the reasons really just boiled down to HFS and APFS being really annoying to use, and Apple's own idea of how files/folders should behave. I never quite understood it, and Finder never felt like it helped me make sense of all the "magic". Unrelated to your work (of course, nothing personal though), I really started to hate the time I spent developing on Mac. Deploying to Linux machines while running a decades-old FreeBSD amalgam kernel was an unbelievable pain in the ass, and I wound up spending more of my time fixing Mac stuff than actually developing software. The lack of a package manager burned me up too, since both Macports and Homebrew had their own issues that simply wasted too much of my time. About 3 years ago I pulled the trigger and switched my main machine to Linux, and I've never looked back since. Seeing that Apple is ditching x86 now, it looks like I made the right call (at least as a developer). Simply put, I spent too much time trying to make MacOS behave like Linux, and I was tired of constantly losing control/options.
thefunnyman 4y ago
The worst thing for me is slow docker performance. Not usually an issue on my work MacBook since I tend to do stuff on remote build servers, but it can be really annoying to spin up projects on MacOS without polluting your OS with all the dependencies.
- eschaton 4y ago
  There’s not really much way around this since Linux puts syscall traps in every binary rather than routing through a libsyscall.so that contains the traps. (If the latter were the case, a container could provide an alternate library to do syscall interception much more easily on non-Linux platforms.)

smoldesu 4y ago

There's a plethora of reasons, especially today. I used to do the whole "Windows for gaming, Mac for productivity" thing, but as time went on I started to really hate macOS. The first pet peeve of mine was Spotlight and it's file indexing, which would always melt my computer whenever I cloned repos or did anything outside of a blacklisted folder. Eventually I just disabled the file search altogether. Finder was also never my favorite file manager, but a lot of the reasons really just boiled down to HFS and APFS being really annoying to use, and Apple's own idea of how files/folders should behave. I never quite understood it, and Finder never felt like it helped me make sense of all the "magic". Unrelated to your work (of course, nothing personal though), I really started to hate the time I spent developing on Mac. Deploying to Linux machines while running a decades-old FreeBSD amalgam kernel was an unbelievable pain in the ass, and I wound up spending more of my time fixing Mac stuff than actually developing software. The lack of a package manager burned me up too, since both Macports and Homebrew had their own issues that simply wasted too much of my time. About 3 years ago I pulled the trigger and switched my main machine to Linux, and I've never looked back since. Seeing that Apple is ditching x86 now, it looks like I made the right call (at least as a developer). Simply put, I spent too much time trying to make MacOS behave like Linux, and I was tired of constantly losing control/options.

thefunnyman 4y ago

The worst thing for me is slow docker performance. Not usually an issue on my work MacBook since I tend to do stuff on remote build servers, but it can be really annoying to spin up projects on MacOS without polluting your OS with all the dependencies.

eschaton 4y ago
There’s not really much way around this since Linux puts syscall traps in every binary rather than routing through a libsyscall.so that contains the traps. (If the latter were the case, a container could provide an alternate library to do syscall interception much more easily on non-Linux platforms.)