4 ms·
Reading these comments, I feel like a heathen for this opinion, but here goes: I find I prefer Jetbrains IDEs to VSC, massively so. VSC is nice, and I tend to
by notamy 6y ago
Reading these comments, I feel like a heathen for this opinion, but here goes:
I find I prefer Jetbrains IDEs to VSC, massively so. VSC is nice, and I tend to use it as my daily driver, but I experience a host of issues with it that I've never been able to solve. In no particular order:
- Autocomplete/Intellisense/whatever-you-call-it just stops working, constantly. This has persisted across many languages: Rust, C, PHP, Elixir, Java, Javascript, Typescript, Scala, ... despite having the relevant extensions installed. It's incredibly frustrating. Reinstalling VSC, disabling all extensions, etc etc etc has made no change. I've found absolutely nothing that indicates what could possibly be the issue, and fixes I've found online haven't helped. I admit I have a habit of leaving VSC open for days on end, but that shouldn't impact anything -- Jetbrains IDEs work reliably for me under the same circumstances.
- Performance-wise, I find it slower. Sure, a window opens up fast, but that's about it. I have a few extensions for symbol/token colourisation (think rainbow parens, rainbow do/end in Elixir, ...), since it makes it easier for me to read the code, and I find that these have a giant impact on its performance. Things like smooth scrolling -- which I like -- tend to lag out a lot for me when there's a lot of text in the terminal, even when not coloured or anything. It's not like I'm running this on a low-end machine, either; specs are R7 1800X / GTX 1080 / 64GB, so to me it's absolutely inexcusable that it's this slow.
- Unreadable themes are an issue I've run into, tho I understand this isn't a VSC-specific issue. With VSC specifically, I can't find a theme that actually has comments that feel readable to me -- I strongly dislike green comments, and all the themes I've looked at make comments a really low-contrast colour that blends into the editor background. I have neither the time nor the patience to make my own theme (or customise someone else's), so using VSC just becomes frustrating at times because someone thought low-contrast comments were a good idea.
- Stuff like jump-to-definition, refactorings, ... are consistently either not-very-functional, or just don't work. Jump-to-definition specifically loves to just give "No definition found" even when the relevant symbol is in the same file.
Maybe I'm doing something wrong, I don't know. But I've used VSC for the last ~2 years and it's been consistently far less usable for me than a Jetbrains IDE. VSC feels like I'm using a plain text editor with syntax highlighting, an integrated file browser, and an integrated terminal.
- dkarl 6y agoSimilar experience here. I find IntelliJ autocomplete, syntax highlighting, compilation etc. to be laggy occasionally as well, but I can usually see why and wait for it to finish reindexing or whatever. With VSCode, I don't bother waiting because 1) I often can't visually see why it's not working or when it's ready to work again, and 2) sometimes it's never going to be ready, because something stopped working. I am still actively using both, because I prefer VSCode for Javascript and expect it to eventually catch up for Java and Scala, but I often switch from VSCode to IntelliJ in the middle of a session, never vice-versa.
- phist_mcgee 6y agoI literally switched from VSCode to Webstorm purely because JS/TS 'no definition found' errors kept coming up. If I ctrl click a function, I really really want to go to the defintion. I know there is a definition because my code compiles. How can my IDE not know where that definition is? I count that as one of the core features of an IDE, and VSCode doesn't consistently hit that mark.