While I don't use VSCode myself, many students and faculty at my school did, and the VSCode SSH extension seems to have some performance issues. It works by copying a server binary onto the remote computer; however, that process is quite heavy in terms of resource usage on the remote, using hundreds of MB of RAM in usual cases (which adds up when you have hundreds of students doing their assignments on one server), and 10s of GB at the extreme. It's also particularly bad about cleaning up after itself: oftentimes, when users disconnect their session, the VSCode instance continues running on the remote server forever until it's manually killed (and every time the user starts a new session, it starts a new process instead of reusing an old one).

Our school servers have a 200-process-per-user quota to prevent accidental fork bombs; students frequently hit this limit and become unable to log into a shell, because their entire quota is taken up by VSCode SSH processes that have accumulated over months.

The combination of these two effects have caused serious problems over the past couple years as VSCode adoption has rapidly increased among the student base, to the point that some professors have banned VSCode from their classes, due to the SSH extension making the class servers completely unusable for everyone during the big rush a few hours before an assignment is due.

Yes.

1. You're already in your terminal.

2. You get to use Vim (if that's your thing).

3. You don't have to use VSCode (if it's not your thing).

No sync issues, no freezes. Your code editor/tools/coding happens in a single computer.

VScode remote extensions are really good though, the best of any GUI editor. But that BLOB it installs on remotes can take a good chunk of scarce VM RAM.