My point is that VS Code works really well for TypeScript and JavaScript, but I think IntelliJ's "infrastructure" makes it better for a whole range of languages. It's well known that rope isn't nearly as good as what P圜harm has built in. When I went to go rename a variable in Python in VS Code, it complained that I hadn't installed rope. The rebase flow is incredibly well done, especially when dealing with conflicts.ģ. The Git support in P圜harm is far more complete and advanced. I can have a whole "stack" of completely different search results in different tabs.Ģ. This is really important if the refactor takes me a few days, and I need to leave the results open the whole time. (Trying to do the same in VS Code is a fairly frustrating experience.) If I need to search for something else, I can save the results in a new tab without losing the original search. As I go through each entry, I don't lose my place in the find results, even if I have to edit the code for a few minutes. I can search for something in order to do a cross-project refactor. The Find window is much better in P圜harm. I think there are three things I miss the most in VS Code compared to P圜harm, WebStorm, IntelliJ, etc.:ġ. I think this video Moving from WebStorm to VSCode does a pretty good job tackling this question, but I remain unconvinced. more productive) than WebStorm, P圜harm, IntelliJ, etc." One question that I really wanted to tackle is "Are there ways in which VS Code is actually better (i.e. I can watch YouTube videos for hours studying how each works and why people like them. To be honest, I'm pretty compulsive obsessive about the whole thing. Don’t just take my word for its awesome capability.I spend a lot of time futzing with editors and IDEs. If you haven’t yet, give it a shot yourself. From that day forward I’ve continued to use and love developing javascript applications with Webstorm. There’s great power in having and utilizing tools that are a niche in their respective use cases, versus trying to use a tool that does it all. In the example above, if you wanted to develop a PHP application that also worked with Javascript, then you could use PHPStorm, as it includes everything Webstorm does, but also allows for advanced PHP development.
Why would you customize your text editor on a per-project basis, when instead you could use an IDE that has all of the advanced capabilities of developing applications in javascript without any configuration needed? That’s precisely my point here, VS Code is too generic, its the end all be all of text editors for any type of text file. Now, what happens when you start using VS Code to write PHP code? Now you have a plugin that lets you right-click and generate angular schematics….but in your PHP project? You might be saying, but ya you can turn on/off plugins at a workspace basis. Want this same functionality in VS Code? There’s a plugin for that, but you need to download, install, and reload your VS Code instance to get started using it in your projects. Want to generate an angular schematic or template file in Webstorm? Simply right-click on the project navigator and select generate schematic. But surely for my use case of purely javascript development, Webstorm was already set up out of the box with all the tools and capabilities you would need for advanced javascript development.
#Visual studio code vs webstorm download#
Sure you can download language-specific tools that might offer more advanced editing features. It’s too broad, it was built to be capable of editing just about any language of code known to computers. See, whereas VS Code is great and offers versatility in its plugins and ability to edit code in numerous languages, that’s also where the pitfalls of the text editor reside. Webstorm is exactly like that experience, over and over again each time you write code with it. I was shocked, it was an experience quite like when you’re walking through a store, and you see an item you’ve never seen before yet wonder how you’ve lived this long without it. So my curiosity peaked and I caved into trying out Webstorm for the advanced front end development in Angular. It wasn’t until I saw a colleague using Jetbrains Webstorm that I began to question whether I should be using a real IDE instead of a simple but extensible text editor. At the time I myself was a full-stack Visual Studio Code developer, utilizing its versatility for both front and back end development on my projects. Recently I began working on two different Angular projects for enterprise clients. TRIGGER WARNING: The content of this post may be found offensive to Visual Studio code enthusiasts and IDE nonconformists.
0 kommentar(er)
