Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safaripkgsrc vs CodeRunner
When comparing pkgsrc vs CodeRunner, the Slant community recommends CodeRunner for most people. In the question“What are the best developer tools for Mac OSX?” CodeRunner is ranked 16th while pkgsrc is ranked 28th. The most important reason people chose CodeRunner is:
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.
Specs
Question Ranking
Pros
Pro pkgin is an apt-like tools for installing binaries from pkgsrc
pkgin aims to be a tool similar to apt/yum for managing pkgsrc binaries by relying on pkg_summary for installing, removing and upgrading packages and dependencies, using a remote repo.
Pro Adapted for use on over a dozen different operating systems
Has been adopted to be used on several Unix-like operating systems and Windows. It's also the default package manager of DragonflyBSD and of the (now discounted) Bluewall Linux distro.
Pro Installs and works in the same way as MacPorts
Installs its own dependencies which means that it is very secure. Cannot install anything unless you use the "sudo" command which is in keeping with the Unix philosophy.
Pro Both binary packages and source build possible
Fast software installation is possible by using binary packages. It's also easy to build from source which allows for different compile-time options (like different UI backends) as well as gaining access to pre-release versions of software in certain cases.
Pro Offering tooling for backporting fixes
Backporting fixes can be done by cherry-picking updates from a newer branch (pkgsrc is released every 3 months) and creating a package. Sometimes bugs need to be fixed for production and there is neither a fix in newer pkgsrc nor the softwares upstream. So pkgsrc has tools like pkgdiff, mkpatches, etc. that help with developing patches and building binary packages from that. A bit of documentation about that process can be found here.
Pro Does not need Xcode command line tools or Xcode.
This means that you can install it fresh on a new installation of MacOS and have all your favorite apps installed right from the start.
Pro Works easily with Ansible
Can be used from within Ansible to install packages on macOS.
Pro Easy installation if you use 3rd party scripts
This one works brilliantly.
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 Supports many different languages
Code Runner comes preinstalled with over 20 languages built in, and it's super easy to run simple programs.
Cons
Con Not so broadly used on MacOS as compared with MacPorts
You do not hear about Pkgsrc as openly as you hear the words "HomeBrew" or "MacPorts".
Con Outdated packages
Some packages are outdated.
Con Can't install some packages
Even building well known packages (except MacPorts) from source using the ports can fail.
Con Relatively complicated setup and installation
Installing and setting pkgsrc up is a bit more complicated than in other package managers where it often consists in running a single script.
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.
