Re:A Picture of Java in 2020
by SomaticPirate on Tuesday September 22, 2020 @01:34PM
(#24557446)
But the trade off here is indexing. Visual Studio code provides no indexing functionality by default (some LSPs provide basic caching but not much). This is the killer feature for me. I can load up Kubernetes in Goland, cook an egg on my laptop while it indexes (about a minute) and have lightning fast goto def and find reference for the rest of the day. VS Code will load quickly but every single goto def will take ages.
Re:A Picture of Java in 2020
by neurotrace on Wednesday September 23, 2020 @10:56AM
(#24567844)
> VS Code will load quickly but every single goto def will take ages.
I wouldn't blame that on VS Code but on the relevant extension. Go to Definition is instantaneous for me when I'm working in TypeScript
That's why I mentioned longer sessions. I tend to jump quickly between many new projects, in which case the indexing is annoying.
When you start a longer session, the overhead is very much worth it, I agree fully.
For longer sessions that's not a problem, but when you're on battery or quickly hopping into the project to look something up it makes a lot of difference. Also, opening up a foreign project is two clicks and one second, compared to project creation and then loading+indexing when using IntelliJ.
I love the IntelliJ line of IDEs. But VSCode outcompetes it in simplicity by far. Especially when we're talking about something like a simple Node project, where compilation+execution is far simpler than something with a full build pipeline with artefacts.