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

The big WHY #140

Open
MacDada opened this issue Jul 24, 2023 · 3 comments
Open

The big WHY #140

MacDada opened this issue Jul 24, 2023 · 3 comments

Comments

@MacDada
Copy link

MacDada commented Jul 24, 2023

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:

  1. I was using Composer to require-dev the tools like PHPUnit, PHPMD, etc.
  2. I started to have conflicts between my "real" project dependencies and the dependencies required by the tools.
  3. Phive separates "my" dependencies from the dependencies of the tools.

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

@theseer
Copy link
Member

theseer commented Jul 24, 2023

We can probably rephrase that and make it more obvious to the likes of what you wrote, but the intro Text actually has all of that:

image

:-)

I'll keep that also in mind :)

@MacDada
Copy link
Author

MacDada commented Jul 24, 2023

the intro Text actually has all of that

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:

The PHAR Installation and Verification Environment (PHIVE)
Installation and verification of phar distributed PHP applications has never been this easy!

  • WOW, that's complicated…
  • Phar… What is Phar? Do I use any Phars? Do I need them?
  • Verification Environment… Wow, I don't understand that ;)
  • Distributed PHP applications… Hmm, am I writing a distributed application? I guess not… What are those anyway?

PHIVE – the manager for your project's PHP tools!
Stop downloading tools with Composer – use Phive instead!

@dereuromark
Copy link
Contributor

Well, phar-io/phive#417 kind of related to this.
It seems that once you actually need a bit more than just the default tool you might run into a wall
Maybe I didnt find this in the docs, but it would be nice to know that you can configure it somehow to include those extra things as well without having to drop phive install/setup right away.

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

3 participants