3 ms·
I seem to be in the minority here. Here it is: I really like this solution. Homebrew is not perfect and I had lots of headaches and problems with it. To install
by csomar 10y ago
I seem to be in the minority here. Here it is: I really like this solution. Homebrew is not perfect and I had lots of headaches and problems with it. To install a program, I have to download lots of dependencies with it. Sometimes, these dependencies (especially Python) messes up with their counterparts; and then I have hell.
Lots of pythons versions, installed everywhere, and something broke somewhere. Then it comes the day I need a package, and homebrew give me that finger. There is, certainly, no way I can debug this problem since the debug log is a 5,000 line of incomprehensible gibberish.
This solution, looks like it consumes lots of resources. Well, resources are cheap these days. And I expect the next Macbook to have a more powerful CPU and at least 32GB of Ram. So consuming resources is the least of my worries.
My workflow today already consists of 8 docker machines. Every product is a machine and each machines has several containers. The dev deployment is a bash file that create and run these containers. I don't even need a full backup anymore! Everything is backed in Github and reproducible given enough internet bandwidth.
The next logical step is to have whalebrew; and thus all my unix/linux utilities are now contained in Docker too. My MacOs fresh install will have: Chrome, MacVim and Docker.
Now if Safari is as good as Chrome and a superior Vim (to Macvim) could be installed through a Docker container, my fresh MacOs install will only has Docker!