PhpStorm vs WebStorm

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.

Supports Symfony2 (including Twig and Doctrine), Yii frameworks, and Laravel.

PHPDoc is a documentation generator. It allows automatically generating documentation from specifically formatted comments.

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.

Has built in support for Xdebug including remote debugging.

Phar support allows running complete applications out of .phar files.

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).

Ability to setup custom external commands, which is something inherited from eclipse and found lacking on netbeans.

Allows users to manage their repositories directly from the IDE with a GUI which lets you do all Git commands.

Active development work on plugins is always a plus, as it can extend the use of the IDE.

Quickly rename classes, methods, and variables used across multiple files in the project.

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.

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.

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.

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.

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.

It recognizes Vagrantfile and allows full control from the IDE.

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.

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.).

PhpStorm is clearly being developed continually, which gives confidence that it will be available for some time and is not abandonware.

Especially the "find in path" feature that displays both results and file preview!

WebStorm integrates with Node.js to allow for running, debugging, and unit testing of Node.js apps.

To make sure your code can be easily maintained, you must first be sure to make it clean and tidy. This is the part where WebStorm really helps you. It automatically refactors your code by performing functions on it, such as extraction of variables, moving files, inline variable extraction, etc.

WebStorm comes bundled with JSHint and JSLint. JSCS, ESLint, and Closure Linter can be installed via npm. They register as inspections and are customizable through IDE settings. They run automatically and will highlight potential issues. Pressing alt+enter on an issue will allow the user to view suggested fixes.

WebStorm has two types of autocompletion: structural completion and word expansion.

Structural autocompletion makes predictions based on its understanding of JavaScript objects, 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.

The local history feature in Webstorm tracks all your local changes in the source code that you are making. You can use it to view changes that you've made to your code and roll back whenever necessary.

WebStorm offers typescript support for building typed JavaScript applications which improves refactoring and code completion, as well as helping to find bugs.

WebStorm includes support for Meteor, Angular, and React.

WebStorm includes a feature called Live Templates. Live Templates are predefined code snippets that can include variables. They're intended to increase productivity by reducing the amount of repetitive code that has to be written.

When you install WebStorm, it allows you to choose from other IDE's for it to base it's hot keys on. So if you are switching from another IDE, it makes it a very easy transition and productivity is not adversely affected by having to learn new hot keys.

WebStorm has a powerful visual git tool, allowing for easy commits, visual diffing, merging, push/pull, rebasing, and inspecting the VCS history of a project. GitHub is supported natively - you can check out a project directly from GitHub.

WebStorm has support for Grunt and Gulp task runners.

WebStorm (and really all of the IntelliJ IDEs) support the plugins throughout their plugin ecosystem which leaves you with 100s of tools to handle your automation tasks. There is a wide range of build-related plugins that help you by having pre-defined commands to execute with the click of a button. Out of any other IDE, WebStorm has by far the most coverage when it comes to tools for your development workflow.

The theme is very easy to customize to your liking. You can change font-size, colors, highlighting colors, and more.

Webstorm supports not just Git and Mercurial, but Subversion, CVS, and Perforce as well.

This integrates with other community tools like ESLint and editorconfig.

Code Templates are powered by Apache VTL (Velocity Template Language) and allow for includes, custom variables, conditional blocks, iterators, and live templates.

Webstorm comes with icons for many filetypes which makes it easier to find what you're looking for in the project list.

WebStorm has a built-in webserver that allows you to run projects from http://localhost:63342/ProjectName.

The IDE comes with a built-in terminal, a feature lacking in some lighter editors.

WebStorm has built-in support for CoffeeScript and Dart.

Karma allows you to execute unit tests and monitor code coverage. You can read more about using Karma with WebStorm here.

WebStorm has built-in support for Sass which is one of the most stable and powerful CSS extension languages.

WebStorm has a powerful debugger, with support for conditional breakpoints.

With the settings repository, you can easily enforce your development standards.

Non-commercial open source projects, and students and teachers (including classroom licenses) may qualify for a free license. There is a 50% off license for startups (under 3 years old). You can read more about it here.

It is able to specify for example node versions, which will be used to run task for current project.

Assists with configuration and understands module resolution.

Cordova allows for building native mobile applications via HTML, CSS, and JavaScript.

Autocompletion, syntax-highlighting, refactoring, and pub integration for Dart are supported in WebStorm.

Autocompletion, syntax-highlighting.

It may seem like a complex IDE and it does have a lot of functionality, yet it uses way less RAM than barebones-looking, Electron-based IDEs.

Makes adjusting an existing or creating new themes a breeze. Especially due to things like inheritance, as well as easily exporting/distributing/importing the color settings which really only store where on deviates from the defaults (thus the resulting files are very small and relatively human-readable).