- A PHP-Oriented Review

Created: Tue, 08 Apr 2014 00:00:00 GMT

Updated: Sun, 02 Jan 2022 18:30:26 GMT

Time to read: 1 minute

Cartoon image by @tpope: Parody of Mac vs PC commercials from the early 2000s. One man represents Vim and the other represents emacs. A third man appears and claims to represent Atom. The first two men are then seen beating up the Atom man.
Image credit: Tim Pope @pope

Last week, I gave a short demo of the text editor to the Kansas City PHP User Group. I realized after-the-fact that I had presented the early-release as an IDE, when I should have presented it as a fancy text-editor.

Coming from using PHPStorm as my primary PHP IDE, Atom seems like a cute, yet unintelligent cousin.

I tried to find things to like about it from a PHP point-of-view. After enabling autocomplete and PHP snippets, I could appreciate the text editor as just a text editor. Code completion is currently maddening in that it shows absolutely everything ever typed; therefore, it shows nothing of value. The code snippets were more interesting. Creating a foreach loop stub in PHP was as simple as typing foreach <tab>. If I were in a <?php ... ?> segment, I would get a nice foreach loop stub within which to fill in the blanks; yet, if I were in an <html>...</html> segment, I would get a nice <?php foreach ... ?> stub within which to fill in the blanks. I appreciate that the PHP, JavaScript, and HTML stubbing is container-aware.

From a PHP point-of-view, that was the only positive which I could find for the text editor. I made certain to explain that the editor is not yet ready for Prime Time nor are its PHP flavorings fully fleshed out. The editor holds great promise for PHP and code-in-general, but until it can fulfill that promise, I will prefer VIM for editing text and PHPStorm for a PHP IDE.

After my largely negative review, I was still able to hand out at least 2 invites.

I look forward to what comes next for


This site is built using Gatsby, TailwindCSS, and a whole bunch of other fun stuff.

Corrections or curious to see how this was put together? Check out the latest version of this site at its github repo.