![]() With the massive addition of prebuild binary 'bottles' now provided, this has become even more true. And when it doesn't work will tell you why its not working in a clear way. When an install is not thoroughly damaged, I assure you it just works. Homebrew's entire premise is that it just works. ![]() Updates will have to be tracked manually, and applied in the same laborious google, download, wait, click click, click done kind of way. The installer works great and will generally just work. ![]() Here are some of the (lame imo) arguments against it: Finally, if you go with homebrew it give you access to automated, unattended installations to all non unixy applications via homebrew cask: Finally, as someone interested in development, having access to all the amazing tools packaged by brew (including ruby, python, go, rust etc) is totally awesome. If you understand git, going back into history and installing old versions of programs is trivial. The package manager itself is just a git repository of ruby formula that live in /usr/local so its really easy to make changes to the package build process if you disagree or need something different that was packaged. It gives you updates nearly as soon as they are available thanks to the amazingly dedicated community of contributors. I would highly recommend installing everything (including node) via homebrew and homebrew cask if you can be bothered to. Tl dr homebrew is great and you should totally install node with homebrew if you like homebrew Hi! Homebrew node formula contributor here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |