Why I Switched from Visual Studio Code to JetBrains WebStorm

Post by carlmr » Sat, Apr 13, 2019, 10:07 AM UTC

matharmin wrote: post #45

ashnehete wrote: post #3

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

What's your definition for an IDE that does not include VS Code? Just because VS Code feels lightweight, doesn't mean there is any fundamental limitation preventing it from supporting all the features mentioned in the post. In fact, as the author and others mentioned, you can achieve many of the same features with plugins in VS Code. Yes, WebStorm is better in the points mentioned by the author, and the JetBrains IDE…

Post by steeve » Sat, Apr 13, 2019, 10:17 AM UTC

Niksko wrote: post #4

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

Post by Illniyar » Sat, Apr 13, 2019, 10:20 AM UTC

founderling wrote: post #6

When 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…

Post by Illniyar » Sat, Apr 13, 2019, 10:22 AM UTC

ashnehete wrote: post #3

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

Post by scarface74 » Sat, Apr 13, 2019, 10:24 AM UTC

jjeaff wrote: post #44

not_kurt_godel wrote: post #14

Earlier quoted context omitted.

Out of the hundreds of devs I've worked with, I can think of exactly two who use(d) vim to edit code with any regularity. Both are fairly proficient above-average devs overall, but I'm pretty sure they also use IDEs heavily and only use vim for quick things. Beyond a certain level of codebase complexity, there is simply no way to do the job with a text editor, even with fancy macros. Vim is an elegant tool, but is si…

Interesting. From reading HN, you would think every coder worth anything is hacking away with emacs or vim on black and green terminal screens. But I suppose people that use emacs and vim are like vegans. Those that do, are definitely going to tell you about it.