3 ms·
This looks really cool. I've recently been similarly inspired by watching Node.js guys (Substack in particular) and the penchant for very targeted re-usable com
by dools 15y ago
This looks really cool. I've recently been similarly inspired by watching Node.js guys (Substack in particular) and the penchant for very targeted re-usable components.
The strength of PHP is that there's so much code already written that monolithic frameworks are a step backwards, but a good package distribution system is required for this to work.
I recently released a little front controller style microframework that has a default autoloader with a simple way to register your own:
https://github.com/iaindooley/RocketSled https://github.com/iaindooley/RocketSled
and an associated package manager that basically just has a list of github repos and a config file which specifies dependencies:
https://github.com/iaindooley/RocketPack https://github.com/iaindooley/RocketPack
Since I don't want to constrain myself to using only namespaced code or one particular autoload implementation I won't be using Composer just yet (indeed I'm an advocate of a "lazy" namespacing policy) but I look forward to following the project's progress via github.
My goal is to use tools that don't "have an opinion" - that allow me to use whatever is going to get the job done most quickly. Things like coding standards, policies and aesthetics are moot when it comes to delivering code on the day, especially if your code is highly modular and compartmentalised.
- bergie 15y agoRegarding Substack code, I've made a PHP implementation of the DNode protocol: https://github.com/bergie/dnode-php https://github.com/bergie/dnode-php With this you could actually call Node.js code from your PHP apps. And yeah, php-dnode is available on Composer :-) http://packagist.org/packages/dnode/dnode http://packagist.org/packages/dnode/dnode
- dools 15y agoOh cool! I was interested in dnode-php, you've already done all the work :) /me follows