News for hackers. Stuff that matters.
Re:Visual Studio Code is designed to fracture by sevensor on Monday September 30, 2024 @09:27AM (#41696851)
VSCode also, by design, obscures what’s really going on on the development environment, so that when I help a VSCode user who gets stuck, they often don’t know what computer they’re logged into, where their files actually are in the file system, which Python interpreter they’re using, what HTTPS_PROXY is set to, and so on. The ssh extension also spins up a server process for every client a user connects, and it seems a bit inconsistent about preserving state across disconnections. All in all, I spend a lot of time helping people fix problems they’ve made for themselves by using VSCode.
Re:Visual Studio Code is designed to fracture by spencerchubb on Monday September 30, 2024 @11:05AM (#41697997)
What kind of set up do you use? This does not resonate at all with my experience of vs code
Re:Visual Studio Code is designed to fracture by zdragnar on Monday September 30, 2024 @11:08AM (#41698036)
Presumably, this is talking about some remote devcontainer configuration. None of that really applies to using vscode locally, at least not any more than any other editor.
Re:Visual Studio Code is designed to fracture by shaklee3 on Tuesday October 01, 2024 @12:38AM (#41704647)
The bottom of the screen says exactly what you're connected to, so I'm not sure what they're referring to.