3 ms·
I use cloud IDEs, more for the cloud workspace than for the IDE, I guess. Maybe I could have the same thing with VMs or containers (disclaimer: I've never even
by MrPatan 11y ago
I use cloud IDEs, more for the cloud workspace than for the IDE, I guess.
Maybe I could have the same thing with VMs or containers (disclaimer: I've never even set up docker or vagrant), but I still would like to have that in the cloud where somebody else takes care of patching stuff, backing up data, etc, and I can share it with a URL if I want to, instead of with a multi-GB file.
I'm too lazy to care about my infrastructure anymore, and I'm happy I can pay other people to do it for me.
- ivan_burazin 11y agoLove it! This is why we build what we do :)
- lewisl9029 11y agoSpecifying a Vagrantfile and Dockerfile is usually the first thing I do for any non-trivial project these days. I find there's tremendous value in having a fully reproducible dev environment on all of the different OSes and machines I work on, and I suspect the benefits would be even more pronounced in a team environment. The cloud IDE takes this concept even further by only ever having a single source of truth for the dev environment, but this comes at the cost of offline access and choice of editors, which is a compromise I'm not willing to make yet.