61–70 of 246 posts
I rent server rack space at a datacenter where I have a beefy workstation to do all my work. I use VS Code Remote and SSH port forwarding. The workstation has fast 2TB NVMe and 64gb of ram, 16 cores and a RTX GPU. It's actually cheaper and faster than our production cloud server. I tried Github Codespaces and thought it was cool but wasn't nearly as fast as my remote workstation.
I am sorta doing this, locally. I have a handful of servers in my basement that I use vscode+remote-ssh to work with. The benefit is that I can jump from my desktop to my laptop without any fuss. I can leave long-running scripts online for like an experimental batch job and attach to that from any machine, even when I am not home thanks to wireguard/tailscale. It is very nice knowing my dev env is always there in the…
No because I want the entire development environment to run locally (and anywhere else) without WAN connectivity.
> I have never in my career seen a good implementation of cloud development. At every company I've ever worked for, "cloud development" is nothing but a Linux VM that gets provisioned for you in AWS, a file watcher that syncs your local files to the VM, and some extra CLI tools to run builds and tests on the VM. And every time I've used this, the overhead of verifying the syncing is up to date, the environment is consistent between my laptop and VM is the same, all this other mess...every time I end up just abandoning "cloud dev" and doing things on my laptop. God forbid you change a file in your cloud VM and forget to sync in the reverse direction. Not only is local development more reliable, but it's also faster (no remote network hop in the critical path of building things).
Not quite the same since it's not really containerized, but I set up the project once and then I'm good to go from there
It's nice cause I detest Apple/MacOS and this lets me avoid it completely since I'm just interacting with a Debian machine
For Jetbrains users: Step 1. Create an Oracle Cloud account Step 2. Create an Ampere 6 core, 32gb memory instance for like $5/mo Step 3. Use Jetbrains Gateway to run your IDE as a thin client, executing on that host. You get a pretty darn beefy ARM64 VM instance from OCI for extremely cheap. You can get these in a region near you, with low latency. And Jetbrains Gateway works pretty great. On the plus side, this is a…
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?
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
I'll repost here a comment I made on another HN post about cloud dev environments and why I will never be convinced to use them. > I have never in my career seen a good implementation of cloud development. At every company I've ever worked for, "cloud development" is nothing but a Linux VM that gets provisioned for you in AWS, a file watcher that syncs your local files to the VM, and some extra CLI tools to run build…
We generally see a ton of velocity increase in dev from teams that adopt the Cloud IDE alongside the rest, as exhibited by lots of comments. Internally, we dogfood them 100% and the team would never go back to the old "local-first" ways. So we are using them and love them. The key qualities we love are ephemerality, parallelism, and accessibility. But in general there is a lot of resistance for various reasons, as seen in many comments here.
We wrote up some of our POV in our docs here: https://docs.withcoherence.com/docs/explanations/remote-deve...
[I'm a cofounder of Coherence]