-
Notifications
You must be signed in to change notification settings - Fork 53
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
The big WHY #140
Comments
Yeah, as I said: "It is mentioned in the docs", BUT… I'm kinda talking about headlines, slogans, marketing ;) The first big thing I see on the website is:
PHIVE – the manager for your project's PHP tools! |
Well, phar-io/phive#417 kind of related to this. |
It is mentioned in the docs, but for me – a simple developer who wants to solve a problem – it is not emphased enough…
Why would anybody want to use Phive? Learn yet another tool, figure out how to configure it, maintain?
I can now remember what was the issue that Phive solved for me a few years ago:
require-dev
the tools like PHPUnit, PHPMD, etc.So: this is BIG for me. Phive solves a real–world problem ;-) It should be clearly advertised as the replacement for Composer when it comes to tools.
All the "verification" stuff, GPG, etc. – it is a "clutter" to me – I didn't find Phive for that. It is actually a burden – stuff that I have to (while don't wanna xd) learn, understand -> to make Phive finally solve my "real problem". All that GPG, keys, etc. – I know it is important be working, but kinda should stay behind, as the internal stuff, not the feature itself. Automated as much as possible. Just my humble opinion.
So yeah, I'm not a marketing guy or anything, but "Phive is a Composer for tools", "Use Phive instead of Composer to download your tools", "Have conflicts between your app dependencies and developer tools dependencies? Use Phive!" – should be a clear and visible message :D
The text was updated successfully, but these errors were encountered: