Is there something in PhpStorm that is not in VSC, something so fundamentally necessary that it is worth considering as an alternative?

Question

PHP

I work at VSC (switched three years ago from Notepad++ :) I'm

very satisfied. But now it popped into my head:

- Why does PhpStorm have so many users (many colleagues work in it) - maybe there is something there that I don't know about?

"Installing and trying" is not an option - to get a feel for an IDE, you need weeks of real work in it - but working in a new IDE is a pain :)

Therefore, the question for connoisseurs is whether it is worth testing the awl tightly if there is already normal soap?))

Thank you.

Answer 1

VS Code is a good editor. And if you add plug-ins, then the possibilities will approach a full-fledged IDE.
PhpStorm is a complete IDE out of the box. Installed and you have everything right away and working.

Therefore, the question for connoisseurs is whether it is worth testing the awl tightly if there is already normal soap?))

In my opinion, it's worth it. But a couple of days won't be enough. You need a week or two to sit and get used to it. And then you won't get off.

Answer 2

Your question doesn't make sense.
It is about the same as "I drive a KIA PIcanto, I feel comfortable, but they advise me to change to a Jeep Grand Cherokee."
Comfortable - so ride what you can.
There is only one reason to switch to Storm - it is the standard in advanced teams.
Accordingly, if you get into a team where interaction is accepted, it will be easier.
From personal experience - I moved a few years ago from the same npp to Storm, I do not regret it.
But then VSC was miserable.

Answer 3

I will add the advantages of PHPStorm:

• you can work in several php, switching on the fly (for example, we are working on two projects, one on 5.3, the second on 7.4). VSCode takes the default one and to switch you need to change the path. Maybe in plugins, but you need to check
  
• The desired line wrapping format. You can customize a lot. This is important in projects where there is a certain style code with its own transfers (you can use a file with parameters, but VSCode misses a lot)
  
• Working with frameworks. It is enough to open a project on Laravel and it is immediately clear that in the IDE you need to check the box "this is Laravel" and that's it (it is immediately offered). There is a cool paid plugin, but I did not use it. VSCode is going crazy, I installed a few plugins, the situation has improved, but facades are still a problem.
  
• PHPStorm works well with js (it has functions from WebStorm), except for creating new package projects that you can simply create from the console
  
• There are too many plugins in VSCode. Yes, I consider this a disadvantage. Example, you need a plugin to work with sftp (ftp via ssh), VSCode has a bunch of similar plugins. Ok, let's install the most popular one. I. It doesn't work. Okay, let's install the second one. It throws an error, but it works. We look at the third, this is a fork of the second, which simply does not show an error. And there are many such situations. By the way, for normal work with PHP in Soda, the plugin is paid, after a while he asks to buy it (I just close the notification and work on, but it's a little annoying). PHPStorm works out of the box with ssh
  
• PHPStorm has a cool code analyzer (yes, because of it, weak computers just broadcast), which gives useful (and not so) tips.
  
• Uses PSR
  
• Autosubstitution. She is very comfortable here. At the same time, the necessary things are substituted (vscode substitution works correctly with JS, in php often some kind of "game" is substituted)
  
• Working with git, and I really enjoyed working with conflict resolution. Also no problem with update. Just click Update and the code update is downloaded, conflicts are resolved immediately, and if it doesn’t work out, then it is requested from the user. Other programs cannot update the project if you have corrected the file and there is a new version elsewhere in the file.
  
• Working with BD, plus the analyzer writes SQL query errors directly in the code
  

Cons compared to VSCode:
* Speed. VSCode opens much faster
* Free
* There are a lot of plugins for working with different files
* I use it for quick editing of files, for example, I need to fix a line in the code or a small function (instead of notepad).

Answer 4

PhpStorm is a great ide, there is a 30 day trial for testing. There is something else, google
1. You need to choose the appropriate version, it’s better not to have a fresh release, but for example PhpStorm 2021.1.2. New ones are often not optimized and slow down a lot. This version, which works fine for me, does not lag, does not freeze. At the same time, 6 projects on laravel and yii are open.
2. There are a lot of things out of the box and you can add useful and convenient features through plugins. It makes no sense to write about them, you can just find articles or reports and watch the first article from Google zhurov.me/blog/phpstorm-base-features.htmlbut again, you need to get used to it. And every month you can find and apply new features and hotkeys, which speeds up and helps you write code, refactor, debug and find the right pieces of code in a very short period of time.
I got used to PhpStorm for about a couple of weeks and after 7 years, I will say that this is a different ide.
Holivar, who opened Dmitry Belyaev, is a matter of taste, judging by his commentary, he especially used PhpStorm and used it through force, and not in order to switch to it. Yes, and his development on js, which I think also affects the choice of ide, we have front-end developers also on VSCode, backend on PhpStorm