3 ms·
Jetbrains Gateway is very poor compared to VS Code's remote development plugin. I can't use it without wanting to pull my hair out. It's laggy, installing plugi
by ctvo 3y ago
Jetbrains Gateway is very poor compared to VS Code's remote development plugin. I can't use it without wanting to pull my hair out. It's laggy, installing plugins is painful (per project?!), etc..
Has it improved in the last year?
- quantified 3y agoIt's still painful. Maybe it's improved, but my day-in/day-out with it is horrible.
- Rapzid 3y agoSounds close to my experience with Rider the other week. Had a fantastic experience migrating my dev environment to WSL+VSCode from VirtualBox. Went to try Rider pointed at the WSL instance and.. Basically gave up on it lol.
- tgpc 3y agonot really i so desperately want it to work, but it messes up often enough that it's not worth it yet fwiw, using local intellij with nfs mounted source is a better experience
- jlmorton 3y agoYes, it's improved remarkably over the past year. I had the same experience as you, but it's at the point where it's pretty usable. There are still irritations. But I am comfortable using it day-to-day. It's absolutely critical that your remote gateway be nearby. I'm about 10ms away from mine, and though there is sometimes perceptible lag, it's not bad at all.