3 ms·
Or you juggle multiple projects that may not be on the same versions of everything. Or you sometimes need to git-bisect back to an older version of your project
by yamtaddle 4y ago
Or you juggle multiple projects that may not be on the same versions of everything. Or you sometimes need to git-bisect back to an older version of your project, which may have older dependencies including e.g. Ruby or Python or Node versions or uses a different and incompatible version of Cmake or whatever, and it's much nicer to have an isolated environment for that, scripted such that it's used automatically, than having to fiddle with the programs actually installed on your dev machine.
And it's nice to have all that work across an entire team, no "works on my machine" weirdness.
- fatih-erikli 4y agoMaintainig containers will cost more than keeping the package.json or rubyjso whatsoever updated. Also you need some hacky things to make vbox running on OSX so it becomes totally a "works on my machine".
- yamtaddle 4y ago> Maintainig containers will cost more than keeping the package.json or rubyjso whatsoever updated. Fine. What about compilers? System libraries? PostgreSQL version & config? Does package.json manage your node version? Oh and we switched from npm to some hipster new thing a while back, and older package.json files of ours will fail to install properly with the new thing. Have fun git-bisecting. > Also you need some hacky things to make vbox running on OSX so it becomes totally a "works on my machine". Been doing this for like a decade and it's not much more than "brew install docker" and a line or two in your shell rc file. It used to be slightly worse because you had to manage docker-machine separately, but it's never been hard or complicated.
- fatih-erikli 4y agoHow do you install brew? You copy paste a line from a website?
- yamtaddle 4y agoYeah, of course.