When comparing aText vs Homebrew, the Slant community recommends Homebrew for most people. In the question“What are the best power user tools for macOS?” Homebrew is ranked 2nd while aText is ranked 49th. 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.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro No Update
Pro A snippet can be expanded to plain or styled text and include pictures
Pro Has built-in snippets for common typos
Pro Cheaper than competition
$4.99, cheaper than textExpander ($35)
Pro Compatible with TextExpander snippets
TextExpander snippets can be imported into aText
Pro Works with VMs
Pro Imports from most alternative text expansion apps
aText can import data from TextExpander, TypeIt4Me, SpellCatcherX, Automaton and CSV file.
Pro Has common HTML & JS snippets built-in
Pro Snippets can include editable fields
Pro Data can be synced through cloud storage services
Pro Snippets can include a wide variety of variables
Possible variables include date, time, other snippets, clipboard content, etc.
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 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 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.
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 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 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.
Cons
Con Doesn't work in Mojave
The current version, with no issues. In fact, I've never had any issue with it with Mojave, so I assume when Mojave was released, aText was already up to date for it.
Con Frequent crashes in MacOS Sierra
aText crashes frequently, and the developer is unresponsive. Not clear if app is supported or under current development: last update was in 11/15; last post to aText Facebook page 10/15.
Con Long time no update
Seems to be abandoned.
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 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.