When comparing zsh vs aText, the Slant community recommends aText for most people. In the question“What are the best power user tools for macOS?” aText is ranked 49th while zsh is ranked 53rd.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Interactive autocompletion
When you start typing a command, you can press the tab key and it will complete the command you started typing. If there are multiple potential commands, you can choose which one to run by simply pressing tab again. Case-insensitive by default, too.
Pro Powerful community-driven tools via oh-my-zsh
Oh-my-zsh is a community-driven framework, which helps users with their zsh configuration and plugins. 400 plugins, 200+ themes and auto-updates to always be up to date.
Pro Autocomplete for options
Zsh intelligently determines if you are trying to complete a file path or an option, and pressing tab after typing -
will reliably bring up a list of options.
Pro Good bash compatibility
Things you've learned using bash will largely apply to zsh. Scripts written in bash will run with little to no modification.
Pro Safer variable behaviour
Unlike Bash, zsh does not split unquoted variables by default, making it less error-prone.
Pro Recursive globbing
ls **/*.log
for example is supported by ZSH.
Pro Great install procedure
Zsh will take you through a procedure which is roughly 30 minutes in length before during install. Through this procedure it asks you to set different options and customize the shell the way you want it to. Most of these settings are also found in other shells, but to customize them you have to go dig configuration files while zsh allows you to do it in the beginning.
Pro Shared histories
If you spend a lot of time in the terminal, most likely you will have several terminal windows open. Zsh has great support for command line histories. The history is unique and shared through all the different instances.
Pro Smart escaping
Zsh can determine the context of the command you're typing in and determine if it should escape characters if you're typing in a URI.
Pro Pipe output to a temporary file:
Some programs don't support loading from stdin, but ZSH can store outputs to a temporary file, example: unzip =(curl http://example.com/someZipFile.zip)
Pro Faster spelling correction
Zsh' s correct (or correctall) is vastly superior to Bash's attempt at spelling correction.
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.
Cons
Con Not fully compatible with bash
There is a small chance you may have a bash script that doesn't work in zsh, although this is very very rare and most developers will never run into any issues.
Con Requires a lot of configuration to be used fully
Zsh requires a lot of tinkering with configuration files and downloading plugins in order to be able to do tasks which other shells may be able to do out of the box.
Con Defaults are unfriendly for a long-time bash user
Expect to find a configuration you like (or use the configuration utility) to set reasonable preferences. Default zsh interaction is different enough to make you stutter through what used to be familiar workflows.
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 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 Long time no update
Seems to be abandoned.