Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why I Switched from Visual Studio Code to JetBrains WebStorm

mokkapps.de

Post reply on HN
Print view View original

91–100 of 163 posts

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

#91

Post by scarface74 »

black-tea wrote: post #32
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…

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…

Real coders boot up their computers and type

  CALL -151
  !
And type 65C02 assembly.

Now get off my lawn.....

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

#92

Post by Illniyar »

I've used both. Webstorm is definitely slightly better in most things. Little things like better handling of closing tags or more useful context menu.

VSCode is massively easier to configure and has a lot more plugins. Most major plugins are covered by Webstorm or plugins, but it's the small things that give you an extra push.

Webstorm is more polished. VSCode is faster and more configurable. They are nearly equal rivals in my book, except one thing. Git integration in VSCode is horrendous. I work with git constantly while I code and the lack of proper support is a considerable productivity hurt.

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

#94

Post by kmlx »

realusername wrote: post #24

It's always the same debate, on my case all the features of Webstorm he's listing I will likely never use them whereas the lag issues & the clutter interface of Webstorm just make it a no-start as my main editor.

you mention speed. then you’ll be happy to find out that sublime text is much faster than vs code. on my mac even my intellij idea ultimate is faster than vs code. from my experience, vs code is the slowest editor you could possibly use, slower than a full blown ide, slower than a text editor. it’s just a slow piece of software.

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

#95

Post by kmlx »

dfischer wrote: post #57

I've used a lot over the years – always in VIM mode. As I have moved to GO recently I was using VS Code but found it bugging out at times. I switched over to Goland (I used to be heavy in WebStorm). It just works. I am happy.

intellij idea ultimate with the golang plugin feels like a swiss army knife for go :)

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

#96

Post by nnq »

jasonkester wrote: post #78
nnq wrote: post #54

Maybe people should realize that the problem is with the JS libraries ecosystem and how most are build in a way that "just jumping into a lib/framework to read its code and see what it does" can't seam to be feasible anymore . For example, in a React app if I'd want to jump from a `Route` import from react-router to it's readable code definition [1], NO IDE or editor around is capable a properly doing the jump, I eit…

That's a strong argument against using front-end frameworks and other things that require you to run a build on your front-end code. There are plenty of options to build fast, modern front ends without having to deal with any of that. And you're right about IDEs too. Given the choice between a full-blown VS.NET + ReSharper versus VSCode + $1,000 in my pocket, it's just no contest. No matter your bill rate, you still…

> a strong argument against [...] things that require you to run a build on your front-end code

Not really, if it's your own code that requires a build step, then you control that build step and the tools and all and you can have nice auto-reload and fully working source maps and integration with all your other tools...

Do whatever exotic build and transpilation makes you more productive when developing your application's code. But libraries and frameworks... it's not OK to have a large part of the ecosystem dependent on such build tools and at the same time have no usable tooling standardization to easily implement something as basic as "jump to implementation in original source".

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

#97

Post by TimMeade »

Illniyar wrote: post #85
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…

For the last 10 years I've worked with perhaps 200 developers, I haven't seen a single one who uses vim or emacs, whether they are 20 or 50 years old. Maybe it's the nature of the work - web development (frontend and backend). I've known a few who use sublime text, and there was no correlation with either being a good developer or being productive (though I haven't met a bad developer using sublime yet, mediocre ones…

In general I agree with you. But! I do know a couple programmers, one who is in his 20's and one older who use vim for everything. Honestly i would say the they are more productive doing it. Watching them work is astounding. Unfortunately the learning curve to that level is Everest like.

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

#98

Post by realusername »

kmlx wrote: post #94
realusername wrote: post #24

It's always the same debate, on my case all the features of Webstorm he's listing I will likely never use them whereas the lag issues & the clutter interface of Webstorm just make it a no-start as my main editor.

you mention speed. then you’ll be happy to find out that sublime text is much faster than vs code. on my mac even my intellij idea ultimate is faster than vs code. from my experience, vs code is the slowest editor you could possibly use, slower than a full blown ide, slower than a text editor. it’s just a slow piece of software.

Yes indeed I know, I hesitate to go back to Sublime because of that, VSCode is still pretty slow and the RAM usage isn't great.

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

#99

Post by johnny22 »

sho wrote: post #19
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.

most people here aren't talking about speed of editing, but rather speed of code navigation.

That way it's easier to figure out what's going on in larger codebases, or one even just one you're not familiar with.

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

#100

Post by namelosw »

nnq wrote: post #54

Maybe people should realize that the problem is with the JS libraries ecosystem and how most are build in a way that "just jumping into a lib/framework to read its code and see what it does" can't seam to be feasible anymore . For example, in a React app if I'd want to jump from a `Route` import from react-router to it's readable code definition [1], NO IDE or editor around is capable a properly doing the jump, I eit…

I'm not sure if this is positive or negative. But somehow more or less encouraged JavaScript community move towards:

1. Minimal interfaces 2. Better documentation

Say like React although the codebase is more or less difficult to read. But the most useful surface-level APIs are quite minimal and intuitive. There are more minimal libraries follow this pattern.

And for the documentation -- probably because of the minimal interfaces, successful JavaScript libraries tend to have better documentation over most of the languages. A lot of documentation with both quick start guide and great higher level design or motivation explanation, instead of just generating doc from comments.

I think that's why this community is moving fast forward because people trying to be communicative, and constantly trying to simplify and introducing new ideas. It's very hard for people just read the code to understand some brand new concepts without a good understanding of the high-level constructs.

Post reply on HN