(no title)
Yanael
|
1 year ago
I started to develop in containers before VSCode introduced the dev container to keep my local machine clean. A few years ago, I switched to the VSCode dev container, and the integration is very good. Having the ability to have a dev environment ready per project is very neat. We started to adopt it in my company. As a team it saves a lot of hassle, and onboarding is much faster. However, we have encountered some issues, mainly when we want to work with GPU and PyTorch dependencies, and that is the opposite of pleasant! Otherwise, now each new project/repo I create comes with a dev container.
ikety|1 year ago
A form of this which mixes devcontainer and nix might be the holy grail
https://www.youtube.com/watch?v=kpBXrsVg83Y&t=941s
Positives
- You lean on the power of dev containers while still using a portable spec
- You get access to nixpkgs which is arguably the most exhaustive package library
- You get the "true reproducibility" of nix over docker
Negatives
- Docker remains the king for ephemeral databases, more convoluted to manage with nix
ossusermivami|1 year ago
(nobody in my team use vscode or devcontainers but enjoy using docker)
Yanael|1 year ago
In your case, is maintaining 2 dev env not annoying?
ronef|1 year ago
synergy20|1 year ago