[flagged]
Codespaces but open-source, client-only, and unopinionated
81–90 of 157 posts
Re: Codespaces but open-source, client-only, and unopinionated
#82Earlier quoted context omitted.
I've been using devenv for new projects. I like it so far. Some might find nix (which it requires) to be overkill, but I think that's underestimating how devilish of a problem it's solving.
It seems more approachable than going down the NixOS rabbit hole. I haven't had a need to reach for it yet, but I will probably try it out at some point.
I'd be cautious about thinking that you'll be able to use it for complex projects without eventually needing to enter the NixOS rabbit hole. This hasn't happened to me yet on a project that I'm using devnenv with, but while using nix flakes I've found weirdness in nipkgs that I wanted to address.
On the other hand, the ability to put non python deps in a place that feels like a venv... feels pretty magical.
Re: Codespaces but open-source, client-only, and unopinionated
#83Re: Codespaces but open-source, client-only, and unopinionated
#84What are some of the competitors in this space? - Gitpod, a SaaS competitor to Codespaces. http://gitpod.io - Coder, which I guess is the more enterprisey self-hosted Codespaces alternative? https://coder.com - This project, Devpod, seems to be a polished experience but not centralized like Coder. - I recently stumbled upon Recode, which looks like a more indie take on the problem. https://github.com/recode-sh/cli
For something a bit more lightweight, Toast: https://github.com/stepchowfun/toast
Re: Codespaces but open-source, client-only, and unopinionated
#85I made something to do remote vscode development on gcp a while back, using some terraform scripts to spin up and down environments: https://lockwood.dev/development/remote/2020/03/17/experimen...
It's pretty crude but hopefully will give people some ideas!
Re: Codespaces but open-source, client-only, and unopinionated
#86Earlier quoted context omitted.
It seems more approachable than going down the NixOS rabbit hole. I haven't had a need to reach for it yet, but I will probably try it out at some point.
I'd be cautious about thinking that you'll be able to use it for complex projects without eventually needing to enter the NixOS rabbit hole. This hasn't happened to me yet on a project that I'm using devnenv with, but while using nix flakes I've found weirdness in nipkgs that I wanted to address. On the other hand, the ability to put non python deps in a place that feels like a venv... feels pretty magical.
Yes for Python it seems to sit between a blurry midpoint of "just use Poetry!" and "just use a container!", but I can see it potentially being useful for a batteries-included devenv in more niche applications like Julia, Elixir, microcontrollers/development boards, etc.
Re: Codespaces but open-source, client-only, and unopinionated
#87Re: Codespaces but open-source, client-only, and unopinionated
#88[dead]
Re: Codespaces but open-source, client-only, and unopinionated
#89I made something to do remote vscode development on gcp a while back, using some terraform scripts to spin up and down environments: https://lockwood.dev/development/remote/2020/03/17/experimen... It's pretty crude but hopefully will give people some ideas!
Thanks for sharing!
Re: Codespaces but open-source, client-only, and unopinionated
#90Earlier quoted context omitted.
It's a lot older but I would say Vagrant intersects with this space https://github.com/hashicorp/vagrant Possibly devenv, as well.. Though I haven't personally tried it https://devenv.sh/
Vagrant was the reason for Hashicorp :-)
Too bad they abandoned it.