"How"? Getting geeked up over a switch is probably overdoing it. I mean...you just do it. Install Fedora on it--I mean, you could install Ubuntu, but the movem

"How"? Getting geeked up over a switch is probably overdoing it. I mean...you just do it. Install Fedora on it--I mean, you could install Ubuntu, but the movement seems to be away from Ubuntu and for good reasons, in production I wouldn't run something that wasn't CentOS, and Fedora is close enough while removing a lot of the pain points of dealing with Debian derivatives--and start working. It'll suck at first, it'll suck less over time, you'll get there. You'll learn to RTFM if you haven't learned it already, and you'll get there. As a developer, using either is basically substitutable. I still use a Mac laptop because Linux laptop support varies between okay and awful (and System76 et al make computers that feel like junk, though Dell's support is worth calling out as a positive--my next machine is probably an Alienware 15, largely because of the keyboard and the GPU) but when not on the road I use the Mac mostly for Keynote and Photoshop, not writing code. Every Unix development tool I use (i.e., I still have Windows partitions around for good reasons), from VS Code on down the line, works on both Linux and OS X without trouble. There's really not much "switching" to be done. If you use novelty stuff like Espresso or whatever it might be a trickier situation, but I feel like most developers aren't in that boat. Consider Dropbox or similar for syncing dotfiles, though. Sharing those across will reduce your frustration a decent bit. Just make sure to have separate files for Mac and Linux-specific stuff, where applicable, and source them appropriately.