My anecdotal observation is the same. Most of my friends in Silicon Valley are using Macbooks, including some at some fairly mature companies like Google and Facebook.
I had a 5-year sysadmin career, dealing with some Microsoft stuff especially on identity/accounts/mailboxes through Active Directory and Exchange, but mainly did Linux specific stuff on headless servers, with desktop Linux at home.
When I switched to a non-technical career field I went with a MacBook for my laptop daily driver on the go, and kept desktop Linux at home for about 6 or 7 more years.
Now, basically a decade after that, I’m pretty much only driving MacOS on a laptop as my normal OS, with no desktop computer (just a docking station for my Apple laptop). It’s got a good command line, I can still script things, I can still rely on a pretty robust FOSS software repository in homebrew, and the filesystem in MacOS makes a lot more sense to me than the Windows lettered drives and reserved/specialized folders I can never remember anymore. And nothing beats the hardware (battery life, screen resolution, touchpad feel, lid hinge quality), in my experience.
It’s a balance. You want the computer to facilitate your actual work, but you also don’t want to spend too much time and effort administering your own machine. So the tradeoff is between the flexibility of doing things your way versus outsourcing a lot of the things to the maintainer defaults (whether you’re on Windows, MacOS, or a specific desktop environment in Linux), mindful of whether your own tweaks will break on some update.
So it’s not surprising to me when programmers/developers happen to be issued a MacBook at their jobs.
My anecdotal observation is the same. Most of my friends in Silicon Valley are using Macbooks, including some at some fairly mature companies like Google and Facebook.
I had a 5-year sysadmin career, dealing with some Microsoft stuff especially on identity/accounts/mailboxes through Active Directory and Exchange, but mainly did Linux specific stuff on headless servers, with desktop Linux at home.
When I switched to a non-technical career field I went with a MacBook for my laptop daily driver on the go, and kept desktop Linux at home for about 6 or 7 more years.
Now, basically a decade after that, I’m pretty much only driving MacOS on a laptop as my normal OS, with no desktop computer (just a docking station for my Apple laptop). It’s got a good command line, I can still script things, I can still rely on a pretty robust FOSS software repository in homebrew, and the filesystem in MacOS makes a lot more sense to me than the Windows lettered drives and reserved/specialized folders I can never remember anymore. And nothing beats the hardware (battery life, screen resolution, touchpad feel, lid hinge quality), in my experience.
It’s a balance. You want the computer to facilitate your actual work, but you also don’t want to spend too much time and effort administering your own machine. So the tradeoff is between the flexibility of doing things your way versus outsourcing a lot of the things to the maintainer defaults (whether you’re on Windows, MacOS, or a specific desktop environment in Linux), mindful of whether your own tweaks will break on some update.
So it’s not surprising to me when programmers/developers happen to be issued a MacBook at their jobs.