3 ms·

Try VSCode Remote, works wonders and simply.

nightski 4y ago
This is one area I'll never jump ship. I like developing the code I write on a local machine. If some day in the distant future we are required to use cloud servers to develop, I'm out. Done. Adios.
- wilsonnb3 4y ago
  What’s the issue with developing on cloud servers? Computing on a remote computer has a rich history going back to the terminals of the 60s and 70s and has never really gone out of style. VSCode is just the latest iteration.
- berkle4455 4y ago
  I prefer the remote setup because my dev machines are nearly identical to the production machines in every aspect. I can have a fresh new machine online in minutes, so can the rest of my team, or a new hire. All our code runs close to the data. My dev instance is significantly more powerful than my laptop. I switch between a desktop and laptop across a given day but my dev box doesn’t change. I’m not sold on the “in a browser” setup that this post is selling, I still run VSCode natively and also use it for my terminal shell.
- acdha 4y ago
  Why is your position so absolute? There are trade-offs and as engineers we typically would balance those — for example, local development avoids putting the network in the critical path while remote development allows perfect fidelity with your deployment environment, can be an important security win[1], and could make it easier to access resources which you don't have enough space or want to store locally. Neither of those is right or wrong globally: your particular situation will determine how much you weight each of them. 1. e.g. if you install the wrong Node module, it can still wreak havoc on your remote environment but it can't steal your local credentials, trojan your workstation, or attack your other projects — and by splitting your credentials from the remote environment's you can usually run with a far more restricted set of permissions.

This is one area I'll never jump ship. I like developing the code I write on a local machine. If some day in the distant future we are required to use cloud servers to develop, I'm out. Done. Adios.

wilsonnb3 4y ago
What’s the issue with developing on cloud servers? Computing on a remote computer has a rich history going back to the terminals of the 60s and 70s and has never really gone out of style. VSCode is just the latest iteration.
berkle4455 4y ago
I prefer the remote setup because my dev machines are nearly identical to the production machines in every aspect. I can have a fresh new machine online in minutes, so can the rest of my team, or a new hire. All our code runs close to the data. My dev instance is significantly more powerful than my laptop. I switch between a desktop and laptop across a given day but my dev box doesn’t change. I’m not sold on the “in a browser” setup that this post is selling, I still run VSCode natively and also use it for my terminal shell.
acdha 4y ago
Why is your position so absolute? There are trade-offs and as engineers we typically would balance those — for example, local development avoids putting the network in the critical path while remote development allows perfect fidelity with your deployment environment, can be an important security win[1], and could make it easier to access resources which you don't have enough space or want to store locally. Neither of those is right or wrong globally: your particular situation will determine how much you weight each of them. 1. e.g. if you install the wrong Node module, it can still wreak havoc on your remote environment but it can't steal your local credentials, trojan your workstation, or attack your other projects — and by splitting your credentials from the remote environment's you can usually run with a far more restricted set of permissions.