3 ms·

I almost use always vscode via it's ssh remote development feature. In my experience this thing is flawless and indistinguishable from local development. It's h

I almost use always vscode via it's ssh remote development feature. In my experience this thing is flawless and indistinguishable from local development. It's hardly believable how good they've made it. The idea vs. code is something i don't buy. Each has its use cases. Idea has great tools for android development, it's just tightly geared towards that, which is especially good for someone that is not a main android developer and need to those extra wheels. While vscode is my go to editor for everything else, including java ee.

arduinomancer 6y ago
Just curious but what is the use case for needing to have your source code on a remote server while you’re editing it?
- sto_hristo 6y ago
  That depends on the person using it, there isn't a fix list provided by the devs of vscode. For me it's some of the following: It can be a remote workstation you'd otherwise have to RDP into it. Sometimes RDP is annoying due to network conditions. Via vscode this works great, even at the worse case scenarios of connection drops. Mind you, it's not just source code editing, but debugging, local server management during iterative development. Experience is just like if it was local. Can have multiple projects (directories) opened at the time via a single vscode instance, or multiple instances of vscode running different projects (or modules of the same project) all connected to the same ssh target. It can be a local container filled with tons of prerequisites/deps, like application server runtimes, support files, all that stuff that i don't necessary want (or need) to pollute my host just because of that one thing right now i will be working on. I just destroy that container when i don't need it, or do anything with it without fear of consequences on the main host. Another case would be a container that perfectly mimics final production environment with all its config.
- fancyfish 6y ago
  Enterprise policy is one use case, where devs must use locked down windows workstations to dev on remote Linux hosts.

arduinomancer 6y ago

Just curious but what is the use case for needing to have your source code on a remote server while you’re editing it?

sto_hristo 6y ago
That depends on the person using it, there isn't a fix list provided by the devs of vscode. For me it's some of the following: It can be a remote workstation you'd otherwise have to RDP into it. Sometimes RDP is annoying due to network conditions. Via vscode this works great, even at the worse case scenarios of connection drops. Mind you, it's not just source code editing, but debugging, local server management during iterative development. Experience is just like if it was local. Can have multiple projects (directories) opened at the time via a single vscode instance, or multiple instances of vscode running different projects (or modules of the same project) all connected to the same ssh target. It can be a local container filled with tons of prerequisites/deps, like application server runtimes, support files, all that stuff that i don't necessary want (or need) to pollute my host just because of that one thing right now i will be working on. I just destroy that container when i don't need it, or do anything with it without fear of consequences on the main host. Another case would be a container that perfectly mimics final production environment with all its config.
fancyfish 6y ago
Enterprise policy is one use case, where devs must use locked down windows workstations to dev on remote Linux hosts.