No, the Atom text editor does not have an uninstaller. On Mac OS X, to completely uninstall, remove the following files and directories:

~/.atom
/usr/local/bin/atom (NB only present if command line tools installed)
/usr/local/bin/apm  (NB only present if command line tools installed)
/Applications/Atom.app
~/Library/Application Support/com.apple.sharedfilelist/com.apple.LSSharedFileList.ApplicationRecentDocuments/com.github.atom.sfl
~/Library/Preferences/com.github.atom.plist
~/Library/Application Support/com.github.atom.ShipIt
~/Library/Application Support/Atom
~/Library/Caches/com.github.atom.ShipIt/
~/Library/Saved Application State/com.github.atom.savedState
~/Library/Logs/Atom/
~/Library/Preferences/com.github.atom.helper.plist
~/Library/Preferences/com.github.atom.LSSharedFileList.plist
~/Library/Preferences/ByHost/com.github.atom.ShipIt.<letters/numbers>.plist
~/Library/Saved Application State/com.github.atom.savedState
```text
*NB:* The `<letter/numbers>` in the file name located in `~/Library/Preferences/ByHost` appear to be a unique string per machine.

*NB:* Some of these files/directories may not be present. Older installations are likely to have all of them. Some of them aren't on my system with a new Atom install.

**DO NOT, UNDER ANY CIRCUMSTANCES, COPY AND PASTE THE CODE ABOVE INTO THE TERMINAL WITH `rm`.** The code contains spaces and cannot be used on the command line without escaping the spaces.

I installed the Atom text editor quite a while ago and didn’t have much time to play around with it. Last week a friend of mine brought it up in conversation. She was extolling its virtues. I decided now would be a good time to try it out. I was moving a site to Hugo and it has a plugin for Hugo syntax.

So I fired it up and, my word, a decade later an editor window opened. What took it so long to open? I poked around a bit and noticed that I had installed a bunch of packages when I first downloaded it. So I disabled the vast majority of them, then restarted. A minor improvement. Disabled the rest. Restarted. Another minor improvement. Then I disabled some core packages for languages I wouldn’t use. No help for the incredibly slow start time.

I use drush to execute cron on my Drupal sites. After upgrading drush from version 5 to version 8, I started receiving empty emails from cron each time drush was executed. Checked my cron entries and everything looked fine. Researched a whole bunch on the Internet. Couldn’t find much of anything about empty emails related to drush so I redirected the output to a log. Sure enough, even with the –quiet option, drush cron still outputs a blank line. Why? I’ve no clue.