Every time I set up a new Mac, I follow a specific process to install my command-line programming tools. My goal is simple: create a development environment that closely mirrors the RHEL web servers I work with daily. This guide outlines that process.
My philosophy is to keep things as simple and transparent as possible. I often find that modern package and version managers, while powerful, add layers of complexity I don’t need. I rarely require multiple versions of a programming language on the same machine, and I don’t want to guess where my binaries and libraries are located. Instead, I prefer a stable, predictable architecture where I know exactly where to find everything.
If you share that “get off my lawn” approach to development environments, this guide is for you.