MacVim vs Homebrew

Every plugin available for Vim is available for MacVim too.

MacVim is Vim, meaning it has all of Vim's customizability and power.

MacVim supports OSX's native shortcuts making the adoption of Vim easier.

MacVim, like Vim itself has a large community backing it.

In cases of a selected font missing certain characters, MacVim will find a font that has that character.

Vimtutor is an excellent interactive tutorial for people with no prior experience of Vim. It's bundled with Vim and takes about 30 minutes to complete.

Vim associates keys with words. For example, d is for "delete" and w is for "word". To perform an action you string together letters. Thus, to delete a word, press dw.

This way it's possible to abstract a large amount of functionality that Vim provides in an intuitive way.

Interaction with Vim is centered around several modes. Each mode has a different purpose and switching between them changes behaviour and keybindings. There are 12 modes in total (six basic modes and six variations on basic modes) and four of them are used commonly.

Insert mode is for entering text. This mode most resembles traditional text entry in most editors.

Normal mode (the default) is entered by hitting ESC and converts all keybindings to center around movement within the file, search, pane selection, etc.

Command mode is entered by hitting ":" in Normal mode and allows you to execute Vim commands and scripts similar in fashion to a shell.

Visual mode is for selecting lines, blocks, and characters of code.

Modes allow separating concerns between various tasks and reusing keys for different kinds of functionality. As a result, the workflow becomes more efficient.

Permits writing characters that don't fit in one byte, most notably logograms (for writing in languages such as Japanese, Chinese, and Korean) and Unicode characters.

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

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.

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.

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

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.

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.

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.