When comparing Emacs vs PhpStorm, the Slant community recommends Emacs for most people. In the question“What are the best JavaScript IDEs or editors?” Emacs is ranked 9th while PhpStorm is ranked 11th. The most important reason people chose Emacs is:
Emacs can be controlled entirely with the keyboard. While true, I often find the mouse and menus handy for those lesser-used commands. An aide-memoir.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Keyboard-focused, mouse-free editing
Emacs can be controlled entirely with the keyboard. While true, I often find the mouse and menus handy for those lesser-used commands. An aide-memoir.
Pro Total customizability
Customizations can be made to a wide range of Emacs' functions through a Lisp dialect (Emacs Lisp). A robust list of existing Lisp extensions include the practical (git integration, syntax highlighting, etc) to the utilitarian (calculators, calendars) to the sublime (chess, Eliza).
Pro It's also an IDE
You can debug, compile, manage files, integrate with version control systems, etc. All through the various plugins that can be installed.
Pro Works in terminal or as a GUI application
You can use Emacs' command line interface or graphical user interface.
Pro Self documenting
Emacs has extensive help support built-in as well as a tutorial accessed with C-h t.
Pro Free
Licensed under GNU GPL.
Pro Great documentation
With 30+ years of use the Emacs documentation is very thorough. There are also a lot of tutorials and guides written by third parties.
Pro Vi keybindings through Evil mode
Evil mode emulates vim behaviors within Emacs. It enables Vi users to move inside the Emacs universe.
Pro Provides org-mode
Advanced planning and publication which can start as a simple list.
Pro Enormous range of functionalities (way beyond simple "text editing")
Through its programmability, a very broad range of functionalities can be integrated in emacs, turning it even into a "single point of contact" with the underlying operating system.
Pro Cross-platform
Works on Linux, Windows, Macintosh, BSD, and others.
Pro Integrates planning in your development process
You can jump straight from your org-mode files to programming tasks - and back - and build a seamless workflow.
Pro Versatile
Emacs is great for everything.
Pro Mini buffer
You can pass complicated arguments in the mini buffer.
Pro Ubiquity
Fully compliant GNU-emacs is available on many platforms, and they all understand .emacs configuration files.
Pro Rectangular cut and paste
Emacs can select rectangularly.
Pro Lisp customizations
With lisp customization, any behavior of Emacs can be changed. Update with pre-release patch can be also applied without recompiling the whole Emacs.
Pro Visual selection and text objects with Evil
Evil is an extensible vi layer for Emacs. It provides Vim features like Visual selection and text objects.
Pro dabbrev-expand (Alt-/)
Dynamic word completion.
Pro Support multi-line editing, multiple frame, powerful paren, crazy jumping style
Review the "Emacs Rocks" video.
Pro Has been widely used for a long time
The first verion of Emacs was written in 1974 and GNU Emacs in 1984.
Pro Helm plugin adds even more power to Emacs
Powerful commands, search, and more with the Helm plugin.
Pro GTK+ widgets support
Since version 25 you can run GTK widgets inside Emacs buffers. One of these is the WebKitGTK+, which allows the user to run a full-featured web browser inside Emacs with JavaScript and CSS support among other things.
Pro Excelent tutorial to get you started
The tutorial you are presented with at startup shows you exactly what you need to get started and teaches you how to use the built-in help yourself later.
Pro Interactive Shells
Emacs has a number of shell variants: ansi-term, shell, and eshell.
Pro Emacs provides magit, the best and most complete GIT interface
Complex git history editing become a breeze with very few keystrokes. And simple ones are quickly stashed in muscle memory. Git becomes an direct extension of your brain thanks to Magit. Cherrypicking, blaming, resetting, interactive rebasing, line level commit, spinoff branches... you name it, magit already has it and has typically all those 5 to 10 git CLI commands of higher-level patterns also tide to one simple shortcut (want to amend a commit three commits away ? forgot to branch out and you've got already N commits on master
? ... etc... ).
Pro Gnus
Managing several large mailing lists has never been easier using Gnus. The threading commands and the various ways of scoring articles means that I never miss important messages/authors, etc. A joy to use.
Pro Eshell is cross platform
You can use the underlying operating system shell as a terminal emulation in an Emacs buffer. Don't like the default shell for your configuration? You can change it to your liking.
Pro Excellent Lisp editing support
Built-in packages make editing Lisp source code feel natural.
Pro Use-package and org-mode
Missing some neural package that predicts actions, maybe in the next release ...
Pro Intelligent code completion
PhpStorm has two types of autocompletion: structural completion and word expansion.
Structural autocompletion makes predictions based on its understanding of PHP, while the latter tries to predict the word currently being typed based on previously typed words. Word expansion also works in comments and docstrings and it's similar to vim's omnicompletion.
Both types of autocompletion work extremely well, have little to no problems and are quite fast even when loading suggestions on the go.
Pro Supports various PHP frameworks
Supports Symfony2 (including Twig and Doctrine), Yii frameworks, and Laravel.
Pro PHPDoc support
PHPDoc is a documentation generator. It allows automatically generating documentation from specifically formatted comments.
Pro Inspections of all kinds
Not just for PHP, HTML and JavaScript, but especially good is SQL inspection and auto-completion of tables and fields. You can see at a glance, that your DB structure is in sync with your code.
Pro Built-in debugger
Has built in support for Xdebug including remote debugging.
Pro Phar package recognition
Phar support allows running complete applications out of .phar files.
Pro Database view
The database tab, while not perfect, provides all the tools you need for daily usage. You always have your DB overview on the side (you can hide it when not needed).
Pro External command support
Ability to setup custom external commands, which is something inherited from eclipse and found lacking on netbeans.
Pro Integrated Git GUI support
Allows users to manage their repositories directly from the IDE with a GUI which lets you do all Git commands.
Pro Plugins allow futureproofing and customization
Active development work on plugins is always a plus, as it can extend the use of the IDE.
Pro Code Refactoring
Quickly rename classes, methods, and variables used across multiple files in the project.
Pro Auto-sync with remote folders
It allows monitoring code and sync the files that need to be changed with a remote server. This works more efficiently than libnotify and faster than vagrant auto rsync.
Pro Lots of plugins
Lots of plugins from JetBrains and the community are available, from useful things like support for Docker, Vagrant, Angular, Vue.js and more useless (but fun) like a nyan cat progress bar.
Pro Zero latency typing
Type codes with pleasure. Delay of visual feedback on a computer display has an important effect on typist's behavior and satisfaction, as cited here.
Pro Has built-in console and SSH clients
This allows execution of needed commands without switching to other windows. It also keeps track of what's happening right in the IDE, which is especially good with Vagrant, because you can connect to a VM in a single click.
Pro It comes with Testing RESTful Web Services
Save time of building your own or integrating libraries for testing RESTful Web Services. PHPStorm enables you to test endpoints without leaving your workspace or disrupting your workflow . You can code your endpoints in one window and test it immediately from another window.
Pro Integrated Vagrant support
It recognizes Vagrantfile and allows full control from the IDE.
Pro Templating support
Supports Twig and Laravel's Blade (among others). Technically the later is part of a framework which Phpstorm supports but I've seen IDEs (e.g. Netbeans) with Laravel support but no blade support so it does deserve a notable mention.
Pro Responsive core developers
Pro Emmet integrated
Pro Task/Context functionality
Similar to Eclipse Mylyn: you can create tasks or retrieve them from your ticketing system, and each task keeps its own context (opened files, modifications, etc.).
Pro Regular updates for fixes and new features
PhpStorm is clearly being developed continually, which gives confidence that it will be available for some time and is not abandonware.
Pro Excellent search tools
Especially the "find in path" feature that displays both results and file preview!
Cons
Con Learning curve is long
While it's better than it used to be, with most functions being possible through the menu, Emacs is still quite a bit different from your standard editor. You'll need to learn new keyboard shortcuts.
Con Sometimes the extensibility can distract you from your actual work
If I ever want to lose half a day, I'll start by tweaking my .spacemacs config file.
Con Keyboard combinations can be confusing for new users
For example, for navigation it uses the b, n, p, l keys. Which for some people may seem strange in the begging. However they can be changed easily.
Con Documentation is not beginner-friendly
Although lots of good built-in documentation _exists_, I have after four years of Emacs as my primary editor not figured out how to actually make use of it, and rely completely on Google / StackOverflow for help.
Con User interface is terrible
I was using Emacs in the early 1980's, before there were GUIs. In fairness to Emacs, its original design was conceived in that context and is rather good at some things, like flexible ability to bind commands to keyboard shortcuts. Unfortunately, it didn't keep up with the times and fails to take advantage of the entire world of GUI design that's revolutionized computer science since then. So Emacs does 5% or what an editor should do quite will, and is surprisingly under-powered and old fashioned at the other 95%. To this day, it lacks or struggles with very basic things, like interactive dialogs, toolbars, tabbed interface, file system navigation, etc., etc. The things I just mentioned, are all present in some limited and inept form, but falls far short of current standard of good user interface design. For this reason, I would not recommend Emacs to anyone who is under 50 year old, or who needs power user capabilities. For casual, unsophisticated applications by someone who grew up with green screen character based computers, it's probably OK.
Con Emacs lisp is very poorly designed
The language that's used for user customization, extensions, and for much of the basic editor functionality, is Emacs lisp, or elisp for short. I actually like lisp in general, especially Scheme, but unfortunately, elisp is one of the worst versions of lisp ever created, barely meriting being called lisp. It's very slow, impoverished in features, inconsistent, and rather inelegant in design. Elisp needed to be overhauled 20 or 30 years ago, but the Emacs developers were not willing to do the work. I believe this is one of the major reasons Emacs is so buggy, lacking in features, development is so slow, and consequently almost nobody uses it (or should use it) anymore.
Con Very poorly maintained
It's not clear to what extent Emacs is still supported. There's still some development taking place, but so slow that it's almost an abandoned project. There are numerous bugs in Emacs, many these days associated with start up and package management. When you search the Internet for solutions, you often find many posts, sometimes going back months or even years, with no clear fix.
Con Hard customization
For customization, you need to learn Lisp.
Con A lot of jokes in this serious software
Con Using Emacs on a new machine without your .emacs file
Con Resource exhaustive
It often maxes out even 4 cores, not to mention several hundred MBs of RSS with a single small project opened.
Con Proprietary
It is not free software (free as in freedom).
Con Costly or you need github education pack
If you are ready to pay for it for phpstorm then it is better otherwise you need github education pack or if you have'nt either github education pack or you are not ready to pay it then visual studio code insiders is best option.
Con Slow performance
A very slow indexing, many memory leaks, large projects after some time will be very slow, opening large files like 10mb can even break IDE.
Con FTP Extremely Slow
FTP File transfer is extremely slow compared to filezilla or other ftp programs
Con Sometimes buggy
Index gets corrupt which results in errors in syntax presentation, code validation and auto-completion. Version-control system sometimes stops working, occasionally freezes in big files