Why I Switched from Visual Studio Code to JetBrains WebStorm
1–10 of 163 posts
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#2Tldr: nothing fundamental but WebStorm has a few features that the author likes that VS Code doesn't have.
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#3I can understand that people may perceive VS Code and WebStorm as alternatives. Though, as rightly pointed out by the author, the former is an editor while the latter is an IDE. The whole post just says that in 10 different redundant ways.
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#4While VS Code presumably can do almost everything Webstorm (and other Jetbrains products) can, my experience in my fairly large software company is that most of the people that use VS Code don't actually bother to install the plugins to bring it up to feature parity. Out of the box functionality is underrated, even seemingly among devs who have the skills and knowledge to tinker.
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#5Very biased article and by the way, tslint will also warns you if you don't use promise:
https://palantir.github.io/tslint/rules/no-floating-promises...
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#6When you guys think about all the developers you know, do you rather see a positive or a negative correlation between the usage of high level tools and developer productivity?
In other words, is your experience that developers who use an IDE are more productive then developers who only use a text editor?
In my experience, the (very few) developers I know who only use VIM or Emacs are way more productive then those who use an IDE.
The reason seems to be that they tend to 'sit back and think' about the task at hand. And then come up with elegant solutions. While the developers who use a lot of tooling seem to hope that the tooling will kinda force them to do the right thing. But from what I witness, that never works out.
I see a similar thing happening with coders who do a lot of tests (test driven development), some tests and no tests. Developers who don't write any tests are often the most productive.
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#7When you guys think about all the developers you know, do you rather see a positive or a negative correlation between the usage of high level tools and developer productivity? In other words, is your experience that developers who use an IDE are more productive then developers who only use a text editor? In my experience, the (very few) developers I know who only use VIM or Emacs are way more productive then those wh…
I see no correlation
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#8There also this cool text editor, simple and fast, called Pluma and available on Ubuntu Mate which I really enjoyed using.
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#9While VS Code presumably can do almost everything Webstorm (and other Jetbrains products) can, my experience in my fairly large software company is that most of the people that use VS Code don't actually bother to install the plugins to bring it up to feature parity. Out of the box functionality is underrated, even seemingly among devs who have the skills and knowledge to tinker.
VSCode has a ton of extensions but very frequently there's no good information about which extensions you should actually use, and whether you need to configure them to get the best behavior.
For example, the other day I went to install a GraphQL extension for syntax highlighting and there was something like a half-dozen competing extensions, with no good way of figuring out why I should use one versus the other. I eventually ended up picking the one that looked the simplest, because all I really wanted was syntax highlighting and nothing else.
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#10I made a similar switch from VS Code to PHPStorm and had a remarkably similar experience. When I started using a proper IDE, I really began to get comfortable with the inner workings of what I was doing–debugging the frameworks I was using, jumping directly into methods and doing fairly broad refractors with their refactoring tools. I’ve found it’s made me a better developer by making that process simpler, while being very good at pushing me into optimizing my code, be it through PHPDoc or simply not being consistent in my implementation. I was surprised, but also, came to realize IDE platforms seem to be stigmatized by many developers in the web industry: they seem too heavy or not useful, but I’d argue it made me 10x more productive once I took the time to use one.