CodeIgniter

1. CodeIgniter

   #1

   I think I found my newest love affair. AG and I have talked about OOP programming before and I have been trying to find a way to break into it for the longest time. Recently, CodeIgniter (CI) has tickled my fancy. I had been looking at CakePHP for a very long time but the complexity of it seemed a little daunting to somebody just jumping in but I kept going back to the site looking and thinking I could do it.  I read some reviews and saw some benchmarks which is what brougt me to CI. It is a pretty lightweight framework and you have to load all the modules so nothing extra sneaks in. It also doesn't have a template engine which I actually love. I am very comfortable in PHP and don't need yet another abstraction when PHP does just fine as it's own template engine. I don't plan on working with any designers on this so that argument doesn't hold anything for me.
   
   I know MVC isn't exactly OOP, but it is an organized, standardized way of forcing me to code in a cleaner way using and extending classes. It comes with a pretty good toolkit with database abstraction, cacheing, and many other time saving conveniences. Takes a lot of the monotonous grind away and allows me to develop the application more instead of worrying about security and structure and not being able to easily extend in the future.
   
   I am pretty excited about it and am looking forward to starting out with it. I can still reuse a lot of the code I have, just have to rewrite it a bit obviously but the logic is mostly there already.
   
   Anybody have any negative thoughts on this approach?

2. Re: CodeIgniter

   #2

   Looks very nice. If something negative needs to be said, then:
   
   Watch out for newest love affairs in coding frameworks. :)
   
   
   (How much of the code needs to be re-written from the base, and is there an exit strategy if it doesn't turn out as great as advertised?)

3. Re: CodeIgniter

   #3

   Exit strategy is going back to where I am. While I am not "rewriting" it is going to take a large effort to convert anyway. Since I have no formal training in coding per se, I would just be doing V3.0 make it up as I go with no pattern experience and just doing what I have learned since last time.
   
   I think the biggest pull is that it gives me a framework to follow with some standardized conventions to follow. That can only be a good thing. The second thing I like the most about it is that if it comes to a point where I "feel" I am too confined and I can't figure it out in the restrictions of the framework, this one I can totally bypass and just do my own thing. There is nothing in it that actually locks me into using the framework for the entire site. Cakephp sort of forces the issue but CI I can just ignore it and be sloppy for a little if I need to be. Then I can always go back and fix that section after I go to a Holiday Inn Express.

Rise of the Strolenati-Ideas/Suggestions · All categories · Guildhall