Using rvm is a real pain in the ass. I'd rather install Ruby from
Homebrew and then hardcode the gem paths. After all, I only need
this for building DSpace on macOS.
I haven't compiled anything with golang in like a year, and I'm sick of all
these conditionals running during shell initialization—my zsh takes several
seconds to start!
Ansible 2.4 deprecates this variable in favor of ANSIBLE_INVENTORY but I
decided that we should just be specifying this in the ansible.cfg inside
each project anyways.
I liked using Homebrew from a custom prefix but it causes many more
packages to have to build from source because the pre-compiled ones
from Homebrew's CI are installed in /usr/local and non relocatable.
I'm sick of always wondering if there is an issue with my python
because of some pyenv issue, and not to mention I'm happy to get
rid of one more dynamic thing that needs to run on shell init.
Python 3.5+ seem to have pretty easy virtual environments so I will
just use those from now on, ie:
$ python -m venv ~/ansible
$ . ~/ansible/bin/activate
Homebrew runs `brew update` before every fucking brew command? No
thank you. Also, after reading `man brew` I found there are some
other options to tweak for security and performance, like disallowing
HTTPS→HTTP redirects and using less cores to compile stuff (running
four make jobs on a system with two real cores? WTF, Homebrew?).
I noticed a blog post pointing out that resized images usually end
up looking a bit dim or blurry. He suggested some different unsharp
settings, and they do produce an image with more detail.
See: https://even.li/imagemagick-sharp-web-sized-photographs/
This sometimes results in a bit of overhead in image size but allows
images to be loaded in a much more user-friendly way.
Signed-off-by: Alan Orth <alan.orth@gmail.com>
I prefer pkgsrc, but the packages are only updated once per quarter,
so if something is broken you won't get a fixed version for a few
months, or if you want some new upstream release you have to wait.
Installed homebrew manually in /opt/brew because of Mac OS X's system
integrity protection since 10.11.
Signed-off-by: Alan Orth <alan.orth@gmail.com>
These are needed by password store (pass) when editing passwords,
and they are not part of the user's PATH by default.
Signed-off-by: Alan Orth <alan.orth@gmail.com>
