3 ms·
Also maybe a namespace. I doubt they're the only person to have ever made a class called `\Client` :) http://phptherightway.com/ http://phptherightway.com/ Th
by TazeTSchnitzel 11y ago
Also maybe a namespace. I doubt they're the only person to have ever made a class called `\Client` :)
http://phptherightway.com/ http://phptherightway.com/
Though I notice that the README states "[i]ts goal [is] to have one easy to use PHP file without dependencies", and they point out there's already a proper package out there, kelunik/acme. If the goal is a single file with no dependencies, I can understand the lack of Composer, as it's not really targeted at that audience.
- Raed667 11y agoThank you for the great link.
- jnardiello 11y agoIf the target audience are those developers manually including everything, then it's not a package for me. Using composer is completely unrelated to having (or rather not) dependencies. It's actually pretty much the opposite: a way of distributing your package to projects who wish to use it. So again: please use composer. Completely agree with the namespace. You HAVE to namespace it :) Hope it helps
- efesak2 11y agoComposer is awesome, but this is not a package ready to use! (at least not now). Valid point for namespace.