Need advice about which tool to choose?Ask the StackShare community!
PhpStorm vs Visual Studio Code: What are the differences?
Developers describe PhpStorm as "Professional IDE for PHP and Web Developers". PhpStorm is a PHP IDE which keeps up with latest PHP & web languages trends, integrates a variety of modern tools, and brings even more extensibility with support for major PHP frameworks. On the other hand, Visual Studio Code is detailed as "Build and debug modern web and cloud applications, by Microsoft". Build and debug modern web and cloud applications. Code is free and available on your favorite platform - Linux, Mac OSX, and Windows.
PhpStorm and Visual Studio Code are primarily classified as "Integrated Development Environment" and "Text Editor" tools respectively.
"Best ide for php", "Easy to use" and "Functionality" are the key factors why developers consider PhpStorm; whereas "Powerful multilanguage IDE", "Fast" and "Front-end develop out of the box" are the primary reasons why Visual Studio Code is favored.
Visual Studio Code is an open source tool with 78.4K GitHub stars and 10.9K GitHub forks. Here's a link to Visual Studio Code's open source repository on GitHub.
According to the StackShare community, Visual Studio Code has a broader approval, being mentioned in 1104 company stacks & 2298 developers stacks; compared to PhpStorm, which is listed in 637 company stacks and 493 developer stacks.
When I switched to Visual Studio Code 12 months ago from PhpStorm I was in love, it was great. However after using VS Code for a year, I see myself switching back and forth between WebStorm and VS Code. The VS Code plugins are great however I notice Prettier, auto importing of components and linking to the definitions often break, and I have to restart VS Code multiple times a week and sometimes a day.
We use Ruby here so I do like that Visual Studio Code highlights that for me out of the box, with WebStorm I'd need to probably also install RubyMine and have 2 IDE's going at the same time.
Should I stick with Visual Studio Code, or switch to something else? #help

If you're working with both Ruby and JavaScript, buy RubyMine and shut down the other two. It's much better for Ruby than Visual Studio Code is. It can also do everything WebStorm does, if you install the plugins you need from JetBrains, and they all work together nicely.

If you install RubyMine, you shouldn't need WebStorm, as all the functionality of WebStorm appears to be included in RubyMine. (See here: https://softwareengineering.stackexchange.com/a/132950).
I've used PhpStorm for several years and have never needed to open (or even download) WebStorm for anything front-end or JavaScript related.
I work at the same company as you and I use WebStorm for 99% of my tasks. I also have RubyMine installed and use that when I have to tweak some backend code. I tried using RubyMine for JavaScript but was unhappy with how it felt and I believe that WebStorm is faster because it has less plugins and language extensions running. Summary: Buy and use WebStorm for primary development and keep VS Code around for when you have to touch Ruby.

JetBrains all the way - my entire team uses PhpStorm and none of us would even consider switching.
The availability of IDEs for other languages along with consistency in environment and keyboard shortcuts is also a godsend, which is the reason I'd also choose Rider over Visual Studio (but also VS for Mac is trash, but I digress...)

I've never had much issue running multiple IDEs and generally pick them based on the languages they best support. For front end work where I mainly use TypeScript, I stick heavily with Visual Studio Code. However, for backend work which we do primarily in Python, PyCharm is my go-to editor. The one thing that I do however is I do remap keyboard shortcuts so I get consistent keyboard ability even when I switch IDEs.

If I have to choose one I would go with VS Code; it’s become pretty mature and keeps getting better. If those plugins are creating problems for you then just uninstall them, find an alternative, or make a PR to fix. But at the end of the day these are IDE’s and they are meant to save you time. I would go with whatever helps you develop code faster. If restarting VS code slows you down then make a switch, that personally would annoying the crap out of me. Else maybe it’s a quick restart, not the end of the word, hopefully someone will fix at some point.

Visual Studio Code is a text editor. And this is best option in my opinion. For Ruby, I cannot say how VS Code is good. If you wanna choose IDE, RubyMine should fit your needs. Because IDEs are more compatible with major needs. But text editors are just text editor. You can do same things with also text editors. I recommend to try both VS Code and RubyMine. And you will be able to find which fits better for your needs

So here is the deal man, bottom line you want to write code. All of these tools are built in a mouse-driven world, they are designed not for engineers, but office monkeys. If you want a real workflow that gives you ultimate performance, customization and speed you need to use a modal editor, I suggest NeoVim. Start using it 20% of the time on single file edits, watch youtube videos about it and teach yourself vim gestures. It will infuriate you for 6 weeks, make you cry for another 2 months. But as you use it more, as long as your usage goes over 40% of the time, in 6 months you will understand why most of the world's too engineers use it. Settling on lesser editors out of laziness is exactly the attitude that results in shitty the engineering. Yeah it's hard. You're smart. You do hard things. Once it isn't hard anymore you will blow yourself away at how much more efficiently you edit files.
Also vim keybindings in a mouse driven editor does not cut it. Managing files, buffers and workflow is half of the value of vim/neovim. It is OK if you have to use an IDE (currently I only use an IDE for java development, so I have little choice)
So use VSCode while you teach yourself vim.

I've used all of these IDEs and VSC is probably the best overall. WebStorm, PHPStorm, and other Jetbrains IDEs are great for projects that only use the language that the IDE was designed for. But, Visual Studio Code on the other hand has so many extensions and works with so many languages.

Well you can try for a while MacVim because it is already configured with tons of plugins. My favourite text editors are Sublime Text and TextMate which are lightweight and speedy. My feeling is that JetBrains IDEs are making you brainless.

I usually have both running but do the bulk of my language work in the appropriate JetBrains flavor. One thing to watch out for in VS is that under the hood it is running the tools needed for whatever language you are working with. This is where tools like JetBrains shine. While I am sure you can tune the heck out of what you use in VS, the provides context and clarity...

I'm personally a Visual Studio Code fan. I've used it for both Go and Java. It really depends on the quality and support of the plugins. Typically VS Code doesn't crash as much as a bad plugin causes an unforeseen error. Make sure you stay up to date and look at alternative plugins.

If you find something that works and are comfortable with it, stay with it. Changing IDE's and learning their idiosyncrasies takes valuable time away from programming while learning setups and keyboard short cuts. I personally use VS Code for cost and decent multiple language support. I've had issues occasionally with it locking up, but it is under heavy development and continually improving. I have also found it more intuitive for new programmers. ** Having profiles for different languages can reduce the amount of plugins running and issues they can cause.

Are you using the prettier-vscode
VSCode extension or prettier
via prettier-eslint
?
The prettier-vscode
extension recommends you...
Use prettier-eslint
instead of prettier
. Other settings will only be fallbacks in case they could not be inferred from ESLint rules.
Visual Studio Code became famous over the past 3+ years I believe. The clean UI, easy to use UX and the plethora of integrations made it a very easy decision for us. Our gripe with Sublime was probably only the UX side. VSCode has not failed us till now, and still is able to support our development env without any significant effort.
Goland being paid, as well as built only for Go seemed like a significant limitation to not consider it.
PhpStorm has all the integrations you need to build cool PHP Applications. This starts from it's super helpful integrated IntelliSense to the composer-support over much more integrated developer tools, such as git, ToDo-Lists and database connections. I also like the material design you can use with a plugin.
I decided to choose VSCode over Sublime text for my Systems Programming class in C. What I love about VSCode is its awesome ability to add extensions. Intellisense is a beautiful debugger, and Remote SSH allows me to login and make real-time changes in VSCode to files on my university server. This is an awesome alternative to going back and forth on pushing/pulling code and logging into servers in the terminal. Great choice for anyone interested in C programming!
Pros of PhpStorm
- Best ide for php286
- Easy to use233
- Functionality219
- Plugins165
- Code analysis161
- Integrated version control87
- Great php ide for mac76
- All-round php ide73
- Local history62
- Themes53
- Best PHP IDE18
- Database control11
- Easy to find anything and everything in your code10
- Best inspection variable9
- Best bebugging9
- UX7
- Great frameworks integration7
- PHPUnit integration7
- Getting Better7
- Command line integration7
- Performance6
- Coolest IDE6
- Composer integration6
- Best ide for advanced php and symfony5
- Real time code validation5
- Neat does the job and easy5
- Easy to use and github interaction5
- It has no match. it filled one of the biggest void4
- Cross platform4
- TypeScript support4
- Great refactoring support4
- Best ide for php4
- Code indexing4
- Fast and relevant auto-complete4
- Debugger for Javascript3
- Good3
- Very good3
- Integration with Vagrant and Docker3
- Debugging in the Just-In-Time Mode2
- Awesome debugging features2
- Perfect locahost / host sync2
Pros of Visual Studio Code
- Powerful multilanguage IDE328
- Fast293
- Front-end develop out of the box185
- Support TypeScript IntelliSense152
- Very basic but free137
- Git integration117
- Intellisense101
- Faster than Atom74
- Better ui, easy plugins, and nice git integration48
- Great Refactoring Tools41
- Good Plugins40
- Terminal38
- Superb markdown support36
- Open Source34
- Extensions28
- Awesome UI26
- Large & up-to-date extension community25
- Powerful and fast22
- Portable20
- Best code editor17
- Best editor16
- Easy to get started with15
- Crossplatform14
- Open, cross-platform, fast, monthly updates14
- Built on Electron14
- Good for begginers14
- All Languages Support13
- Lots of extensions13
- Extensions for everything12
- Easy to use and learn11
- Useful for begginer11
- Ui design is great11
- Faster edit for slow computer11
- Totally customizable11
- Extensible11
- Git out of the box10
- "fast, stable & easy to use"10
- It has terminal and there are lots of shortcuts in it9
- Great community9
- Great language support9
- Works With Almost EveryThing You Need8
- Fast Startup8
- Powerful Debugger8
- SSH support8
- Features rich7
- Can compile and run .py files7
- Python extension is fast7
- Great document formater7
- She is not Rachel6
- He is not Michael6
- Awesome multi cursor support6
- Easy azure5
- Extension Echosystem5
- SFTP Workspace5
- VSCode.pro Course makes it easy to learn5
- Language server client5
- Has better support and more extentions for debugging4
- Very proffesional4
- Excellent as git difftool and mergetool3
- Emmet preinstalled3
- Supports lots of operating systems3
- Virtualenv integration3
- 'batteries included'3
- Has more than enough languages for any developer3
- Better autocompletes than Atom2
- Light2
- CMake support with autocomplete2
- VS Code Server: Browser version of VS Code2
- More tools to integrate with vs2
- Fast and ruby is built right in2
- Big extension marketplace1
- Microsoft1
- Customizable1
Sign up to add or upvote prosMake informed product decisions
Cons of PhpStorm
- Uses a lot of memory14
- Does not open large files10
- Slow9
- Uses Java machine8
- No way to change syntax highlight for files without ext3
- No save prompt or asterisk on file change2
Cons of Visual Studio Code
- Slow startup43
- Resource hog at times26
- Poor refactoring20
- Poor UI Designer13
- Microsoft12
- Weak Ui design tools11
- Poor autocomplete10
- Poor in PHP7
- Huge cpu usage with few installed extension6
- Poor at Python5
- Super Slow5
- Poor intellisense. poor java4
- Microsoft sends telemetry data4
- Poor in Python3
- No Built in Browser Preview3
- Dilshad3
- No color Intergrator3
- No built in live Preview3
- Very basic for java development and buggy at times3
- Bad Plugin Architecture2
- It's MicroSoft1
- Electron1
- Terminal does not identify path vars sometimes1