Add a description to cask

[muescha]

add a one line description to cask

to get niceer listings like:

acorn       - Acorn 4, a great Mac OS X image editor, built for humans. - Flying Meat
adapter     - Adapter - Free Image and Video Converter for Mac and PC
adventure   - Adventure - Mac App Store Downloads on iTunes - Apple
aegisub     - Aegisub Advanced Subtitle Editor
aero-fs     - Secure File Sharing and File Sync | AeroFS | Features
air-server  - AirServer - Most advanced AirPlay receiver for Mac and PC
airfoil     - Rogue Amoeba | Airfoil for Mac: Wireless Audio Around Your House
amadeus-pro - Amadeus Pro - HairerSoft - Audio editor / sound and voice recorder ...
anki - Anki - powerful, intelligent flashcards
anonym      - Download Anonym for Mac - Surf the Web anonymously ...
app-zapper  - AppZapper - The uninstaller Apple forgot.
appcode     - JetBrains AppCode: Objective-C IDE done right
arq         - Arq: Online Backup for Mac to Amazon AWS Glacier and S3 ...
asepsis     - Asepsis is a system utility for prevention of .DS_Store files
you-view    - Download YouView for Mac - Browse YouTube without a browser ...
zap-proxy   - OWASP Zed Attack Proxy Project - OWASP
zero-xed    - Using a custom number format to display leading zeros
zip-cleaner - Download ZipCleaner for Mac - Discard superfluous files from .zip ...
zooom       - Zooom/2: Window management for your Mac made easy

(from this gist: https://gist.github.com/phinze/211a02d0223acb700260 )

[acollign]

👍 that would be very useful and would benefit the search feature.

[phinze]

We've discussed this in the past and made the same conclusion that homebrew makes: homepages are much easier to maintain than descriptions.

The maintenance problems are numerous:

• who decides how to describe an app concisely?
• how long/short would descriptions be?
• how to deal with apps that require a ton of description?
• what about apps that add/remove core features... who keeps the description up to date?
• what about disagreements in how to describe a given app?

That gist was just a list of fetched <title> elements from homepage - if I were to regenerate the list today I bet you many apps would be different. That's the beauty of storing URLs - each app's team can be responsible for how the app is presented.

I'm happy to entertain counterarguments here, but I'm just not seeing the work/benefit ratio working out for this.

[muescha]

and it would also improve the search results if the brew cask search also can search the description