ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

CI or not

November 22, 2010 10:44am

Subscribe [2]
  • #1 / Nov 22, 2010 10:44am

    RJ

    179 posts

    Hello World!

    I began with CI two years ago while increasing my programming skill set.  I have used it for several projects sense.  I am beginning a new project that will be substantially larger than the previous ones and I thought it would be a good idea to evaluate the pro/cons of CI vs other frameworks.  As I keep pushing deeper into the CI community I notice some of the veterans who support appear to be leaving CI for various reasons. 

    (Least not the failure of a 2.0 stable launch, which for one I can agree as 2.0 was being discussed when I first started with CI.. WTH?)

    Anyways I would love for some community feedback.  I enjoy CI because of the documentation and simple learning curve.  I dislike CI due to its lack of a library/contribution repository.  Too many separate libraries seemingly trying to accomplish the same thing and you never know what is maintained and/or relevant to the 2.0 version without significant effort.

    CI or not?  I am building a social site that will serve millions of users.  I need caching, ability to provide a developers API, ORM (maybe), superior security, speed/speed/and more speed!

    I appreciate your feedback.

  • #2 / Nov 22, 2010 6:21pm

    Vheissu

    278 posts

    I’ve been asking myself this recently, I am relatively new to Codeigniter I have only been using it a few months and feel I have mastered how to use it. Codeigniter isn’t really a framework in the sense of coding conventions and set ways of doing things. So I came to the conclusion that Codeigniter kicks the ass of every other framework out there because of this.

    Codeigniter to me feels like a set of useful functions and classes that save you having to write functionality to do repetitive tasks and make database interaction easier. In comparison to something like CakePHP or Kohana, Codeigniter feels like it can do anything in half the time and half the learning curve.

    In the end you’re going to find Codeigniter isn’t going to be your limitation, but rather PHP itself, sorting out caching, optimising database queries and having the adequate server power on hand as well. I reckon if Codeigniter is what you know well, stick with it.

    For example: changing from what you know all for the sake of saving 2ms of page load is probably a bit ridiculous.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases