I use MacOS heavily for command-line heavy programming work > Future versions of macOS won’t include scripting language runtimes by default, and might require

I use MacOS heavily for command-line heavy programming work > Future versions of macOS won’t include scripting language runtimes by default, and might require you to install additional packages. This sounds sensible to me. For ruby, python, node etc you need specific versions for different projects. I literally never use the OS's python -- that's a private matter for the OS and if it doesn't need Python any longer then fine. (rbenv, pyenv, nvm etc help with managing versions) > What bothers me the most though is that Apple has removed the man pages from their online documentation. I recommend installing the coreutils package from Homebrew and using that over the BSD Unix utilities. I also (perhaps controversially?) would recommend using --help over man pages where possible for the simple reason that you are probably fallible, like me! Us mere mortals tend not to have a clue whether the man pages we're looking at are for the executable we're invoking or not, and staying on top of man pages involve staying on top of a bunch of environment variables and weird directories that date back to the hairier days of UNIX. With foo --help, you are always 100% sure that it is giving help for what the executable "foo" resolved to.