Switching from Vim to Intellij
41–50 of 263 posts
Re: Switching from Vim to Intellij
#42I was thinking there might be something interesting here. Then I got to this line: "I started a new job working on a large typescript React project. Vim couldn’t handle opening a TSX file larger than 50 lines without crashing." And I was like LOL WUT? The author's case in this regard woudl be stronger if they helped us understand what was actually going wrong. Bad plugins? Conflicting macros? I'm pretty sure that sim…
Re: Switching from Vim to Intellij
#43I switched from vim to Webstorm, which is based on IntelliJ. I agree with most of this article. IdeaVim is a pretty good vim emulator (although not perfect, but none of them are). There's something to be said by having sane defaults that do exactly what you want. Probably my biggest issue with vim is you can easily find yourself in no man's land because your setup inevitably becomes uniquely your own. For example I u…
Re: Switching from Vim to Intellij
#44I was thinking there might be something interesting here. Then I got to this line: "I started a new job working on a large typescript React project. Vim couldn’t handle opening a TSX file larger than 50 lines without crashing." And I was like LOL WUT? The author's case in this regard woudl be stronger if they helped us understand what was actually going wrong. Bad plugins? Conflicting macros? I'm pretty sure that sim…
Well, the thing about Vim and Emacs is that the users are expected to figure out configuration problems like these. That's not a point in favor of Vim and Emacs.
Sure, there are a bunch of choices for you to use... but now you have another problem -- there are a bunch of choices.
Re: Switching from Vim to Intellij
#45Re: Switching from Vim to Intellij
#46I recently switched from IntelliJ IDEA Ultimate to VS Code for Go development (side project), because I don't want to pay for it, when I'm no longer a student. With Golang VS Code works great after getting used to it. The Go plugin is not available for the community edition. For Java and Android development I always used (and still use) IDEA because it's feels much better than Eclipse.
I was a happy VS Code user (after being a happy VIM user for a while) until I switched jobs from Go codebase to Ruby and then I quickly jumped back to IntelliJ. So far (for me) this is the only editor that correctly figures out most of the definitions and locations of methods/classes/etc.
Intellij IDEA is my go-to tool when working with the dynamic beast Ruby.
Well, actually Intellij IDEA is my overall go-to tool, also now when I work with Go again mostly.
Re: Switching from Vim to Intellij
#47Just a warning, jetbrains has a huge marketing team. I pretty much can't read anything on the internet about jetbrains without thinking about it being questionable.
https://news.ycombinator.com/newsguidelines.html
Please don't post insinuations about astroturfing, shilling, brigading, foreign agents and the like.
Re: Switching from Vim to Intellij
#48I have been using Jetbrains IDEs for a long time now, started with PyCharm and made my way through Webstorm to CLion for uni. It's great, but the RAM cost has been too high for me. I've been slightly switching the opposite way, using vim more and more for smaller stuff and opening the IDE only for larger projects or work stretches. I definitely love the value of vim as a nifty tool, my workflow is noticeably faster.…
Re: Switching from Vim to Intellij
#49I wrote a similar comparison here: https://henrikwarne.com/2012/06/17/programmer-productivity-e... I've got to say that I am still solidly in the IntelliJ IDEA camp.
I fear someday having to do job interviews and having to get up on a whiteboard or use some half-assed shared-coding IDE, because my fingers and eyes, they really want JetBrains products there... I don't type out for-loops, I use generators, etc. etc. it's all so much faster...
Re: Switching from Vim to Intellij
#50Earlier quoted context omitted.
Well, the thing about Vim and Emacs is that the users are expected to figure out configuration problems like these. That's not a point in favor of Vim and Emacs.
Right -- the argument here isn't against Vim per-se, but the entire ecosystem of plugins and configuration that's needed to work and be productive. Sure, there are a bunch of choices for you to use... but now you have another problem -- there are a bunch of choices.