Kevin

@0xdevalias Since the `1kc-razer` cask you were working on earlier is in the core cask tap, it would benefit from the changes to loading this info from the first suggestion...

Out of curiosity, I looked at parsing this information with the `parser` gem and ran into the problem that this gem only supports valid UTF-8 strings. > Invalid characters inside...

After looking at the code a bit more, I don't think we need to change things to use the API JSON unless we want to get rid of or change...

> > I don't think we need to change things to use the API JSON unless we want to get rid of or change how we use the descriptions cache...

I agree with most of your points especially removing `--eval-all` when only evaluating core packages from the API JSON. It looks like any removal/deprecation of the descriptions cache depends on...

The main performance difference is that loading the JSON for formulas and casks is kind of slow. To load just the core formula hash from JSON it takes around 3/10ths...

Loading core formulae from their Ruby representation is even slower. Loading just core formulae takes at least 5-10 seconds depending on the machine.

In terms of how the DSL should look, would it be too confusing to just have multiple strategy blocks and then just evaluate them in the order they were declared....

Yeah, my idea doesn't really make much sense since it doesn't address passing of information from the first strategy to the second one which is needed here. Are we sure...

To elaborate a little more we can't really have a separate or chained method because the matches from the first strategy block are often needed to build the URL for...