Codespaces but open-source, client-only, and unopinionated

Post by nkko » Wed, Jun 21, 2023, 7:28 AM UTC

charcircuit wrote: post #112

mikenikles wrote: post #109

Local first, cloud optional is the only way (IMHO) we're going to get people off their local laptop development setups. We need to support local dev environments first, with the exact same config a developer can then move to the cloud. See https://github.com/jetpack-io/devbox for how this can be achieved and https://www.mikenikles.com/blog/dev-environments-in-the-clou... for my thoughts after 3 years of working in th…

Cloud dev envs do not require millisecond latency. Typing is done locally. Latency only comes in at the times like when you go to open up a new file which isn't locally cached on your machine. Having to wait 200 ms for a file to open isn't so bad.

Post by GTP » Wed, Jun 21, 2023, 7:37 AM UTC

CGamesPlay wrote: post #8

lastangryman wrote: post #5

Apologies, 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.

Post by ycrab » Wed, Jun 21, 2023, 7:41 AM UTC

swaraj wrote: post #107

I haven't used Codespaces, but how does this work with databases? A common problem we have during onboarding is getting your local database (MySQL) setup properly: run all the migrations => load some sample, de-identified, production-like data => update certain rows to allow for personal development (e.g. for our texting service, make sure you text your own phone number, instead of someone else's). What's the workflo…

Post by infinityio » Wed, Jun 21, 2023, 8:47 AM UTC

nkko wrote: post #121

charcircuit wrote: post #112

Earlier quoted context omitted.

Cloud dev envs do not require millisecond latency. Typing is done locally. Latency only comes in at the times like when you go to open up a new file which isn't locally cached on your machine. Having to wait 200 ms for a file to open isn't so bad.

I was wondering how big pain is latency when using VDIs for example. Microsoft thinks 150 ms is OK: "If all frames in a single second take between 150 ms and 300 ms, the service marks it as "Okay." [1]" But putting this in perspective where in gaming this would be unusable, or even when looking at Apple Vision Pro claims of 12 ms needed to make things meaningfully usable. What are your opinions? [1] https://learn.mic…

Post by GTP » Wed, Jun 21, 2023, 12:45 PM UTC

ycrab wrote: post #126

GTP wrote: post #123

Earlier quoted context omitted.

But this is still based on Docker, right? How does this address those pain points?

creating the workspace is based on docker but within the workspace you're free to do whatever you want, no need to use docker-compose there