I'd say I never had issues with vscode performance and actually its performance is a major factor why I use it.
I'd say I never had issues with vscode performance and actually its performance is a major factor why I use it.
The featuresets aren't the same.
What are you thinking of, in terms of differences? I use both quite a bit (some of VSCode's plugins are better) and have always viewed them as very close to one another, in terms of features.
Sublime doesn't have any (real) debugger even with plugins. Some attempt to tack on a debugger but they have to do so via popup menus or overloaded "magical" text buffers and it's atrocious. Why can't I click on the line I want to break on? Why can't I see the stack in a nice editable tree? Right, because sublime is a text editor and VS Code is an IDE.
Guess you've got a point, then, and I just don't use it that way.
C++ based editors like Kate blow both VSC and IJ out of the water. Runs so fast it feels janky, like the computer isn't doing anything.
And it offers vastly more features than VS Code.
Also, if you’re on a Mac — there’s an Apple Silicon build that is noticeably better.
This is not a good argument in a thread where the central claim is that VSC is a resource hog but other IDEs aren't
I just wrote the exact same thing in another comment.
That's what the problem is ... it's the old timers complaining that things aren't native, thus they are RAM hogs and are slow by default. Even if they are fast, they are "slow and bloated" just because it's the gut reaction when you have layers on layers of other stuff over native code.
And I'm an old timer but I am not complaining. I love VS Code and I think it's blazing fast for what I need it for, a large Angular enterprise application.
99.9% of people who complain about electron apps are not ardent defenders of third world computing. It just violates their sensibilities.
But I think it’s unfair to hold developer tools back to 10 year old specifications.
Because you need to sink hundreds of thousands of man-hours into making it work.
And fight against web tech most of the time you're doing that.
That being said I'm a huge fan of prioritizing longevity of computer parts versus constantly upgrading and generating e-waste.
I’ve since upgraded to a 2014 i7 and now VS Code feels fast.
I understand that everyone's situation is different, but I live in a poor country, making like $2k/month and still consider investments into my computer worthwhile, so I never tried to save money on it. This is american website, so most people here surely can afford fast computer for their work.
Exclude it (via https://code.visualstudio.com/docs/getstarted/settings) by using
"files.exclude": {
"**/.git": true,
"**/.svn": true,
"**/.hg": true,
"**/CVS": true,
"**/.DS_Store": true,
"**/Thumbs.db": true,
"**/node_modules" : true
}
I've not had any issues with speed ever since i started excluding directories that contain junk stuff that you know you will not ever need to see in a project's view.Often happens to me when I run projects that output large CSVs, and it's a very notable performance impact.
Anyway go to definition is a function of LSP server, AFAIU. I understand that it's bundled with vscode and feels like a single product, but still I'd separate vscode and LSP servers and judge them differently.
I think most VSCode features are disabled for node_modules directories by default.
At a guess, I'd say re-disabling that in your workspace file would resolve all of your performance issues. For even simple projects you'd be including hundreds of MB of text files, and thousands of subdirectories.
I also have 0 extensions installed :(
VS Code used to be my quick and dirty IDE when I didn't want to open something heavier, but it's gotten so much more painful than even a couple of years ago.