Why I Switched from Visual Studio Code to JetBrains WebStorm • Hacker News Board

Re: Why I Switched from Visual Studio Code to JetBrains WebStorm

#11

Post by hansflying » Sat, Apr 13, 2019, 7:25 AM UTC

hansflying wrote: post #5

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

ABSOLUTELY EVERYTHING in this article is wrong. I just opened a typescript project in VSCode, created unused function and a class method and I immediately get warning that they are unused. So the author can't even check the facts before writing an article...

Re: Why I Switched from Visual Studio Code to JetBrains WebStorm

#12

Post by irth » Sat, Apr 13, 2019, 7:29 AM UTC

skrebbel wrote: post #2

Tldr: nothing fundamental but WebStorm has a few features that the author likes that VS Code doesn't have.

also, VS Code has those features, but is an extensible editor and not an IDE so you don't get them out of the box but that's by design

Re: Why I Switched from Visual Studio Code to JetBrains WebStorm

#13

Post by fxfan » Sat, Apr 13, 2019, 7:31 AM UTC

seddin wrote: post #8

There also this cool text editor, simple and fast, called Pluma and available on Ubuntu Mate which I really enjoyed using.

If we're going to list editors, I think I have a few in mind ;)

Re: Why I Switched from Visual Studio Code to JetBrains WebStorm

#14

Post by not_kurt_godel » Sat, Apr 13, 2019, 7:32 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…

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 simply outmoded for many modern development tasks in the same way that a hammer is outmoded by a nailgun. You might always need a hammer in your back pocket, but it can't compete with a nailgun for large-scale repetitive tasks.

Re: Why I Switched from Visual Studio Code to JetBrains WebStorm

#15

Post by v-yadli » Sat, Apr 13, 2019, 7:34 AM UTC

skrebbel wrote: post #2

Tldr: nothing fundamental but WebStorm has a few features that the author likes that VS Code doesn't have.

Agreed. Nothing fundamental but js sugars.

For me the IDE is more like a text editor bundled with extra goodies. E.g. multi-window (thus multi display), more elaborated software hierarchy (not just for code editing) vs. a main panel as editor and side panels as auxiliaries, automatic window management like Eclipse perspectives (or in VS, when you debug, it switches to the different window layout).

It’s not black and white unless you go with nano or notepad.exe. You can also roll your own ide with tmux, i3 etc.

btw have you guys ever tried to hack gvim window handles into Visual Studio? :-)

Re: Why I Switched from Visual Studio Code to JetBrains WebStorm

#16

Post by onion2k » Sat, Apr 13, 2019, 7:36 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…

Developers who don't write any tests are often the most productive.

If you look at them in isolation, sure. If you look at the whole team you'll see that the untested code drags everyone else's productivity down because all the other developers can't modify untested code without fully understanding everything it does. They have no tests to give them any confidence that they're not breaking stuff when they change it.

Developers who don't write tests are fine if they're working alone, but they're toxic to team productivity.

Re: Why I Switched from Visual Studio Code to JetBrains WebStorm

#17

Post by firmgently » Sat, Apr 13, 2019, 7:37 AM UTC

seddin wrote: post #8

There also this cool text editor, simple and fast, called Pluma and available on Ubuntu Mate which I really enjoyed using.

A fork of gedit 2 (for anyone interested in such trivia)

Re: Why I Switched from Visual Studio Code to JetBrains WebStorm

#18

Post by polotics » Sat, Apr 13, 2019, 7:38 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…

Word! I have seen many implementations turn into ridiculous over engineered monsters because the IDE enabled bad designs to clamber into an almost-functioning states.

Re: Why I Switched from Visual Studio Code to JetBrains WebStorm

#19

Post by sho » Sat, Apr 13, 2019, 7:39 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…

> do you rather see a positive or a negative correlation between the usage of high level tools and developer productivity?

Absolutely none whatsoever. If anything it's negative. I have never found "speed of editing" to be remotely correlated with good code or even productivity.

Re: Why I Switched from Visual Studio Code to JetBrains WebStorm

#20

Post by m0zg » Sat, Apr 13, 2019, 7:40 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…

It's a wonderful example of selection bias. Basically, vim/emacs is likely to select for people who are "good at computers" and reject everyone else. These people, in turn, are more likely than average to be excellent programmers. But I wouldn't necessarily draw the arrow of causation in this case. Not only does this not mean that IDE users are worse, it also doesn't mean that there are fewer great programmers among them in absolute terms (even though percentage wise, that's probably the case).

Full disclosure: I'm a vim user.