The next battle in the decades long PHP Framework Wars has ignited.

Final or un-Final, protected vs. private: sides must be chosen.

Now in development, for those who wish to use code free from ODO (or, Other Developer's Opinions), I give you... UnPackagist.org

@ralphschindler

I expect 50% of the revenue! That was my idea!
https://phpc.social/@heiglandreas/111166934196479477

πŸ€£πŸ˜‚πŸ™ˆπŸ€·

will talk for :elephpant:! (@[email protected])

@[email protected] Or "Superconductor" dependency management for artisans (repackaged composer with unconflictize and some other useful plugins fetching from a subscription based source) @mwop

PHP Community on Mastodon
@heiglandreas ha! great minds! I will give you 51%! 🀣
@ralphschindler I can only presume this is satire...
@ralphschindler
We should really get to removing all of these silly scopes and states from these vendor classes ASAP. Then they'll work exactly the way we want them to.

Seems like a logical outcome... Somebody might just do it πŸ™‚

Though I suspect somebody else would eventually get mad at it and block it from accessing packagist somehow. Then the whole thing would just bring the war from a code project level to a repository domain level.

@ralphschindler it's s good idea, but I have a better one you will need to complete with.

It's called PHP3... same syntax, none of the features.

@ralphschindler this doesn't seem like a security nightmare at all... </sarcasm>
@ralphschindler
Step 4: Profit (as in: pay me to uncouple your code from libraries when you next upgrade becomes impossible, and the compliance department threatens to shut down your bread-and-butter app)

@afilina haha.. hey now, compliance has nothing on us.

We just sunsetted a ZF1 app that was past it's "best before" date by (checks notes) 7 years!