3 ms·
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 se
by lopkeny12ko 3y ago
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 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).
- ivan_burazin 3y agoI have been building them my entire career and there should be no sync involved at all tbh. Everything is remote but you work in a local IDE and everything feels local
- mikeravkine 3y agoWith VS Code remote SSH, there is no "local" you are always on the server so there is also no syncing. They do some tricks to make this seamless and perform and feel as if everything was local.
- JohnFen 3y agoBut what do you do when you need to work without internet access, or with limited internet access?
- stevage 3y agoI briefly worked for Facebook. Their cloud dev environment blew my mind. Way better than trying to get that stack running on your machine.