Codespaces but open-source, client-only, and unopinionated
1–10 of 157 posts
Re: Codespaces but open-source, client-only, and unopinionated
#2Really cool! Is this intended for individual users or for keeping dev environment in sync across teams of people?
Re: Codespaces but open-source, client-only, and unopinionated
#3Really cool! Is this intended for individual users or for keeping dev environment in sync across teams of people?
That's correct. It uses the .devcontainer.json standard to define everything as code and it abstracts the cloud/infra and allows for an easy way to spin up a dev environment with a .devcontainer.json in any infra
Re: Codespaces but open-source, client-only, and unopinionated
#4[deleted]
Re: Codespaces but open-source, client-only, and unopinionated
#5Apologies, I'm not up to date in this space, so probably a stupid question but how does this differ to docker compose?
My understanding of the value of codespaces was instant start up, literally zero to download locally, and centralised definition. Does this mean I would go back to have to downloading everything locally, albeit in a nice sandboxed package with a neat definition language and convenient command?
Re: Codespaces but open-source, client-only, and unopinionated
#6I really envy folks working on backend / web stuff when I see these kind of things. Stuck building client apps on desktop and mobile, the options are slim (full VMs, slowness, etc.)
Re: Codespaces but open-source, client-only, and unopinionated
#7I'm likely not the target audience, but I personally see "client-only" as a disadvantage. Ultimately I use VS Code to stand up devcontainers on my laptop, but I sometimes need to do dev work on my iPad and don't want to pay for Github Codespaces. Gitpod has worked for me in the past and I've gotten Coder setup.
Maybe this will be nice to get Jetbrains IDEs working with the devcontainer standard, since IIRC they don't support this at the moment
Re: Codespaces but open-source, client-only, and unopinionated
#8Apologies, I'm not up to date in this space, so probably a stupid question but how does this differ to docker compose? My understanding of the value of codespaces was instant start up, literally zero to download locally, and centralised definition. Does this mean I would go back to have to downloading everything locally, albeit in a nice sandboxed package with a neat definition language and convenient command?
Docker compose is a pretty poor development environment experience. Constantly having to rebuild containers to recompile dependencies; dealing with permissions differences for volume mounts; having to modify all the scripts to start with "docker compose run --rm"; having to deal with no shell history or dot files in the application containers... it leaves a lot to be desired.
Re: Codespaces but open-source, client-only, and unopinionated
#9What 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
Re: Codespaces but open-source, client-only, and unopinionated
#10My immediate thought is the design isn’t there yet. Maybe the tool is but people also pick tools based on how they look, and this could take a facelift before mass marketed.