3 ms·
Can't edit anymore, but just wanted to say: on review that post came off as snarkier than I intended it. I just mean that, whatever the policy on including clos
by moshmosh 5y ago
Can't edit anymore, but just wanted to say: on review that post came off as snarkier than I intended it. I just mean that, whatever the policy on including closed-source in the primary Brew repo, casks are enabled by default and don't even require a different command or any set-up anymore. From a user's perspective they're 100% as available as other packages, as soon as you install homebrew. I think the only major difference is that they don't auto-update when you do a "brew upgrade"—you have to specify the cask package you want to upgrade. Which is a good policy since a lot of those programs have their own built-in updaters anyway.