Live data from Hacker News

Why I Switched from Visual Studio Code to JetBrains WebStorm

mokkapps.de

121–130 of 163 posts

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

#121

Earlier quoted context omitted.

Well because it is. With a large codebase, things like navigating through a solution, automated code refactorings, intellisense, etc. can be done with IDEs. Do you all so litter your code with print statements to debug?

Are you just playing ignorant for fun? You must know that there are people out there hacking on the most advanced software projects we have such as the linux kernel or C compilers etc. and they don't all use IDEs.

And what percentage of developers is that? That’s about like the same bubble thinking of every developer works on the west coast making $300K a year that you see on HN.

And some people also still write in assembly. I also thought that any high level language was useless. Then I thought anything more high level than C was for beginners.

But I grew up and start being more concerned with making money and implementing solutions than having geek cred...

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

#122

Earlier quoted context omitted.

How many automatic guaranteed safe refactors can I do with VIM? Of course I’m referring to statically typed languages. Something as simple as renaming a method and it is automatically renamed in your entire code base is a life saver. https://www.jetbrains.com/resharper/features/code_refactorin... I see a similar thing happening with coders who do a lot of tests (test driven development), some tests and no tests. Deve…

The Language Server Protocol [1] makes such refactors possible in Vim (and other editors). [1] https://microsoft.github.io/language-server-protocol/

So it’s possible, have any implementations where you can use VIM and do massive project wide refactors?

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

#123

Earlier quoted context omitted.

Are you just playing ignorant for fun? You must know that there are people out there hacking on the most advanced software projects we have such as the linux kernel or C compilers etc. and they don't all use IDEs.

And what percentage of developers is that? That’s about like the same bubble thinking of every developer works on the west coast making $300K a year that you see on HN. And some people also still write in assembly. I also thought that any high level language was useless. Then I thought anything more high level than C was for beginners. But I grew up and start being more concerned with making money and implementing so…

Good for you, man. I hope the money continues to bring you happiness.

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

#124
post #16

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

well, if you’re referring to the developer gagging hairballs of tests building tons of state for happy paths and individual edge cases then yes, perhaps. Concise property and generator based tests on the other hand are shockingly simple and useful to write

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

#125

Earlier quoted context omitted.

The Language Server Protocol [1] makes such refactors possible in Vim (and other editors). [1] https://microsoft.github.io/language-server-protocol/

So it’s possible, have any implementations where you can use VIM and do massive project wide refactors?

I haven't personally done any massive ones, but vim-lsp and tsserver have worked fine on a tens-of-thousands of lines large project.

It's the same gubbins that VS Code uses for all of its cleverness.

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

#126
post #30

Earlier quoted context omitted.

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.

I honestly don't understand how people are still bickering over style guides in modern programming. Autoformatters exist in every major language. Git hooks exist. Company style guides exist. Pick one, and then it's never an issue what editor people are using, it's bizarre that this bikeshed still exists.

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

#127

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

Of course it's biased, it's a "Why I XXX" article ;) - what did you expect?

Regarding the floating promises warning, this setting is off by default, so you have to know it's there to activate it. Additionally, VSCode's integration with tslint output is mystifyingly poor, and I assume it is this that the author is referring to. There's clickable output in the build output window, but no popups in the text editor.

I like to run the compiler and linter manually, so I can see all the issues in one list. Popups in the editor are handy but clickable output in the build output window is good enough.

Some people prefer to work with file watchers, so the error/linter output is not as accessible. They probably need to be able to see everything in the text editor. But even if you work the way I do, you may well wonder why you don't get tslint editor popups. I've certainly wondered it myself. I can do without, but they're certainly handy.

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

#128
post #106

Earlier quoted context omitted.

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

..that's like saying: "We're proud to have the best the anti-suicide-by-jumping building meshes system and workplace psychiatric counseling in the world! The world record rate of suicide amongst our employees prompted us to implement and perfect this measures to such a high degree, that now we're considering to pivot our entire business model towards selling 'employee suicide prevention consulting services', since no…

This is a rather tasteless joke.

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

#129
post #49

Earlier quoted context omitted.

Would you mind being a bit more specific than using vague language and analogy? What are all these modern development tasks?

* Find usages * Go to definition * Extract method * Introduce parameter * Inline variable * Rename method * Rename variable In a Jetbrains tool these are automatic / atomic operations.

All of these can be done in emacs/vim as well for most of languages. None of the above is modern by any standard.

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

#130
Having used both, I can say without hesitation that they're both fantastic works of software. I personally use vscode as my daily driver now because it has all of the features I care about from WebStorm but it's free.

(I also have a license for Sublime Text and used that for years. I still prefer vscode now. But a developer's IDE/editor is a deeply personal choice and everyone should use whatever software they're most comfortable and productive with.)

Post reply on HN