Have you tried CodeIgniter? I've been using it for a while, it's pretty lightweight in comparison with Zend, it's also much faster in speed.
The MicroPHP Manifesto
71–78 of 78 posts
Re: The MicroPHP Manifesto
#72Laravel is a new PHP framework which focus on clean and expressive syntax, worth a try. ( http://laravel.com )
Re: The MicroPHP Manifesto
#73Re: The MicroPHP Manifesto
#74Earlier quoted context omitted.
Check out Symfony2. The developers adopt some of the best elements of RoR (gems/bundles) and Python (templates) among other things.
some of the best elements of RoR (gems/bundles) I program in Ruby a lot, have done for a long time, and love it, but I've also lost weeks (months?) of my life to fighting gem interdependency problems and watching 'bundle install'. It's almost certainly my least favourite part of the job. That's not to denigrate the efforts that go into RubyGems, Bundler, etc. - they're doing a good job, and they make life much easier…
Thanks!
Re: The MicroPHP Manifesto
#75Earlier quoted context omitted.
some of the best elements of RoR (gems/bundles) I program in Ruby a lot, have done for a long time, and love it, but I've also lost weeks (months?) of my life to fighting gem interdependency problems and watching 'bundle install'. It's almost certainly my least favourite part of the job. That's not to denigrate the efforts that go into RubyGems, Bundler, etc. - they're doing a good job, and they make life much easier…
We're considering a switch to RoR (from CakePHP oddly enough) at my job, but this gem dependency nightmare gives me pause. I ran across rvm in my research, and it's supposed to solve these concerns. I'm wondering if you have used rvm and whether or not rvm solves the problems you've run into in the past. Thanks!
I don't use (or need) RVM on servers, and I don't use it on a daily basis, but I find it useful for testing gems across multiple interpreters before I release them.
Re: The MicroPHP Manifesto
#76I think this is a great and thought-provoking post. The movement toward smaller, decoupled and interoperable libraries in the PHP community is in general a good thing. But without a widely adopted PHP package-management system using many micro libraries becomes more complex to manage than a big all-in-one framework. We need something like NPM for PHP. Maybe PEAR 2 can get us there.
You mean like composer http://packagist.org/ ?
Re: The MicroPHP Manifesto
#77Re: The MicroPHP Manifesto
#78Earlier quoted context omitted.
You mean like composer http://packagist.org/ ?
Yes - like this! Now all it needs is the widely adopted part...
Indeed it will not always be that easy, because the project has to be structured in a way that the autoloader could work with.
Maybe even merely giving the heads up to library developers would be enough to get them to accept it; worth a shot, right?