I've used native Linux and WSL for years and am planning a new workstation for both desktop use and remote development. I generally prefer macOS to Windows, but I'm concerned about macOS filesystem performance, especially with large repositories, worktrees, dependency-heavy projects, and C/C++ or Go builds. I've also heard that some GNU utilities behave differently unless additional packages are installed.
One option is to buy a relatively inexpensive MacBook for the desktop experience and put most of the budget into a powerful headless Linux machine where the projects and builds would live. Another is to use a well-equipped Mac as the main workstation and avoid maintaining two systems.
For people who have used both, how significant are the macOS filesystem and command-line differences in everyday development? Do developers commonly build directly on macOS, and is the two-machine setup worthwhile?
5 Answers
A MacBook and Linux workstation can be a good combination. macOS is convenient for desktop applications, hardware support, audio, and general day-to-day use, while Linux is usually faster and simpler for containers, virtualization, backend work, and server administration. The main question is whether the cost and maintenance of two machines are worth it for your workflow.
The choice is also about desktop preferences, not just benchmark numbers. macOS tends to require less hardware and driver troubleshooting, and commercial software is usually better supported. Linux offers more control, better tiling-window-manager options, easier virtualization, and more performance for the money, but you may spend time fixing hardware or desktop issues.
I prefer Linux for development because the terminal and window-management workflow fit me better, but macOS is a reasonable choice if you value a polished desktop and do not want to maintain the operating system.
For container-heavy development, macOS can feel slower and more finicky because containers run through a virtualized Linux environment rather than directly on the host. Docker and similar tools work well enough, but large projects with lots of filesystem activity can expose the difference. Native Linux generally gives the best performance and lowest overhead for that kind of work.
The impact depends heavily on what you build. A small web app probably will not matter, while repeatedly compiling C++, Go, or large JavaScript monorepos can make the slower filesystem noticeable.
People absolutely do build on macOS, and for many web development workloads the filesystem limitations are more of an annoyance than a dealbreaker. The biggest pain tends to show up with huge dependency trees such as node_modules, large monorepos, or workloads that touch many small files. For ordinary projects, the difference may not affect you much. GNU utilities are also easy to add through Homebrew.
If the projects already live on a Linux machine, a Mac client plus remote builds is a perfectly reasonable setup. You would avoid most of the local filesystem issues, although remote development can add some friction compared with building locally.
I would not make the decision based solely on a general filesystem discussion or someone else’s benchmark. Try your actual repositories and build commands on both systems, especially if you use large worktrees, containers, or generated files. If the Mac handles your normal workload comfortably, its other conveniences may outweigh the performance difference. If Linux already gives you the workflow you want, spending the money on a stronger Linux workstation is likely the better value.
If you rarely need heavy local builds, the Mac can just be the client and the Linux box can handle compilation and services. If you want everything to work offline with minimal setup, a single adequately configured machine is less complicated.