3 ms·
Python and node are probably the easiest to get setup. With Python you have venvs which do a lot of the heavy lifting required. The issue becomes when you are
by fnord123 6y ago
Python and node are probably the easiest to get setup. With Python you have venvs which do a lot of the heavy lifting required.
The issue becomes when you are on a non Linux environment for development and deploy to Linux in containers. If you build your code locally then you are debugging $DESKTOP issues which might not be the same as Linux.
Also languange environments with poor dependency management (e.g. C, C++) benefit from having an installable system.
> Even assuming they have the same version of macOS, homebrew constantly evolves so getting everyone developing with the same version of dependencies as you use in prod is super painful.
If someone is using homebrew for their development dependencies, unless they are targeting a release to homebrew, kindly ask them to stop doing this.
- black3r 6y agofor me the best advantage of working with containers is the initial setup for new colleagues, especially junior devs..., setting up pyenv, correct version of python manually, nvm, postgres, etc.. takes time and our setup guides grown a lot in the past 5 years..., with containers all those long setup guides can boil down to `docker-compose up -d`
- scruple 6y agoOn-boarding really does seem to be the major pull. I've been developing along side docker containers for years now and I just don't see that changing. I do see value in it, though, after the comments and after doing some additional reading. I could see myself pushing this direction if the teams I worked on had higher churn rates or more frequent new hires. Also, I think that it lends itself well to certain tech stacks / languages / ecosystems than others.