One thing I’ve become increasingly interested in over the years is how much developer experience (DX) influences engineering productivity—often more than we initially realise.
Beyond frameworks, languages, or architecture, the local development environment itself plays a major role in reducing friction, onboarding speed, and overall team consistency.
Disclaimer: There are strong arguments on both sides, particularly in enterprise environments where Windows is often the established standard. Ultimately, this comes down to context and personal preference rather than a universal “best” choice. No judgment either way 🙂
Environment parity matters more than it seems
Most modern production systems run on Linux-based infrastructure. Because of that, many engineering teams value development environments that closely mirror that reality.
macOS tends to sit in a practical middle ground here: it provides a Unix-based environment that aligns well with production systems, while still offering a polished, general-purpose desktop experience.
This often results in:
- Fewer environment-specific issues
- More consistent tooling behaviour across teams
- Easier onboarding and setup standardisation
Tooling alignment across modern stacks
A large portion of today’s web development ecosystem is designed with Unix-like environments in mind, including:
- Node.js ecosystems (npm, yarn, pnpm)
- Docker and container workflows
- Cloud CLIs (AWS, GCP, Azure)
- CI/CD tooling and scripting pipelines
These tools work across Windows, macOS, and Linux—but in practice, the experience can vary depending on how “native” the environment feels.
Windows with WSL2 has significantly improved here and is absolutely viable for modern development. However, many teams still prefer macOS for its more integrated, out-of-the-box Unix experience without an additional abstraction layer.
Team consistency and onboarding
From a team perspective, standardising development environments can reduce a surprising amount of friction:
- Fewer “it works on my machine” issues
- Simpler onboarding documentation
- More predictable local setups across engineers
This becomes increasingly important as teams scale.
It’s about trade-offs, not absolutes
This isn’t to say macOS is universally “better” or that other platforms are unsuitable.
- Windows has made major strides with WSL2 and remains dominant in many enterprise environments
- Linux remains the closest match to production systems and is often preferred for backend-heavy roles
- macOS tends to be a pragmatic balance that many product engineering teams converge on
Final thought
In practice, many product-driven organisations—particularly in web, mobile, and cloud engineering—standardise on macOS for engineers because it reduces friction and aligns well with modern tooling expectations.
Notably many Silicon Valley companies have historically leaned heavily in this direction.
Ultimately, it’s less about the operating system itself, and more about reducing variability in developer experience so engineers can focus on building.
