5 ms·

Happy to take this one, as I am one of the cofounder of Daytona. Daytona solves all the automation and provisioning of the dev environment, actually wrote an a

Happy to take this one, as I am one of the cofounder of Daytona. Daytona solves all the automation and provisioning of the dev environment, actually wrote an article here laying out exactly what we do: https://www.daytona.io/dotfiles/diy-guide-to-transform-any-machine-into-a-codespace https://www.daytona.io/dotfiles/diy-guide-to-transform-any-m... Daytona currently supports only the dev container (https://containers.dev/ https://containers.dev/) "dev env infrastructure as code" standard, but are looking to support others such as devfile, nix and flox. Hope this helps

sandGorgon 3y ago
ahh interesting - so there's a split on the dev format. why did you choose dev containers vs nix ? genuine question - asking because replit makes a big deal of nix, so it seemed to me as a very popular choice.
- nkko 3y ago
  Dev containers provide a robust standard that is seamlessly integrated into VS Code, which makes workflow smooth end-to-end. Thanks to the Daytona plugin architecture and Apache license, it is relatively easy to bring in more standards. Cause, you know: https://xkcd.com/927/ https://xkcd.com/927/
- ivan_burazin 3y ago
  You only have so many things you can do at once. From our perspective dev container seemed to be what our target audience was already using; as its supported by VS code natively and also as almost all OSS projects are hosted on Github, and their product Codespaces support it as well - it seemed like the logical first standard. But as mentioned devfile, nix and flox are on the roadmap.