When comparing CodeRunner vs Homebrew, the Slant community recommends Homebrew for most people. In the question“What are the best developer tools for Mac OSX?”Homebrew is ranked 1st while CodeRunner is ranked 15th. The most important reason people chose Homebrew is:

Homebrew makes it easy for people to quickly install any open source software (that is contained within the apps repositories) for Mac.

Pros

Pro

Supports many different languages

Code Runner comes preinstalled with over 20 languages built in, and it's super easy to run simple programs.

Pro

Fast and efficient

You can have multiple tabs open with multiple languages in at the same time and Code Runner still performs excellently. Searching through code is always instant and executing code is fast.

Pro

Quick access to a large repository of open source software

Homebrew makes it easy for people to quickly install any open source software (that is contained within the apps repositories) for Mac.

Pro

Easy to setup and use

Once installed, you control Homebrew using the brew command. You can find packages using brew search, install them using brew install and remove them using brew uninstall.

Pro

Does not require using sudo

One of the things to like about Homebrew is that it refuses to run things under sudo most of the time. This is a great policy, but it causes issues when you want to create symlinks or install in places that SIP has changed permissions on.

Pro

Open Source

Pro

Less maintenance than Macports

Macports seems to be able to get into a bad state where new packages are unable to be installed, or installed software was unable to be updated. This simply hasn't happened with Homebrew. In addition to not having to deal with corruption problems, Homebrew installs packages in userland. Not requiring root to install software is a big win.

Pro

Homebrew tries very hard to use existing tools and libraries

Homebrew’s recipes try very hard to use the existing tools and libraries in OS/X, so they tend to build much faster and require fewer dependent libraries.

Pro

Unintrusive

Homebrew installs packages to their own directory and then symlinks their files into /usr/local. Homebrew won’t install files outside its prefix, and you can place a Homebrew installation wherever you like.

Pro

Builds quickly and requires few dependencies

Homebrew as much as possible uses already existing libraries and tools to install software thus making builds quick and requiring few dependencies.

Cons

Con

Working with very very large projects

Code runner is fantastic for shorter projects, although it can handle very large projects. It stops code completion when the program gets to be several thousands of lines long​.

Con

May cause issues when trying to create symlinks or installing in places where SIP has changed permissions

One of the things to like about Homebrew is that it refuses to run things under sudo most of the time. This is a great policy, but it causes issues when you want to create symlinks or install in places that SIP has changed permissions on. (Alternatively, you could install Homebrew somewhere other than /usr/local, but that might break various packages that depend on having stuff in and relative to /usr/local/.)

Con

Relies on outdated system libs

Con

Command line tools for XCode required

Once xcode is installed you can install Homebrew, including new(er)/different versions of most of the build stuff that xcode-select installed, like a newer gcc, newer git, etc.