Skip to content

The big WHY #140

Description

@MacDada

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions