Live data from Hacker News

Why I Switched from Visual Studio Code to JetBrains WebStorm

mokkapps.de

161–163 of 163 posts

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

#161
post #110
post #65

Earlier quoted context omitted.

1. That depends on the developer 2. Dev's who use VIM/Emacs are probably already living in their computer so you can't really say if they are good because of the editor they use or the other way round 3. What do you mean by "productive"? Closing more tickets in a sprint? In the end not only individual efficiency is important but also the future of a project. With test you document stuff and ensure at least the tested…

If I got a job offer and they insisted on using Eclipse, I would most likely turn it down. Once you are used to Intellij, there's no going back. I even paid for a private license that I use for my own projects. I sometimes open VS Code for small for small non-project related files, but I am much more productive with an IDE. One thing that many get wrong in the VIM vs IDE comparisons are the benefits of keyboard short…

Don't know how I managed to trigger you here but:

- I would also not use eclipse and turn that down - Maybe you are more productive. I have seen people who will be more productive than you just using their customized VIM (I'm 100% sure about that) - You say "something" has an advantage over VIM (or EMACS) in the means of keyboard as input interface? Think again or at least try to let someone show you what VIM can do with just a keyboard ;-)

The difference is not only about the control with a keyboard. The true beauty of VIM etc. lies in the fact that you can use it without an X Server (so also over SSH). Then there is efficiency - VIM can do a lot more with a lot less resources. A PC that will already choke when you open up your project in a full-fledged "give me 2GB of RAM" IDE will seamlessly open up in VIM in seconds.

When you're traveling and want to preserve battery, VIM also comes in handy. Not everything I do needs the refactoring features of an IDE and I also don't have to use the test runner every time I do / change something (also there is CLI tools that are totally OK to use).

I think you are trying to compare something you don't really know.

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

#162
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…

why do you italicize random words?

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

#163

Earlier quoted context omitted.

What planet are you people living on? It's like you just whack the word "modern" on the front, stick your hands up and say "haha, you couldn't understand, grandad". Programmers have been doing these things since the beginning of time.

I programmed exclusively with text editors for a number of years. Of course you can do anything in a text editor that you can do in a modern IDE as long as you have patience. I would even go so far as to say that having the experience of using a text editor instead of an IDE is a valuable one; certain types of edits really can be done much more efficiently in vim than an IDE so it's an excellent tool to have at your…

That's cool, if you plan to work on the same technology forever. I think why vim/emacs users have over IDE users is that when you change technology or company or team, you can just change some things about your config and keep working. Try replacing a cool IDE for assembly with a cool IDE for PHP and then a cool IDE for Clojure.
Post reply on HN