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

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

#31

Post by avip » Sat, Apr 13, 2019, 7:53 AM UTC

larkeith wrote: post #29

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…

Anecdata: I fairly recently switched from vim to VSCode, and don't feel like there's any meaningful productivity difference. I've enjoyed using VSCode, but any difference in task overhead feels trivial - likely because I still need to spend the same time considering a given item, and whether I spend the time on overhead tasks or tabbing between files doesn't really change when I come up with the solution.

And possibly due to vim binding mode you don’t need to relearn keystrokes which is the main productivity killer.

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

#32

Post by black-tea » Sat, Apr 13, 2019, 7:53 AM UTC

not_kurt_godel wrote: post #14

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

If I can't do a "modern development task" with emacs or vim and a smattering of standard Unix tools, then I question the sanity of said task. At the end of the day we're editing text. Plain text has stood the test of time exactly because you can process it with tools that everyone knows and have been around for decades. If you find yourself needing special purpose, proprietary tools to handle your code base then you should really reconsider where you're going.

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

#33

Post by steve_taylor » Sat, Apr 13, 2019, 7:54 AM UTC

hansflying wrote: post #11

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

TypeScript is definitely a first-class citizen on VSCode. I’m considering TypeScript in my next React project and will definitely consider using VSCode instead of WebStorm. I’m a long time WebStorm user and ES6+React developer. TypeScript looks like it can solve a lot of my pain points and it supports JSX syntax (TSX).

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

#34

Post by black-tea » Sat, Apr 13, 2019, 7:57 AM UTC

useful wrote: post #30

onion2k wrote: post #16

Earlier quoted context omitted.

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

In my experience this is the same for people who use a low level text editor as an IDE. The code that comes out of developers that use IDEs is normalized in a way that makes it very easy to change. Sure, if your big enough you can spend all your time inventing linting rules and creating templates to generate scaffolding and tests.

In all my years of using emacs I have not once been called out on formatting. In my last job the bastion of PEP-8 was a vim user. If you're talking about actual low level text editors like nano or notepad.exe, then sure, but vim and emacs are proper tools.

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

#35

Post by __m » Sat, Apr 13, 2019, 7:58 AM UTC

I love the jetbrains toolbox. I do unity development with Rider, Android development with Android studio, web development with webstorm, python automation and ai learning with pycharm, java development with idea and I use it as diff/merge tool like the author (additionally you can toggle blame mode, which shows you the last person who edited the individual lines, at what time and with a color coding that highlights recent changes). Having a familiar user interface for all these IDEs and on top of that available on Mac, Linux and Windows won me over. I started with Rider for unity since I mostly use macOS and Monodevelop did not spark joy (vs for Mac didn’t exist yet and I prefer the user experience of the jetbrains IDEs).

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

#36

Post by virtualmic » Sat, Apr 13, 2019, 8:02 AM UTC

steve_taylor wrote: post #27

virtualmic wrote: post #25

Earlier quoted context omitted.

> Now you better use WebStorm for the frontend part, right ? All functionality of Webstorm is included in RubyMine and PyCharm (I use PyCharm daily). Ref: https://www.jetbrains.com/ruby/features/

It’s available as a plugin, with a different release schedule than WebStorm, so it’s always lagging behind WebStorm.

I just tried 3 latest features for Webstorm listed here: https://www.jetbrains.com/webstorm/whatsnew/

All are working on my latest version of PyCharm Pro.

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

#37

Post by loxs » Sat, Apr 13, 2019, 8:05 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…

I only use Vim, currently inside WebStorm. From my anecdotal experience, people who are willing to learn vim/emacs are also willing to learn a lot more about the whole programming experience, tools and theory. They usually are more productive, but I don't think it's vim that's making them productive, it's the other way around usually.

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

#38

Post by the_gipsy » Sat, Apr 13, 2019, 8:11 AM UTC

useful wrote: post #30

onion2k wrote: post #16

Earlier quoted context omitted.

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

In my experience this is the same for people who use a low level text editor as an IDE. The code that comes out of developers that use IDEs is normalized in a way that makes it very easy to change. Sure, if your big enough you can spend all your time inventing linting rules and creating templates to generate scaffolding and tests.

Just use a formatter already and get over linter bikeshedding.

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

#39

Post by stupidcar » Sat, Apr 13, 2019, 8:11 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.

Maybe the fact that they don't install such extensions indicates that they don't actually need them? I switched from IntelliJ to VSCode precisely because it was too slow and cluttered due to the sheer amount of extra features it provided, most of which I never used.

Even if all those extra features are useful, I'm still willing to compromise the core experience of editing and navigating code, as that's always what I'm going to be spending the majority of my time doing. I need that to be fast, easy and reliable, which is not what I have found to be the cast in IDEs, vs editors.

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

#40

Post by gloggy » Sat, Apr 13, 2019, 8:12 AM UTC

__m wrote: post #35

I love the jetbrains toolbox. I do unity development with Rider, Android development with Android studio, web development with webstorm, python automation and ai learning with pycharm, java development with idea and I use it as diff/merge tool like the author (additionally you can toggle blame mode, which shows you the last person who edited the individual lines, at what time and with a color coding that highlights r…

Yep, this describes me too. I work on multiple OSs, in multiple languages and I use everything from CLion to WebStorm. The interfaces are consistent on each OS, all the commands are the same, and while not the fastest IDEs in the world, my dev machines are good enough that I can run them comfortably. I think good IDEs make me more productive. I find the whole "you're only a good programmer if you program in ed" line to be really disingenuous.