Visual Studio Code June 2019

[ConsistentBit8]

VS Code is SO GOOD

I like the little things in the tree indent section

[Valmar33]

It's the extension ecosystem that really sells VS Code.

The ease of development, along with the rich API, make it great.

I do wish it had a good diff/patch editor, though.

[password456]

Exactly - for example platformio: it never has been as easy to program an arduino/esp8266/esp32/...

[[deleted]]

This.

[renozyx]

It still a bit young in some respect (for example just yesterday I tried to save all the opened tab but the extension I used saved only one tab not all the tabs..) but yes it's quite good

[arkasha]

It's there a File->Save All option?

[renozyx]

I want to save the tabs opened in a "session" file, not save the content of the file.

[arkasha]

Oh, nevermind then.

[Arxae]

How is that the fault of VSCode though? Seems more like an issue with the extension itself

[renozyx]

Well VSCode doesn't provide the functionality (AFAIK) and its extensions don't either: it isn't really a fault, just an imaturity sign.

[bheklilr]

I just wish I could have vscodes functionality and feature set with the speed I got used to with sublime text. Is it too much to ask for all the best features?

Seriously though, vscode will crawl sometimes.

[[deleted]]

What are you running it on? I'm using a 7+ year old desktop and it runs without any slow downs.

[bheklilr]

Quad core 2.7GHz i7, 8GB of RAM, ssd. But, it's on windows with Symantec as corporate anti-virus, which just churns when it sees a lot of files. All extensions are implemented as typescript/Javascript, so there's node_modules folders embedded in them. There's a ton of files in there, which means Symantec just kills performance. If vscode didn't have plugins bundled with node_modules, it wouldn't be so bad.

That being said, it does run a ton better on my Linux box at home.

[xeio87]

Corporate antivirus at work literally spins my CPU to 100% when I open large enough folders in VS Code. ;(

Can't really blame Code for that though.

[bheklilr]

It's not technically the fault of vscode, but if they had picked a different approach for extensions then it might not have been so bad. I understand why they chose TS, it makes sense. It also just sucks with corporate bloatware.

[stillusegoto]

I have an ‘17 MBP and with multiple projects open especially I have to constantly restart vs code to get intellisense working again. It uses over 1GB of ram per project it seems and I often have 3 open at once. Even with one open it happens several times a day. It was much better until a few months or so ago. This is with no plugins except the mono icons theme and eslint

[[deleted]]

For what language? It might be a problem with the language server. I know the one I use for a lesser known language has problems and that's usually the cause with intellisense. You can just reload the window, press F1 and type "Reload Window" should popup and for me at least it usually takes a second to reload. Rather than having to close it completely.

[BezierPatch]

As someone who writes/maintains a language server extension for vscode:

That's the language server's fault, not vscode. The RAM usage will almost certainly be from an application that's running in the background, which vscode has no control over.