Who's into frameworks?

[YowMamaSita]

So yea, since trying CI back in 2010 ive been relying to frameworks even on small applications. I dont know if thats bad or not - anyway...

Check this http://symfony.com/ its getting popular for php devs, but still no jobs for it on listings...

Well, what's your story with frameworks? pros? cons?

Other fw's worth checking: http://laravel.com/ and of course for the first timers, CI http://codeigniter.com/

[ericb]

Was able to use Symfony back in 2007 as my first ever framework, then switched to CakePHP 2 years ago. AFAIK, Symfony devs are in demand especially from countries in UK. Symfony's learning curve is harder than CI, CakePHP and Kohana, but there are a lot of plugins which can help you on your development. My 2 cents

[Maynard Cabalitan]

Hi
i have a question, what is the big difference of symfony and cakephp? which is better?
thanks

[neilBardos]

I use codeigniter, Yii and Zend for my projects.

[chrstphrbrj]

I have used CakePHP and Yii but I like Yii better.

[dwaqaddi]

sir pag gumamit ba ng codeigniter di na pde gumamit ng wordpress?or pde magkasama un dalawa?

[dyesiboy]

I used CodeIgniter(basic)

[YowMamaSita]

sir pag gumamit ba ng codeigniter di na pde gumamit ng wordpress?or pde magkasama un dalawa?

that depends on your situation e.. let me list out some possible scenarios

kung meron kang site built from codeigniter and you want a blog for your site, yes you can still use wordpress and do some integration (nothing you wont understand btw, integration is something that would be easy to do in this case)

pero if youll be building a cms from codeigniter then using wordpress for --? i dont think that makes sense so.. no.

you can also use codeigniter if youre already using wordpress as your main script, and you want codeigniter to serve a different function (and you do prefer working with a framework)

tldr you can still use CI alongside any script, I guess you have no idea what CI/frameworks are, so better read first and apply para magets mo lalo patience is a virtue! lol, daming sinabi )

[arisroyo]

Advice from Rasmus:
1. Use PHP as-is, without additional complex external layers.
2. A good framework it will provide you a dozen things that you will never need.
3. No one is going to build your application for you, no matter what it promises.

[zero1]

I use CI, I swear by it. I hate the thought of doing PHP projects without using any framework. I would consider myself a CI evangelist (or rather a blabbermouth) at work since I'm the only one who know how to use it. I'm pushing my colleagues to use CI so that its easier for others to locate where a feature need to be updated.

Other pros with CI is that it has helper functions (security), the documentation, and its ActiveRecord . The cons I could say is that some of the modules such as Javascript and sqlsrv driver do not work and I still need to modify them before I can use them.

Lately, there seems to be a need for HMVC developers from oDesk clients. It seems that CI does not natively supports it but there's a workaround. I'm not aware of this HMVC thing and why the need to distinguish them from MVC-only framework. So I think that's one of the cons of CI that I might consider jumping ship in the future.