[mattlondon]

For what it is worth, I have never experienced this issue on modern hardware, and I regularly work with a very large monorepo.

Perhaps it is my habit of opening a subset of the repo into the workspace rather than the whole thing (e.g. only the bottom 4 or 5 directory levels so there is at most only a few hundred files in the workspace - builds etc just run from the usual command line so not having the entire repo in the workspace is not an issue for my workflow) but I have been nothing apart from really happy with the performance and have never been found wanting more, apart from loading time but that only happens once or twice a week so I can live with that.

[lioeters]

I use VS Code daily, and most of the time I have a single workspace open with everything in it, probably more than a thousand repos.

Checking now, the workspace contains ~3.7 million files. I have had no perceivable performance issues with the editor, it works like a champ. Granted I have a beefy machine, but VS Code has been a pleasure from my first impression. For my needs, it's a great development environment.

Recently I onboarded someone to set up remote SSH editing. It did require a few technical steps, but after that they were joyous to see how well it works - a "game changer" in their words, saving them a lot of time and effort.

[mattlondon]

Absolutely agree with the remote SSH being a game changer - it is seamless and works amazingly well.

Since the start of lockdown I've been using it to remote edit from my laptop into my dekstop still at the office and it has been a flawless experience.

Compared to laggy and visually-aliased remote desktop experience (I did this for a while a few years ago and I ended up feeling see-sick after a while), or the faff of remotely mounting disks, it has been utterly seamless.