When comparing IntelliJ IDEA vs aText, the Slant community recommends IntelliJ IDEA for most people. In the question“What are the best power user tools for macOS?” IntelliJ IDEA is ranked 37th while aText is ranked 48th. The most important reason people chose IntelliJ IDEA is:
IDEA places an emphasis in safe refactoring, offering a [variety of features](https://www.jetbrains.com/idea/features/refactoring.html) to make this possible for a variety of languages. These features include safe delete, type migration and replacing method code duplicates.
Ranked in these QuestionsQuestion Ranking
Pro Smart refactorings
IDEA places an emphasis in safe refactoring, offering a variety of features to make this possible for a variety of languages.
These features include safe delete, type migration and replacing method code duplicates.
Pro Fast and smart contextual assistance
Uses a fast indexing technique to provide contextual hints (auto-completion, available object members, import suggestions).
On-the-fly code analysis to detect errors and propose refactorization.
Pro Android support, JavaEE support, etc
A very complete development environment support.
Pro Stable and robust
IntelliJ IDEA hardly ever crashes or has any issues that plague other Java IDEs like file corruption or slowness.
Pro Lots of plugins
Many plugins are available for almost any task a developer may need to cover. Plugins are developed by Jetbrains themselves or by 3rd parties through the SDK available for writing them.
Pro Support for many languages
IntelliJ supports many languages besides Java, some of these are: golang, Scala, Clojure, Groovy, Bash, etc.
Pro Intuitive and slick UI
IDEA has a clean, intuitive interface with some customization available (such as the Darcula theme).
Pro Clear and detailed documentation
The documentation is exhaustive, easy to navigate, and clearly worded.
Pro Free version available
There is a free community edition (open source) and an ultimate edition, which you can compare here.
The ultimate edition is available for free for one year for students but must be registered through an .edu e-mail account.
Pro Many convenient features
These simplify the daily work, e.g. copy/cut a whole line without the need to select it.
Pro Very powerful debugger
With ability to step into a certain part of a large method invocation (Shift+F7), drop frame, executing code snippets, showing method return values, etc.
Pro Gradle support
Pro Buit-in Git support
Pro No Update
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 Has built-in snippets for common typos
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 A snippet can be expanded to plain or styled text and include pictures
Con Slow startup
Startup can be slow deepending on system configuration
Con Uses a lot of RAM
Con Standard hotkeys behave differently
Seems like hotkeys assignment in Idea has no logical consistency.
Like «F3» is usually next match, «Ctrl+W» - close tab, etc — they map to some different action by default.
There is a good effort in making the IDE friendly for immigrants from other products: there are options to use hotkeys from Eclipse, and even emacs. But these mappings are very incomplete. And help pages do not take this remapping into account, rather mentioning the standard hotkeys.
So, people coming from other IDEs/editors are doomed to using mouse and context menus (which are rather big and complex).
Con Bugs are not solved as often as they should
They are more interested in adding new features or issuing new versions than solving bugs.
Con Cannot open multiple projects in the same window
Con Built with closed source components
The version with full features is not opensource. Parts of the code are under apache licence though.
Con Lack of plugins
IntelliJ supports a very small amount of plugins. Although these are 'quality approved', many features are missing and can't be implemented because of that.
Con Doesn't work in Mojave
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.