Brackets vs pkgsrc

Brackets will automatically refresh the browser and load the latest saved version of a file open in the browser. This works with php as well. Editing a css will even highlight the tag that's currently being worked on. However, it only works with Chrome.

Brackets is easy on memory usage and it starts up quickly.

Brackets is entirely free and open source.

The functionality of Brackets can be extended via a simple-to-use extension manager. The extension manager also has a considerable number of extensions and themes.

A feature called "Quick Edit" allows the user to select a tag in (a html file, for example) and edit the associated style without switching over to the css document. It also supports SASS and LESS pre-processors.

Brackets is being actively maintained and developed.

Hovering over colors hex codes or image paths will pop up previews of corresponding colors and images.

Brackets supports drag and drop of text, as well as multi / rectangular selection.

The editor is built using html, css, and javascript, making it extendable by any front-end developer.

You can have your cursor independently on multiple lines and so creating templates and/or editing multiple things at once is really fast and easy.

Vim-style editing is already built in the text editor.

A default extension allows for the extraction of PSD resources, such as images and styles. There's good integration for placing extracted resources into source.

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.

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.

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.

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.

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.

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.

Can be used from within Ansible to install packages on macOS.

This one works brilliantly.