4 ms·

I can't read this without thinking that the author isn't paying attention to the rest of the PHP community. Every point on the checklist is what composer was b

I can't read this without thinking that the author isn't paying attention to the rest of the PHP community. Every point on the checklist is what composer was built to solve and it can be used without any framework. Even in terms of package creation, PSR-4 allows the author of a package to define their own directory structure and inform the autoloader what that structure is. It's great to revisit assumptions, like using one index.php file for a whole project, but I think that's an area where talking to lots of people leads to the best solution.

dools 13y ago
I can't read this without thinking that the author isn't paying attention to the rest of the PHP community. Every point on the checklist is what composer was built to solve and it can be used without any framework. I don't really like composer so I wrote my own package manager[1], but you could just as easily use composer with the cut down "framework" that RocketSled became if you preferred it. And yes, composer (and RocketPack) can be used without a framework. That's sort of the point: PHP doesn't need a "framework" as such, just various tools of choice (like composer if that's your bag). in terms of package creation, PSR-4 allows the author of a package to define their own directory structure and inform the autoloader what that structure is Actually, PHP allows you to do that with spl_autoload_register. I find the "PSR-*" conversations to be pretty pointless and not very interesting. I have a basic autoloader that I wrote and I'm happy with ... BUT in PHP anyone can use any autoloading implementation that they like very simply. There doesn't need to be a standard way of doing things, so long as you provide me with something like a "bootstrap" or autoloader file that I can include in my project and have everything "Just Work(TM)". The only time it becomes a challenge is if you're working within a framework which dictates your directory structure and/or the main entry point of the application. If I'm just creating my own index.php I can include whatever packages, autoloaders, whatever very simply. [1] https://github.com/iaindooley/RocketPack https://github.com/iaindooley/RocketPack

I can't read this without thinking that the author isn't paying attention to the rest of the PHP community. Every point on the checklist is what composer was built to solve and it can be used without any framework. Even in terms of package creation, PSR-4 allows the author of a package to define their own directory structure and inform the autoloader what that structure is. It's great to revisit assumptions, like using one index.php file for a whole project, but I think that's an area where talking to lots of people leads to the best solution.

dools 13y ago

I can't read this without thinking that the author isn't paying attention to the rest of the PHP community. Every point on the checklist is what composer was built to solve and it can be used without any framework. I don't really like composer so I wrote my own package manager[1], but you could just as easily use composer with the cut down "framework" that RocketSled became if you preferred it. And yes, composer (and RocketPack) can be used without a framework. That's sort of the point: PHP doesn't need a "framework" as such, just various tools of choice (like composer if that's your bag). in terms of package creation, PSR-4 allows the author of a package to define their own directory structure and inform the autoloader what that structure is Actually, PHP allows you to do that with spl_autoload_register. I find the "PSR-*" conversations to be pretty pointless and not very interesting. I have a basic autoloader that I wrote and I'm happy with ... BUT in PHP anyone can use any autoloading implementation that they like very simply. There doesn't need to be a standard way of doing things, so long as you provide me with something like a "bootstrap" or autoloader file that I can include in my project and have everything "Just Work(TM)". The only time it becomes a challenge is if you're working within a framework which dictates your directory structure and/or the main entry point of the application. If I'm just creating my own index.php I can include whatever packages, autoloaders, whatever very simply. [1] https://github.com/iaindooley/RocketPack https://github.com/iaindooley/RocketPack