Skip to content
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

Explain why we "probably want imagemin-optipng instead."? #111

Open
Pomax opened this issue Dec 12, 2019 · 2 comments
Open

Explain why we "probably want imagemin-optipng instead."? #111

Pomax opened this issue Dec 12, 2019 · 2 comments

Comments

@Pomax
Copy link

Pomax commented Dec 12, 2019

The readme opens with "You probably want imagemin-optipng instead." but no explanation as to why. Was it renamed? Was it moved? Was a new projected started and this one's now on life-support? Why would we probably want imagemin-optipng? =)

(and can that information be added to the README.md?)

@scmx
Copy link

scmx commented Nov 3, 2020

imagemin-optipng uses optipng-bin so it's just an advice to probably install that instead

@Pomax
Copy link
Author

Pomax commented Nov 3, 2020

If it needs explanation, that explanation should be in the README.md, not left as guessing game. README's should not have "probably": if there are use cases in which a different technology is advised, it should explicitly state when it is appropriate to use this CLI tool, and when it is advised to not use it.

In both American and British, in lieu of a more detailed explantion "you should probably use X" means "you should use X" with the "probably" merely there to soften the command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants