-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
List available casks in the http://caskroom.io/ #10858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
There is a search. Submit an issue (or even better, a PR), to the appropriate repo to clarify the message. |
I am saying that as a new user it's very unclear what is available in cask. |
No one is discarding it. I'm saying your feedback is in the wrong place. Please submit it to the appropriate repo, where it should be discussed, and the appropriate people will see it. In addition, by submitting an issue or a PR, we can properly discuss what changes need to be made to make it clear. Simply saying “I couldn't understand the website” doesn’t help at all; we need you to clarify at length (or, once more, submit a PR) what will address the issue of it not being understandable. Why isn’t it understandable? What exactly could’ve been done to make it better? Those are the kinds of insights we need from you. To do it, lets do it right; open an issue in the appropriate place. In addition we're not a discoverability service. This has been discussed multiple times, as it is not part of the goals of homebrew-cask. Amongst other things, the logistics are unsustainable. This is to say you’re not supposed to see all casks available — the goal is to have them all; you’re supposed to install what you want, not shop around. |
Something that is missing though is which applications are available in cask. Having a page with a dynamically assembled list, or specifying a command to see available software on http://caskroom.io would be very useful.
By the way, in all honestly, it wasn't immediately clear to me what cask was when I first read your homepage.
The text was updated successfully, but these errors were encountered: